Add version number to common-variant-tag from <version> property.
Change common-names to only return the common-variant-tag for temporary compatability.
[SVN r20822]
* Modified Python testing code to use the facilities of testing.jam,
so that it can be processed with process_jam_log
* Updated Python library tests to use a test suite
* Added Python test suite to status/Jamfile
* Added --run-all-tests option to force tests to run even when up-to-date.
Also,
boost-base.jam:
Added some missing rule signatures
RUN_LD_LIBRARY_PATH became LINK_LIBPATH because it was only really
used during linking.
Reformed the movement of path variables up the dependency graph
Removed the defunct Run rule
Set up generalized constants for path manipulation
darwin-tools.jam, gcc-tools.jam:
use LINK_LIBPATH
python.jam:
Reformed the choice of Python executable
testing.jam:
Refactored testing code so it could be used for Python
Now building all environment variable setup code ahead of time
RUN_TEST became TEST_EXE
[SVN r20815]
(link.dll) : -soname is not accepted by solaris LD. Using -h allows
it to work with GNU LD and solaris LD (and presumably others).
Patch from Andre Hentz.
[SVN r20750]
* Realign the toolset path determination to the changes made in the gcc
toolset (upon which the sunpro toolset is based).
* Updates the documentation:
- matches the changes in the toolset
- adds version specific compatibility information
[SVN r20711]
* tools/builtin.jam
(linking-generator): Move <library> properties to sources in the 'run'
method. This makes the logic usable by everyone who invokes the generator.
(exe-target-class, lib-target-class): Don't do the above.
[SVN r20707]
two version of library just because it's used by both console and gui
application.
Probably, a better approach would be to make 'user-interface' feature
irrelevant to all targets except for exe, but that requires some design
and coding.
Patch from Brock Peabody.
[SVN r20699]
* Set the proper suffix for shared libraries
* Added C and C++ compile options used in v1:
-Wno-long-double, -no-cpp-precomp, and -fcoalesce-templates
* Converted the link.dll rule to use the bundled libtool
* Added support for linking to frameworks
Patch from Christopher Currie.
[SVN r20695]
we need to bypass <library-path> property, as well.
* tools/builtin.jam
(lib-target-class.compute-usage-requirements): The above change.
* build/virtual-target.jam
(subvariant.set-usage-requirements, subvariant.usege-requirements):
New methods.
(abstract-file-target.dg): Don't allow changing the value.
* build/targets.jam
(basic-target.generate): Explicitly don't change value of 'dg'.
[SVN r20655]
rules which create corresponding EXE/LIB targets.
The drawback with the previous approach, where there was a separate generator
for RSP file, was that the list of consumable target types is different,
depending on main target which uses RSP, and it's hard to express this
information.
* tools/builtin.jam
(response-file): Move to...
* tools/common.jam: Here.
* tools/msvc.jam
* tools/borland.jam
Split 'link' rule into 'link' and 'link.dll'. Call 'response-file'
from rules.
* tools/stage.jam
Fix a bug which cause RSP file to be staged incorrectly.
[SVN r20650]
