[Boost-build] Using the install rule with a pre-built library

Subject: [Boost-build] Using the install rule with a pre-built library
From: Peter Fry (pbf_at_[hidden])
Date: 2013-02-28 23:29:16

Hi everyone,

I'm trying to build an executable project on RedHat EL6, using an install
rule to deploy it's executable to an artefacts directory. Since it requires
another project's shared library to execute, I would also like to use an
install rule to deploy the pre-built shared library into my project's
artefacts folder. In case it's material, I'm using Boost.Build 2011.12-svn.

I've found that if I set-up the pre-built library using the <file> feature,
it works as expected. However, when I change to the use <name> and <search>,
it doesn't copy the file.

This will (hopefully) make more sense with an example. Here's a cut-down and
contrived version, to demonstrate what I'm trying to do.

The pre-built library is configured in
/some_source_location/project1/jamroot:

The project I'm trying build is defined in
/another_source_location/project2/jamroot:

This works fine, however if I changed MyLib_Works to MyLib_Fail, it doesn't
copy the file.

I presume it's because it's not converted MyLib into the platform specific
libMyLib.so?

I would like to use the <name> and <search> version, since I use a
<conditional> rule to generate the search path depending upon the variant
and address-model. I would also like to have bjam turn the name into a
platform-specific one (i.e. libMyLib.so on Linux, MyLib.dll on Windows),
rather than hard-code it.

Anyone have any ideas?

Peter.

--
View this message in context: http://boost.2283326.n4.nabble.com/Using-the-install-rule-with-a-pre-built-library-tp4643631.html
Sent from the Boost - Build mailing list archive at Nabble.com.