Boost logo

Boost-Build :

From: Bilokon, Paul (paul.bilokon_at_[hidden])
Date: 2008-05-08 09:55:17

P.S. It appears that my question is related to this one, which hasn't been answered:

Many thanks,

-----Original Message-----
From: Bilokon, Paul
Sent: Thursday, May 08, 2008 2:08 PM
To: 'Boost.Build developer's and user's list'
Subject: RE: [Boost-build] Using Boost.Build with Boost.Python: Three Questions; "Copy" Rule

Hi Jurko,

Many thanks for your help. This answers almost all of my questions. I have one problem though.

I need to copy (a Python test harness for the Python extension "hello") to each variant of the build directory:

(project root)\build\msvc-8.0\debug\link-static\threading-multi\
(project root)\build\msvc-8.0\release\link-static\threading-multi\

How can I achieve this using the builtin install rule? I've tried a number of things, but a copy of the file doesn't appear.

Many thanks once again!

Best wishes,

-----Original Message-----
From: boost-build-bounces_at_[hidden] [mailto:boost-build-bounces_at_[hidden]] On Behalf Of Jurko Gospodnetic
Sent: Friday, May 02, 2008 12:09 PM
To: boost-build_at_[hidden]
Subject: Re: [Boost-build] Using Boost.Build with Boost.Python: Three Questions; "Copy" Rule

   Hi Paul.

> (1) Is it at all possible to change the location of the "bin" folder
> for my project or is it hardcoded? (bjam generates a number of files
> under (project root)/bin/msvc-8.0/debug and (project
> root)/bin/msvc-8.0/release. If so, what is the "correct" (good
> practice) way of achieving this?

   You can specify it either for your project target (see
as in:

     project my-project : build-dir C:\Haleluya

or you can specify it using the --build-dir command line option (see

> (2) I am using Boost.Build with Boost.Python. The generated files are
> linked to boost_python-vc80-mt-gd-1_34_1.dll (debug) and
> boost_python-vc80-mt-gd-1_34_1.dll (release). But then I'm using
> install bin : hello : <location>$(dist-dir)/debug <variant>debug ;
> install bin : hello : <location>$(dist-dir)/release <variant>release ;
> in Jamroot to dist the files. The DLLs do not get copied to the dist
> location (nor do they appear under "bin"). How can I instruct bjam to
> copy the DLLs?

   Depends what your 'hello' target does. Did you try running 'bjam hello variant=debug' and 'bjam hello variant=release'? Did that create the DLL files you need? If it did not then the install target got no such DLL targets as sources...

> (3) On a related note, is there a "copy" rule in Boost.Build (very
> much along the lines of the similar Ant rule), which would copy my
> supporting Python files to $(dist-dir)?

   I believe that the install rule (a.k.a. stage) you are using is exactly what you need. :-)

   Hope this helps.

   Best regards,
     Jurko Gospodnetiæ

Unsubscribe & other changes:
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

This message is intended only for the personal and confidential use of the designated recipient(s) named above. If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited. This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers. Email transmission cannot be guaranteed to be secure or error-free. Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such. All information is subject to change without notice.

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at