From: Vladimir Prus (ghost_at_[hidden])
Date: 2006-10-06 04:44:40
On Friday 06 October 2006 10:10, K. Noel Belcourt wrote:
> I have an install rule like this
> for local p in $(projects)
> install stage-lib-$(p)
> : $(p)
> : <dll-path>$(install-dir)/lib
> # <install-dependencies>on
> 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 try
> 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 minimal
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.
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