[llvm-dev] New LLVM git repository conversion prototype
Chandler Carruth via llvm-dev
llvm-dev at lists.llvm.org
Thu Oct 18 14:41:36 PDT 2018
On Thu, Oct 18, 2018 at 12:03 PM Martin Storsjö via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On Thu, 18 Oct 2018, Renato Golin via llvm-dev 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
> >> * libcxx
> >> * libcxxabi
> >> * libunwind
>
> +1 from me for this layout as well. (Ideally maybe with all these 4 libs
> separately.)
FWIW, this was discussed repeatedly and extensively.
At the end of the day, there was (slightly) more support for just having
one, and so that's what folks have made progress implementing.
Personally, I'm much more in favor of the current prototype layout. But I'm
even more in favor with getting this stuff to github sooner rather than
later.
There are a bunch of ideas about how to effectively allow people to
*consume* these libraries in reasonable ways despite them being developed
in a monorepo. I think we should focus on working on these, seeing how well
they work, and getting them to provide an adequate model. It may not be
perfect, but my impression from all of the discussions is that this will be
the least bad overall.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181018/887d3f6d/attachment.html>
More information about the llvm-dev
mailing list