[pkg-boost-devel] Bug#619766: Bug#619766: libboost1.46-dev: hardcode-dll-paths feature is missing

Romain Bossart romain.bossart at free.fr
Thu Mar 31 07:00:02 UTC 2011


Thanks Steve, I agree with your explanation. For further information, this 
use-case is mentionned as useful here, in the second paragraph:


When developping, especially if you have a fairly large number of libraries 
(about 40 libs in my case), updating the search paths is tedious. Tedious also 
to deploy libraries and executables before even trying to run them. In a word, 
run-in-place is often useful, and the hardcode- feature is already here to 
handle that.

More details [personal]:

Boost.Build also separates targets built with different compilers (gcc and icc 
for instance) in different folders: bin/gcc-4.6.0/release, 
bin/gcc-c++0x/release, bin/icc/release, etc. When developping, with BB you just 
have to run in place each executable in its own folder, it will be linked to the 
appropriate libraries.

In other words, the harcode-dll-paths feature lets you focus on code and code 
partitioning, relieving you from the details of build dependencies and runtime 
linking. This feature exists and is completely automatic. On installed targets, 
those details are handled by the linker + traditional search paths, on built 
targets, you have the hardcode-dll-paths feature.

Maybe CMake makes things as simple as BB. I'm just saying that if the 
hardcode-dll-paths is removed in the debian distribution, BB loses a cool 
feature, included by default by the BB developpers.

Does this post clarify things a bit?


On 03/31/2011 02:56 AM, Steve M. Robbins wrote:
> Hi,
> On Tue, Mar 29, 2011 at 03:12:31PM +0200, Olaf van der Spek wrote:
>>> This feature is really useful for developpers.
>> Why?
> My understanding of the use-case is: suppose you are using
> Boost.Build to build a project that contains a library
> as well as an executable linked with that lib.  If the
> library is built as a shared object, the hardcode-dll-paths
> lets you build and run the executable in-place.
> I'm Cc'ing the bug submitter for further clarification.
> Regards,
> -Steve

More information about the pkg-boost-devel mailing list