[llvm-dev] [RFC] LLVM Directory Structure Changes (was Re: [PATCH] D20992: [CMake] Add LLVM runtimes directory)

Sean Silva via llvm-dev llvm-dev at lists.llvm.org
Tue Jun 14 20:23:35 PDT 2016

On Tue, Jun 14, 2016 at 10:38 AM, James Y Knight via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> On Tue, Jun 14, 2016 at 1:19 PM, Renato Golin via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>> On 14 June 2016 at 17:40, Chris Bieneman <beanz at apple.com> wrote:
>> > I believe that splitting compiler-rt's sanitizer libraries and builtin
>> archives into separate projects will allow the project structure to more
>> clearly represent the way it fits into the project build graph. It is not
>> strictly necessary for anything, so if people generally don't agree I won't
>> fight for it.
>> I think my general feeling of this thread is that most people agree
>> with the idea. I personally do.
>> +1 from me.
> IMO, they should not be split apart into different repositories, because
> tracking lots of tiny repositories is annoying. If anything, I think llvm
> should be moving towards merging some of the repositories together, not
> splitting further apart.
> But, splitting their *configuration systems*, making the two parts have
> separately invokeable "toplevel" cmake files (or whatever like that is the
> appropriate solution) seems like a fine idea.


This gets to the essence of my concern.

-- Sean Silva

> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160614/bbd624b0/attachment.html>

More information about the llvm-dev mailing list