Subject: [Boost-build] Building boost shared libraries with their paths embedded?
From: Bruce Stephens (bruce.r.stephens_at_[hidden])
Date: 2012-05-11 13:58:33
We build most of our shared libraries knowing their installed
That means when we link programs against them (in the build tree) those
programs won't actually work until all the libraries are installed
(without convoluted fiddling with LD_LIBRARY_PATH, I guess), but that's
Is it possible (easily) to build boost libraries like that? Currently it
seems that on Darwin (for example) that can't happen easily:
actions link.dll bind LIBRARIES
"$(CONFIG_COMMAND)" -dynamiclib -Wl,-single_module -install_name
"$(<:B)$(<:S)" -L"$(LINKPATH)" -o "$(<)" "$(>)" "$(LIBRARIES)"
-l$(FINDLIBS-SA) -l$(FINDLIBS-ST) $(FRAMEWORK_PATH)
-framework$(_)$(FRAMEWORK:D=:S=) $(OPTIONS) $(USER_OPTIONS)
so by the looks of it -install_name gets passed the bare library name,
not the path. And that seems to match my experience of trying to build
programs: after I've linked them, they don't know where to find boost
Am I missing something, or is this how it's supposed to be?
I know that if we used Boost.Build to build everything that we could use
dll-path and things to fix this, but changing our build system in this
way is very unlikely. Much more likely is that I'd hack the link rules
for the various platforms we care about so that they embed the path in
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk