Hi, I have finally got my head round boost::python and I'm loving it. I am on Ubuntu Hardy, stackless python 2.5, gcc 4.2.3. Two questions: 1) When using bjam to build libraries which expose C++ classes and functions to python, how can I use bjam to output the built libraries into a different folder to /bin/gcc-4.2.3/debug? 2) is this actually a debug library? if so, how do I create release versions? Many thanks Simon
Simon Pickles wrote:
Hi,
I have finally got my head round boost::python and I'm loving it. I am on Ubuntu Hardy, stackless python 2.5, gcc 4.2.3.
Two questions:
1) When using bjam to build libraries which expose C++ classes and functions to python, how can I use bjam to output the built libraries into a different folder to /bin/gcc-4.2.3/debug? You could probaly use the install rule.
2) is this actually a debug library? if so, how do I create release versions?
Yes. Usually to create a release version you simply do %bjam release you can add "-n" to see what bjam will do before it actually does anything
Many thanks
Simon _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
-- Sébastien Fortier
Sébastien Fortier wrote:
Simon Pickles wrote:
Hi,
I have finally got my head round boost::python and I'm loving it. I am on Ubuntu Hardy, stackless python 2.5, gcc 4.2.3.
Two questions:
1) When using bjam to build libraries which expose C++ classes and functions to python, how can I use bjam to output the built libraries into a different folder to /bin/gcc-4.2.3/debug? You could probaly use the install rule.
Could you elaborate? I am having trouble understanding bjam. Never used any jam before you see.
2) is this actually a debug library? if so, how do I create release versions?
Yes. Usually to create a release version you simply do %bjam release
you can add "-n" to see what bjam will do before it actually does anything
Many thanks
Simon _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
--
Sébastien Fortier
------------------------------------------------------------------------
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
the install rule is explained here. http://www.boost.org/doc/tools/build/doc/html/bbv2/tasks/installing.html So basically in your Jamfile you define an install rule so that when you do bjam install, it wil copy the built files to specific locations. In my project I have the folowwing setup Jamroot [contains general info + custom help] ExeDir Jamfile [contains info on exe target + install for the exe] Library1Dir Jamfile [contains info on exe target + install for the library] Library2Dir Jamfile [contains info on exe target + install for the library] take a look a the boost distribution folder... [snip] Sébastien Fortier p.s. I'm not sure but I think you should adress these questions to the boost build mailing list.
AMDG Simon Pickles wrote:
1) When using bjam to build libraries which expose C++ classes and functions to python, how can I use bjam to output the built libraries into a different folder to /bin/gcc-4.2.3/debug? You could probaly use the install rule. Could you elaborate? I am having trouble understanding bjam. Never used any jam before you see.
For example lib foo : foo.cpp ; install dist : foo ; copies foo into the directory dist. See http://www.boost.org/doc/tools/build/doc/html/bbv2/tasks/installing.html for more details. In Christ, Steven Watanabe
participants (3)
-
Simon Pickles -
Steven Watanabe -
Sébastien Fortier