[llvm-dev] New LLVM git repository conversion prototype

[Roman Lebedev via llvm-dev]

On Thu, Oct 18, 2018 at 5:46 PM Zachary Turner via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
>
>
> On Thu, Oct 18, 2018 at 6:46 AM Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>
>> On Thu, 18 Oct 2018 at 14:19, David Chisnall via llvm-dev
>> <llvm-dev at lists.llvm.org> wrote:
>> > I would still prefer that projects that are not tightly coupled to LLVM (lib*, pstl, compiler-rt) be in separate repositories.  These do not link against LLVM libraries, are not version locked to any given LLVM / clang / whatever release, and most of them need to support multiple LLVM releases, so there is little benefit to having them in the monorepo and there is a disadvantage for people wishing to use and contribute to them independent of the rest of LLVM.
>>
>> This sounds like:
>>
>> Mono-repo:
>>
>> >   * cfe -> clang
>> >   * clang-tools-extra
>> >   * llvm
>> >   * llgo ??
>>
>> Separate - Core Libs (4 repos or all-in-one?):
>>
>> >   * compiler-rt
compiler-rt tests strongly depend on clang version.

>> >   * libcxx
>> >   * libcxxabi
>> >   * libunwind
>>
>> Separate - Other Libs (each in own repo):
>>
>> >   * libclc ?? (in mono?)
>> >   * polly ?? (in mono?)
>> >   * openmp
>> >   * parallel-libs
>> >   * pstl
>>
>> Separate - Tools (each in own repo):
>>
>> >   * lld
>> >   * lldb
>
>
>
> lld and lldb are at least as tightly coupled to llvm as clang, if not more.  lldb, for example, is strictly more coupled to llvm than clang, since it is also tightly coupled to clang.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev