Boost logo

Boost-Build :

From: Larry Evans (cppljevans_at_[hidden])
Date: 2004-05-18 12:41:21


On 05/17/2004 05:21 AM, Vladimir Prus wrote:
> Larry Evans wrote:
[snip]
>>
> I suggest that you add "<hardcode-dll-paths>true" to the requirements of
> project in "managed_ptr/test". That would do the necessary magic.
Yep, I tried it and it works.
Thanks Vladimir.

IMO v2/boost_build_v2.html#using_libraries would be clearer if it
mentioned this requirement right after the code snippet, as follows.
<---------------------------

exe app : app.cpp ../lib/lib1//lib1 ;

In addition, the project requirements needs "<hardcode-dll-paths>true".

>---------------------------

However, I also see that:

v2/boost_build_v2.html#static_shared

claims:

Further, only gcc compiler supports this option.

yet, the location:

v2/boost_build_v2.html#builtins_features

claims:

When this property is on, usage requirements for each library will
include additional dll-path propertry, with the path the the generated
library file. This allows to run executables without placing all the
dependent libraries to a single location.

which doesn't mention gcc. Which is correct? Also, after some minor
corrections, this would read:

When this property is on, usage requirements for each library will
include an additional dll-path property, with the path being the
generated library file. This allows running executables without
placing all the dependent libraries at a single location.

However, even with the above corrections, I can't decipher:

with the path being the generated library file

because I'm unsure how the the library file is "generated".

Could you explain further or maybe correct my "correction" to
this paragraph?

BTW, I think this documentation is a lot clearer than previous docs I
read (several months ago).

Thanks for the good work.

Regards,

Larry

 


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