2
0
mirror of https://github.com/boostorg/python.git synced 2026-01-19 16:32:16 +00:00

improved comments in-line

[SVN r22628]
This commit is contained in:
Dave Abrahams
2004-04-11 12:07:18 +00:00
parent 79c7d736f0
commit 17b0c819e4
3 changed files with 40 additions and 3 deletions

View File

@@ -1,4 +1,6 @@
# This is the Jamfile for Boost.Build v2, which is currently in
# prerelease. Ignore this file unless you are a bleading edge sort of
# person.
use-project /boost/python : ../build ;
project

View File

@@ -1,7 +1,29 @@
# Copyright David Abrahams 2003. See accompanying LICENSE for terms
# and conditions of use.
# Edit this path to point at the root directory of your Boost
# installation. Absolute paths work, too.
# If you move this example from its place in the Boost tree, edit this
# path to point at the root directory of your Boost installation (the
# one containing a subdirectory called "boost/" and a sub-subdirectory
# "boost/python/" that contains .hpp files. Absolute paths work, too.
path-global BOOST_ROOT : ../../.. ;
# Boost.Python configuration variables, as described in
# http://www.boost.org/libs/python/doc/building.html. Usually you
# don't need to set these; the defaults will work. If you do set
# them, try to change as few of them as possible, starting with the
# first ones.
# PYTHON_VERSION = <the two-part Major.Minor version number, e.g. 2.2> ;
# PYTHON_ROOT = <path to root directory of your Python installation> ;
# PYTHON_INCLUDES = <path to Python #include directories> ;
# PYTHON_LIB_PATH = <path to Python library object> ;
# You may need to configure your compiler toolset, especially if you
# want to build with a compiler that is not the "system default" or if
# it is installed in a nonstandard place; see
# http://www.boost.org/more/getting_started.html#Configuring for
# details.
# Makes a project id for boost so that other Boost.Build projects can
# refer to it by name.
project boost : $(BOOST_ROOT) ;

View File

@@ -4,3 +4,16 @@ 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
-sVARIABLENAME=value
or in the local Jamrules file.
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
boost-build.jam.