From: K. Noel Belcourt (kbelco_at_[hidden])
Date: 2006-10-07 16:26:28
On Oct 7, 2006, at 1:39 PM, K. Noel Belcourt wrote:
> On Oct 6, 2006, at 2:44 AM, Vladimir Prus wrote:
>> On Friday 06 October 2006 10:10, K. Noel Belcourt wrote:
>>> When I use it to install shared libraries, I find that only the
>>> shared libraries defined in the project sources are installed.
>>> But I
>>> want to install the shared libraries in the project sources plus any
>>> shared libraries they depend on. I tried using <install-
>>> dependencies>on, but it appears to hang bjam (ran for two+ hours, no
>>> change in memory footprint). Also, does enabling the install
>>> dependencies property figure out the dependencies just based on the
>>> <install-type> properties present in the install rule, or does it
>>> to identify all the header, source and library dependencies?
>> <install-dependencies>on is supposed to find all Boost.Build
>> targets that
>> sources of 'install' rule depend on, in any way. Then, they are
>> filtered by
>> target type and installed.
>> This won't handle searched libraries -- since Boost.Build don't
>> know how
>> linker searches for them, and won't handle header dependencies.
>> If <install-dependencies>on hangs for you, please try to create a
>> example and send it to me. Alternatively, you can run bjam -d+5 and
>> send me
>> the output. But watch out -- the output can quickly can get very
>> large. You
>> might want to run the tail command to get last 10000 lines of the
>> output. If
>> there's hang in some rule, last lines should show it.
Use anonymous ftp to ftp.sandia.gov. cd to pub/kbelco. There should
be a file last_10k_lines.log.
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