python.jam:
Support for the specification of "_d" extension suffix.
In compute-default-paths, fixed the check for residence in
a "PCBuild.*" directory so we can build against Windows Python built
in a source distribution.
common.jam:
Fixed generation of the "y" tag to look for <python-debugging>on
rather than the whole debug-python build variant.
Fixed some grammar and spelling.
virtual-target.jam:
Added the ability to forego the prepending of "." to a
generated-target-suffix by specifying the suffix enclosed in <...>
libs/python/build/Jamfile.v2:
#define BOOST_DEBUG_PYTHON when <python-debugging>on
[SVN r37326]
target. My explanation from a mail to Martin Wille:
IIUC, your
configuration looks like:
using python : 2.4 : ... ;
using python : 2.4 : ... : : : <toolset>gcc <toolset-gcc:version>4.1.2_linux_x86_64 ;
using python : 2.4 : ... : : : <toolset>gcc <toolset-gcc:version>4.1.0_linux_x86_64 ;
The intention is of course that the latter pythons will be used in
preference to the former one if their conditions are matched more
explicitly.
We are using the "flags" rule to directly associate the interpreter
command with targets being built, provided the condition passed is
matched.
# Set up the PYTHON variable to point at the interpreter.
flags python.capture-output PYTHON $(condition:J=/) : $(interpreter-cmd) ;
Here's an excerpt of docs for the condition parameter on flags:
condition * : # A condition when this flag should be applied.
# Should be set of property sets. If one of
# those property sets is contained in build
# properties, the flag will be used.
So what happens is that, because it's less specific, the flags
invocation for the first python matches when either of the latter
pythons was supposed to match, and the PYTHON variable that is used to
hold the interpreter command on the testing target accumulates both
interpreters.
We have a mechanism for "choose the closest property match," but it
doesn't apply to the flags rule: it's target alternatives. Since we
define target alternatives for the python library anyway, I think I
can handle this by creating a property to hold the interpreter command
and associating it with the appropriate target alternative, then
keying off *that* command to set up flags.
[SVN r37272]
Make path-to-native work on zero or more paths, which simplifies lots
of code.
Factor native path translation out of compute-default-paths and into its caller.
Remove the path-to-native translation on the prefix from
candidate-interpreters, as the passed prefix has to be native anyway.
Fix the capturing of the exec_prefix for use in setting dll-path for
windows targets.
[SVN r37255]
* add ".lib" to the target name for libpython. *** This is a kluge!
I don't know why it should be necessary ***, but when I was
inserting debugging code that did
ECHO [ $(target).name ] ;
it would always drop the 2nd digit, e.g. python-2.4 would come out
as "python-2". This change prevented it.
* Fixed spelling and grammar in comments
* Fix the incorrect assumption in capture-output that only one Python
extension will participate (also in tools/build/v2/testing.jam).
[SVN r37215]
libs/python/test/Jamfile.v2:
* add dynamically-linked embedding test
* fix builtin_converters test so it can work (BBv1 allowed the
duplication of main target names; BBv2 does not)
libs/python/test/import_.cpp: move some more of the Python code within
a handle_exception callback so at least we can better diagnose
failures.
[SVN r37214]
