Update of /cvsroot/boost/boost/libs/python/example
In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv29097/libs/python/example
Modified Files:
Tag: RC_1_34_0
README
Added Files:
Tag: RC_1_34_0
Jamroot
Log Message:
Fully switch to BBv2
--- NEW FILE: Jamroot ---
# Copyright David Abrahams 2006. Distributed under the Boost
# Software License, Version 1.0. (See accompanying
# file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
# Specify the path to the Boost project. If you move this project,
# adjust this path to refer to the Boost root directory.
use-project boost
: ../../.. ;
# Set up the project-wide requirements that everything uses the
# boost_python library from the project whose global ID is
# /boost/python.
project
: requirements <library>/boost/python//boost_python ;
# Declare the three extension modules. You can specify multiple
# source files after the colon separated by spaces.
python-extension getting_started1 : getting_started1.cpp ;
python-extension getting_started2 : getting_started2.cpp ;
python-extension std_pair_ext : std_pair.cpp ;
# A little "rule" (function) to clean up the syntax of declaring tests
# of these extension modules.
local rule run-test ( test-name : sources + )
{
import testing ;
testing.make-test run-pyd : $(sources) : : $(test-name) ;
}
# Declare test targets
run-test test1 : getting_started1 test_getting_started1.py ;
run-test test2 : getting_started2 test_getting_started2.py ;
run-test test3 : std_pair_ext test_std_pair.py ;
# A target that runs all the tests
alias test : test1 test2 test3 ;
# Don't run tests by default
explicit test test1 test2 test3 ;
Index: README
===================================================================
RCS file: /cvsroot/boost/boost/libs/python/example/README,v
retrieving revision 1.6.12.1
retrieving revision 1.6.12.2
diff -u -d -r1.6.12.1 -r1.6.12.2
--- README 20 Sep 2006 22:49:17 -0000 1.6.12.1
+++ README 11 Dec 2006 05:22:04 -0000 1.6.12.2
@@ -3,21 +3,14 @@
.. file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
To get started with the Boost Python Library, use the examples
-getting_started1.cpp and getting_started2.cpp.
-
- bjam -sTOOLS=your-toolset test
-
-in this directory will build and run the examples.
-
-Other configuration variables may need to be set as described in
-http://www.boost.org/libs/python/doc/building.html. These can be
-supplied by the environment, on the command-line with
+getting_started1.cpp and getting_started2.cpp. Invoking
- -sVARIABLENAME=value
+ bjam --toolset=your-toolset test
-or in the local Jamrules file.
+in this directory will build and run the examples. See
+http://www.boost.org/more/getting_started.html for details about the
+--toolset= option.
If you move this example from its place in the Boost development tree
-you'll need to edit at least one line in Jamrules and one line in
+you'll need to edit the two lines indicated in Jamroot and
boost-build.jam.
-
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Boost-cvs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/boost-cvs
