[lldb-dev] Exclusively build and install LLDB?

[Kamil Rytarowski via lldb-dev]

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

On 27.11.2015 00:57, Kamil Rytarowski via lldb-dev wrote:
> On 11/23/15 10:28, Pavel Labath wrote:
>> I believe that for purposes of building distribution packages you
>>  should use the out-of-tree mode of building lldb. This means,
>> you build llvm and clang separately, and then point your LLDB
>> build to their installation path with LLDB_PATH_TO_LLVM_BUILD and
>>  LLDB_PATH_TO_CLANG_BUILD variables. This way you can avoid 
>> building llvm/clang twice, you can have a separate package for
>> each logical component of llvm and you can make lldb optional for
>> your users (e.g. have only clang installed normally, if user
>> chooses to install lldb, it will automatically pull in clang if
>> needed). In this mode "make install" should install only the lldb
>> components, which should be correctly linked to the
>> already-installed llvm libraries.
> 
>> That said, I can't guarantee that this mode will work for you 
>> out-of-the-box. We occasionally get patches to fix it up, but I 
>> don't know anyone who is using it extensively. However, I think 
>> this would be the best way forward for you and I'm prepared yo
>> help you out if you choose to go that way.
> 
>> What do you think about that?
> 
>> pl
> 
> 
> Thank you for your note on this mode. I was trying to prototype a
> set of packages with: sources of llvm and clang, build dirs of llvm
> and clang and installations of llvm and clang.
> 
> Badly this approach doesn't work with pkgsrc, as this framework 
> contains various checks against using sources, headers, executables
> or other files out of the build tree. Packaging sources and build
> tree triggers errors with moving invalid files into ${DESTDIR}.
> Everything is wolkaroundable, but I think it's not the correct way
> of handling it.
> 
> I've checked that libcxx, cfe and compiler-rt ship with mechanism
> to build against preinstalled LLVM. I will try them out and I'm
> going to prepare new pkgsrc packages using this approach. Then I
> will try to research doing the same with LLDB, exporting needed
> libraries and headers for the compiler withing llvm and lldb.

For the cross reference.

A patch allowing to build (tested on NetBSD) out of sources pushed to
review: reviews.llvm.org/D15067
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWW96JAAoJEEuzCOmwLnZsCLAP/0LrhGlzivOjtykjW3ywvXia
wtZRLYsPwsNBJJERdOGVOJVPovnT02H+Bf1a4eDf0dJXbecklyfiupNfthlvFr9l
PxCLZI4GQPLcP+jqWbhcFRdhzFeyEnLLy0Wjt1MNYG0s3m2u4jJM2ViNLA10/kwS
XX82e2K7q5MUb51MMEJ09ufpYyGff7XmjVE78w1ekfNSRlKFMc0DNBsaIx4oKZfM
G2IUtRNL59ad2pkw/xA3D2OPtoTk7+a2jjF8Z4nYY6kUSyBPUlCYrjyfavVCreR6
6Zo2E3lkkEb6PSIfb57RlMtxBIfmIBjv5w6OcFjSK6aYvffY9IMgyBJvGbdA+Ee7
DlCFZax25eJPglEnfzAI2XOHOUQJtDwhb45N+XWshLfUax2e52KJvj9nq9J8pOse
AC00qRQN+KTZsil43dlOfEn5m18mJ9o+CohK5eLMoTnS9QdtP8OEv72zGjOsSqrx
vXDx01ziuQRCgsJ+niZXHgRLA65hxD5XgSGEBzr5prRLtU6q6V/HpYOsC46+pySc
ibLrRWHnaeBVJknwz11iBo4gBZRk3lGhi5aTfu9+kcX6ylKSn2nn34+HGHr//FZi
SrKcb3z7WikAR0c9cHBNOnwbro6o08j8zUE2l2S08risLRDDu01KBo3yFebjHz8D
vQqFJNDkRLywQbXezcjB
=7C7K
-----END PGP SIGNATURE-----