mirror of
https://github.com/boostorg/build.git
synced 2026-02-14 12:42:11 +00:00
e5d385d390
* property-set now considers <conditional> to be conditional * property.evaluate-conditionals-in-context now handles indirect conditionals as well. This is the correct behavior for all places where evaluate-conditionals-in-context is currently used. * Indirect conditionals now translate paths relative to the project in which they were defined, not relative to the current project. * usage-requirements no longer use targets.evaluate-requirements, as the iterative algorithm is completely unnecessary (It's also wrong, since the new features shouldn't be applied to the evaluation context). * indirect conditionals are removed from the property set when they are evaluated, just list regular conditionals. (This is a consequence of passing them through evaluate-conditionals-in-context) * This also allows non-free features in usage-requirements to "work" again (for some definition of work).
Boost.Build =========== See the Boost.Build website at https://boost.org/build. See the `guidelines for contributing <./CONTRIBUTING.rst>`__.