This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Should we import gnulib under gcc/ or at the top-level like libiberty?

On 11 July 2016 at 13:53, Mikhail Maltsev <> wrote:
> On 07/10/2016 08:15 PM, Manuel López-Ibáñez wrote:
>> Moving all gnutools to a single git/svn repository that can still be
>> built piece-wise would help sharing gnulib and other useful libraries.
>> If LLVM can do it, there is no reason why gnutools can't. And they
>> have shown that it helps code reuse and modular design. All the manual
>> syncing between gnu projects is a waste of time.
> But LLVM does not keep everything in a single repository. In fact, it's quite
> the opposite: they have a separate repo for Clang (the frontend, ~ gcc/c, cp,
> ...), for compiler-rt (~ libgcc), for libc++ (~ libstdc++).
> All utilities (~ libiberty) live in the LLVM repo (include/llvm/ADT,
> include/llvm/Support, lib/Support). Other projects, like LLDB, are checked out
> into a subdirectory, and are always built from the combined tree.

I stand corrected. It has been a while since I built the whole LLVM
toolchain and I was misremembering the details.



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]