[llvm-dev] [RFC] One or many git repositories?
Patrice Kouame via llvm-dev
llvm-dev at lists.llvm.org
Sat Sep 3 15:04:27 PDT 2016
+1 for keeping it separate.
One can easily set up a git subproject structure if the need is pressing...
> On Sep 3, 2016, at 5:39 PM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>> On Sep 2, 2016, at 12:33 PM, Dimitry Andric via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>> On 16 Aug 2016, at 00:12, Lawrence, Peter via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>> As someone that has worked with both gcc and llvm,
>>> One thing about gcc that drives me bat-guano-crazy is that
>>> First you check out gcc, try to build it, and find that you also
>>> Need mpc, so you check that out and try to build it, and
>>> Find out you also need gmp, so you check that out and try
>>> To build it, and find out that you also need mpfr, …..
>> I can understand your frustration, but these are all completely external libraries, and it does not really make sense to include this into any mono-repository.
>> For example, you are also dependent on libc headers, are you going to include these into your repository? And kernel headers? The end result will possibly include half of GitHub into that mono-repository... :)
>> So as usual, for any open source project, read the requirements first, and install those from whatever your local package management system is.
>> If LLVM is going to use a mono-repository, it should only include LLVM components, in my opinion.
> This seems a good principle in general, but note that we already included external projects in the repo. Out-of-my-head right now I can think of the google tests library, and ISL.
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
More information about the llvm-dev