* python.jam (python-test-generator.run): Set dependency
on other python sources only for the result, not for
extension module.
Set ARGS variable on capture-output.
[SVN r35609]
alias foo : [ run a.cpp ] ;
and
exe main : main.cpp [ lib helpers : helpers.cpp ] ;
Now inline targets are marked explicit, so that they are not
build unless requested, and for the alias target, the names
of inline targets are not qualified by the name of top-level target.
build/
* alias.jam (alias): Pass 'no-renaming' to
target.main-target-sources.
* target.jam (main-target-sources): New parameter
'no-renaming'. Make inline target explicit.
* builtin.jam (lib): Declare 'result' variable,
to avoid implicit declaration of a global one.
tools/
* testing.jam (test-suite): Make synonymous with 'alias'.
test/
* inline.py: Adjust to the fact that alias no longer
changes names of inline targets. Check that inline
targets are explicit.
[SVN r35607]
when generating PCH. When an action generated two targets, target
variables must be set on both, on just on the first one.
Patch from Franz Schnyder.
tools/
* msvc.jam (compile.c++): Call get-rspline on all 'targets',
to implicitly verify there's just one element.
(compile.c.pch): Call get-rspline on all targets.
(compile.c++.pch): Likewise.
[SVN r35605]
Notable changes:
1. There's no need to cast header to the PCHHEADER type.
2. There are two separate type "C_PCH" and "CPP_PCH", that
use C and C++ compilation respectively.
Most of the patch sumbitted by Ilya Sokolov.
tools/
* builtin.jam (class dummy-generator): New.
* gcc.jam: Override extension of the PCH type.
(class gcc-pch-generator): New.
Register generators for C_PCH and CPP_PCH.
(compile.c++.pch, compile.c.pch): New.
* msvc.jam (class msvc-pch-generator): New.
Register generators for C_PCH and CPP_PCH.
* pch.jam: Remove 'PCHHEADER' type.
(pch-generator): Fail unlress it's used at top-level
generator.
Register catch-all produce-nothing generators for PCH-less
toolsets.
[SVN r35508]
This option increases the amount of heap / stack space available
to bjam when it runs. By default on IBM SP2 clusters, the available
stack is limited to 256 Mb which is insufficient for building larger
applications.
-bmaxdata=<num>
Sets the maximum size of the area shared by the
static data (both initialized and uninitialized)
and the heap to <num> bytes. The default is
-bmaxdata=0.
[SVN r35323]
when specified as a relative path,
e.g. path-global BOOST_ROOT : ../../boost
The fix should not interfere with the build of the boost library at all.
If there are problems though, simply remove everything between
<speedsnail> ... </speedsnail> again, and drop me a note.
[SVN r35305]
