I'm not completely sure this is precisely the right fix:
a. The error message used to reference a non-existent variable.
What was it supposed to be?
b. Should property.remove et. al. be able to cope with conditional
properties?
[SVN r18023]
- Added XML catalog support (finally!). The DocBook XSL stylesheet and DTD
directories can be specified via "using boostbook : xsl-dir : dtd-dir ; "
in any BBv2 configuration file, or via command line parameters/environment
variants DOCBOOK_XSL_DIR and DOCBOOK_DTD_DIR, respectively.
user-config.jam:
- Add "using boostbook" example
[SVN r17983]
* new/build-request.jam
(directly-requested-properties-adjuster): Redo.
* new/targets.jam
(main-target.generate-really): Adjust properties here.
* new/virtual-target.jam
(register-actual-name): New rule.
(virtual-target.actualize-no-scanner): Call the above, to detected bugs,
where two virtual target correspond to one Jam target name.
[SVN r17955]
* new/targets.jam
(generate): Use a special string to report failure, not just return
of empty list.
(basic-target.generate-sources): Accomodate the above change.
(basic-target.check-for-unused-sources): Allow empty list of targets.
* test/alternatives.py: New test.
[SVN r17906]
* new/property.jam
(split-conditional): New rule
(translate-paths): Use the above to handle conditional properties.
* test/path_features.py: New tests.
[SVN r17881]
unconditionally.
* new/builtin.jam
(linking-generator.run): New rule. Sets dependency on <library>
properties.
* new/generators.jam
(construct): Do not handle usage requirements. Do not handle
dependency features in any way.
* new/targets.jam
(main-target.generate-really): Don't create/set subvariant-dg.
(basic-target.generate): Collect usage requirements. Create/set
subvariant-dg.
* new/virtual-target.jam
(subvariant-dg): Take actual build properties together with
requested ones.
[SVN r17813]
property-set instances, because of different order.
* new/property-set.jam
(create): Sort the properties.
* new/feature.jam:
(minimize): Bugfix.
[SVN r17812]
* new/targets.jam
(main-target.apply-default-build): Call
'build-request.expand-no-defaults', not 'expand'. The motivation
is to have defaults added in one place: 'property-set.add-defaults'.
Also handle the case where default-build is empty.
(main-target.generate): Apply defaults here. The motivation is
that if we're using default build, default features should be
applied here as well, or else we'll get ambiguous alternatives.
(basic-target.generate): Do not add defaults.
[SVN r17755]
default value will always be present in build properties of all
main targets. The change moves adding default value into main
targets --- it was done at the top level.
* new/build-request.jam
(expand-no-defaults): No longer local.
* new/build-system.jam
Use 'build-request.expand-no-defaults', not 'expand'.
* new/feature.jam
(add-defaults): Tolerate conditional properties
(e.g <variant>debug:<define>DEBUG)
* new/property-set.jam
(property-set.add-defaults): New method.
* new/targets.jam
(basic-target.final-properties): Add defaults.
* test/default_features.py: New test.
[SVN r17753]
