[lldb-dev] Exclusively build and install LLDB?

Kamil Rytarowski via lldb-dev lldb-dev at lists.llvm.org
Thu Nov 26 15:57:17 PST 2015


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

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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWV5xaAAoJEEuzCOmwLnZsgp4P/AwEFmITXpwolEfTkrGjaYIA
rRAqEkwkNjynN2vKEJYIZWOTxmFpjV/8bih8nCpWozirEAhssa7fD58D3cfO9wKT
8DLLf4bs4DCHfhWgbW9DDjkrjdevUOqAgte6bDN5toOwhNxR5RmCLfepWIpQ8HXj
4nGJ3DRl9CL4nZgO3WEGdkXI6xZY/55MmwXxQI9u5zU/RA+5iPmzm5iJIvMhyTNX
ULGJ1OgIBefj6XOfJ9CT7Y+l6vpv300m5uFmO4iqU9VbY5bQmyGf3CpDEYIteSXs
3axJ879pwv3kw9OoJC8ihOEYlk4aBjaGyoBflfGLS0Dk6ZikWk1jJ/qbPFapT0fA
rov2N+i1FS4+gApCo50ADQpkwCddvnmjNYo7/xNyFJLvKdODh/JxphmoiaG2gv68
QlkvZtAx53ahvD2M76nW2vZu9Mm3JEKd58uTkE36w6Res+xSuICuM2rirAMk9Xqp
28UZl2WhZcDCEAL+gmgxr84ThI9w/gRzqZ13I9Bifefim0V4bIrD+bhaodwlx3mI
j/YQpd2wZpwphzP7nnc+5ZBltpMgtuzI+CaJXpntONj4VUoPeVHrX4boPdczZAZx
JBNlKdXx0QHsOVUshbfK/Cz47oybnOEee0NE+4QlYVbkFXaYrB4Thu7OY5i+04Dd
UzBETcNz7IrnFpI7WjNv
=tiYf
-----END PGP SIGNATURE-----


More information about the lldb-dev mailing list