Hi, Forwarding this question to boost-users as it applies to Boost.Python and Boost.Build in equal measure. Regards, Paul

______________________________________________ From: Bilokon, Paul Sent: Wednesday, April 30, 2008 3:07 PM To: 'boost-build@lists.boost.org' Subject: Using Boost.Build with Boost.Python: Three Questions; "Copy" Rule

Hi,

I would be very much obliged if you could share your insights on the following three questions:

(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?

(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?

(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)?

Sorry if my questions have obvious answers; I did read through the documentation and check the related resources on the Web.

Many thanks for your help.

Regards, Paul

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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.