Re: Should lang/clang use lang/libLLVM?

[Kamil Rytarowski <n54%gmx.com@localhost>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 30.12.2015 14:46, Benny Siegert wrote:
> Hi!
> 
> I noticed that there is a large amount of files that are duplicated
> between the clang and libLLVM packages, albeit with slightly
> different paths (e.g. include vs. include/libLLVM).
> 
> Is there a reason for this duplication? I would love to see clang 
> depend on libLLVM, so that you can have both and not rebuild the 
> world twice.
> 
> Thoughts?
> 
> --Benny.
> 

I'm developing LLDB for NetBSD and I keep llvm, clang (cfe) and lldb
separated. The three packages are in wip as wip/llvm, wip/clang and
wip/lldb. Today all the LLVM elements are either modular or close for
modularity (see wip/lldb/patches).

Last time I checked it was applicable for libcxx and compiler-rt as well
.

Building the stack of llvm+clang+lldb in one go with debug symbols and
all backends consumes for me at least 64GB RAM+storage space and a lot
of time (since I don't have so much RAM). For this reason I
modularized the LLDB dependencies in wip.

The LLVM project decided to make the next release the last one to ship
with autoconf and gmake build system. We will need to refactor the
Makefiles for it when it will happen.

I would opt for modularization of lang/clang into lang(devel)/llvm,
lang/clang, devel/lldb etc. Otherwise I will need to add a special
rule for lang/clang and build it without debug symbols and stick to
wip packages.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWhDWcAAoJEEuzCOmwLnZsiokP/R+zcg5rm067xOHaVy5zZoX8
s+Z4rwyoh3L4bl4rbjPIa1B4KJFGV/T423uovZBlEVBZO0gC2yHt8yQucv+M9kb2
z1Di/vEkpgO3ltv7CIXka2Y1dHmYpGmrSI5e2dHrbnmOre7ZSrPLqCSWvGksTDTr
CbyecK3sXW0qguQAq6AoRUIF2iaKO2Qul41zEiBVhuthqbaNW98kLiIUFRVgm5Zt
nfPj0QeUKQN18bBf8dR17W6USJ2wC9nv6WCupaokvZoePI07efwK69B6t8UNDTj1
30+PuRlXUj6srScpRCUuvSErPCZJy+0FHvMrwkyosF5FISUZX7sc6E+yUKHfZ3/c
UrhgzGaabJKUUBmznkpKYf/ozE+WTJN/f9SN/R+vHXcBoofaNmeWFWPv8B73Ag7L
hFaFYTT4Dy5Gmb3rJpOz88npcH9p6Fa9ry5RBLsD7TN1YFPHZkbP6uNxdODkEhu4
zK6/khWDu3coQyCeqs10R7l578h1+THrLXi/lOlyeH2ZCyCH5vVlcF7qkXeox7+U
GtXkvxv+ggH52FSoNqtm6KBtgpYyeKL1LfEah7xQnAOvFl8MY3CggoiMR4DE91MT
6YxkKpleMSFNLhHtVFXOLOyKwDlfItGGwPDgSj4P9NZm/4wpf8zN+cQZMCkfOWRy
TrSOCrXD3PEa5ueoGh6e
=Z+vU
-----END PGP SIGNATURE-----