[llvm-dev] Third-party libraries policy

[Mehdi Amini via llvm-dev]

> On Oct 18, 2016, at 6:28 PM, Bekket McClane via llvm-dev <llvm-dev at lists.llvm.org> wrote:
> 
> Hi,
> The LLVM variant we're building now contains usage of a third-party threading library, and we would like to push our work upstream in the future.

What is the motivation?
For instance what is this doing that std::thread or llvm::ThreadPool is not providing? Why is it useful to have it in tree?


> Are third-party libraries welcomed to be added in LLVM? If yes, what folder structure should we arrange? 

In general we avoid them as much as possible and need a really compelling justification to include one.
Chris reinstated this position recently: http://lists.llvm.org/pipermail/llvm-dev/2016-September/105166.html <http://lists.llvm.org/pipermail/llvm-dev/2016-September/105166.html>

— 
Mehdi

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20161018/856c1b99/attachment.html>