#45251: request for lldb --------------------------+---------------------- Reporter: rjvbertin@… | Owner: larryv@… Type: request | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: lldb | --------------------------+---------------------- Comment (by jeremyhu@…):
a redistributable libclang
I'm ok with splitting up the port and would be happy do to so if we can avoid build time regressions and setup sane dependencies. I don't like the current situation in which clang rebuilds libLLVM.dylib at build time instead of using llvm-config to find the installed one to build and link against.
The change basically locks the dylibs to their intended location; is there anything wrong with that?
If that is needed, it should be addressed as a patch to the build system that can be integrated upstream. Using install_name_tool can introduce a dependency on cctools, which is a pain point as it can cause a dependncy cycle (eg: building clang-3.7 on Leopard requires us to build two older llvm versions in order to bootstrap the process: llvm-3.3 -> cctools -> llvm-3.4 -> ld64 -> clang-3.4 -> llvm-3.7 -> clang-3.7).
Should we assume that it's up to the dependent software to add the path to libclang to its rpath?
Let's track that in a separate bug (I filed #52196). I'm of the opinion that `llvm-config --ldflags` should "do the right thing" but it doesn't setup rpath. -- Ticket URL: <https://trac.macports.org/ticket/45251#comment:27> MacPorts <https://www.macports.org/> Ports system for macOS