diff --git a/build/Attic/python_v1.zip b/build/Attic/python_v1.zip deleted file mode 100644 index 0377a07b..00000000 Binary files a/build/Attic/python_v1.zip and /dev/null differ diff --git a/doc/building.html b/doc/building.html index 815c66d1..c664ba61 100644 --- a/doc/building.html +++ b/doc/building.html @@ -18,28 +18,28 @@
Boost.Python requires Python 2.21 or newer.
+Boost.Python requires Python 2.21 or newer.
There are two basic models for combining C++ and Python:
Since Boost.Python is a separately-compiled (as opposed to header-only) library, its user relies on the services of a Boost.Python library binary. The Boost Getting Started Guide @@ -89,12 +89,12 @@ to a file, so you can see what your build system needs to do.
The Boost.Python binary comes in both static and dynamic flavors. Take care to choose the right flavor for your application.2
The dynamic library is the safest and most-versatile choice:
It might be appropriate to use the static Boost.Python library in any of the following cases:
As described in the Boost.Build reference manual, a file called user-config.jam in your home -directory (%HOMEDRIVE%%HOMEPATH% on Windows) is used to +directory7 is used to describe the build resources available to the build system. You'll need to tell it about your Python installation.
Users of Unix-Variant OSes
If you are using a unix-variant OS and you ran Boost's configure script, it may have generated a -user-config.jam for you.4 If your configure/make sequence was successful and Boost.Python binaries +user-config.jam for you.4 If your configure/make sequence was successful and Boost.Python binaries were built, your user-config.jam file is probably already correct.
If you have a fairly “standard” python installation for your platform, there's very little you need to do to describe it. -Simply adding
+Simply havingimport toolset : using ; using python ;-
to a user-config.jam file in your home directory6 -should be enough.
+in a user-config.jam file in your home directory7 +should be enough.6
On the other hand, if you have several versions of Python installed, or Python is installed in an unusual way, you may want to supply any or all of the following optional parameters to @@ -194,7 +194,7 @@ distribution (Ubuntu Feisty Fawn) has a specially configured
Note that in the examples below, case and especially whitespace are significant.
You can set up your user-config.jam so a bjam built under Windows -can build/test both windows and cygwin python extensions. Just pass +can build/test both Windows and Cygwin python extensions. Just pass <target-os>cygwin in the condition parameter for the cygwin python installation:
@@ -244,12 +244,12 @@ using python ; using python : : c:\\cygwin\\bin\\python2.5 : : : <target-os>cygwin ;
when you put target-os=cygwin in your build request, it should build -with the cygwin version of python:5
+with the cygwin version of python:5bjam target-os=cygwin toolset=gcc
This is supposed to work the other way, too (targeting windows -python with a cygwin bjam) but it seems as though the support in +python with a Cygwin bjam) but it seems as though the support in Boost.Build's toolsets for building that way is broken at the time of this writing.
| [1] | Note that although we tested earlier versions of + |
| [1] | Note that although we tested earlier versions of Boost.Python with Python 2.2, and we don't think we've done anything to break compatibility, this release of Boost.Python may not have been tested with versions of Python earlier than @@ -317,7 +317,7 @@ happens. |
| [4] | configure overwrites the existing + |
| [4] | configure overwrites the existing user-config.jam in your home directory (if any) after making a backup of the old version. |
| [5] | Note that the <target-os>cygwin feature is + |
| [5] | Note that the <target-os>cygwin feature is different from the <flavor>cygwin subfeature of the gcc toolset, and you might need handle both explicitly if you also have a MinGW GCC installed. |
| [6] | Create the user-config.jam file if you don't +already have one. |
| [6] | Create the user-config.jam file if you don't -already have one. For Windows users, the home directory can -be found by typing: + |
| [7] | (1, 2) Windows users, your home directory can be +found by typing: ECHO %HOMEDRIVE%%HOMEPATH%@@ -350,7 +356,7 @@ ECHO %HOMEDRIVE%%HOMEPATH% diff --git a/doc/building.rst b/doc/building.rst index 1d31d2f7..9ee245f8 100644 --- a/doc/building.rst +++ b/doc/building.rst @@ -141,7 +141,7 @@ Configuring Boost.Build As described in the `Boost.Build reference manual`__, a file called ``user-config.jam`` in your home -directory (``%HOMEDRIVE%%HOMEPATH%`` on Windows) is used to +directory [#home-dir]_ is used to describe the build resources available to the build system. You'll need to tell it about your Python installation. @@ -161,14 +161,14 @@ The Basics If you have a fairly “standard” python installation for your platform, there's very little you need to do to describe it. -Simply adding :: +Simply having :: - import toolset : using ; + import toolset : using ; using python ; -to a ``user-config.jam`` file in your home directory [#home-dir]_ -should be enough. +in a ``user-config.jam`` file in your home directory [#home-dir]_ +should be enough. [#user-config.jam]_ Advanced Configuration ---------------------- @@ -254,7 +254,7 @@ significant. ; - You can set up your user-config.jam so a bjam built under Windows - can build/test both windows and cygwin python extensions. Just pass + can build/test both Windows and Cygwin_ python extensions. Just pass `` |