* New feature <relevant> which is automatically deduced in most cases.
* Features which are not relevant do not affect target paths and
do not prevent merging of virtual targets.
* generators.jam: generator.run always returns usage-requirements
to allow usage-requirements in non-top-level generators. This
is necessary because we're using usage-requirements to track
relevance from flags.
* New rule toolset.uses-features to specify features that the rule
checks manually, instead of using toolset.flags. In the future,
we should consider restricting the properties actually passed,
to detect errors.
* Adjust tests to handle the new paths (verified by inspection).
* Add temporary option --ignore-relevance to consider all features relevant
to aid migration.
* New rule property.evaluate-conditional-relevance which helps tracking
relevance in <conditional>.
* Widely scattered changes to use the new interfaces.
* Fixed `build.bat` stack overflow on some machines by splitting up to several files
* CSharp script simplified and now will check VC++ toolset version
This allows building with Visual Studio "15", expected to be released
in 2017. Tested with Visual Studio "15" Preview 3. The compiler itself is the
same as with Visual Studio 2015 Update 3, but if only Visual Studio "15" is
installed, the compiler could not be found.
The previous code would do parts of Windows Store support initialization
using 'default-path', and would fail in all cases where that returns false,
in particular for 12.0_xp version.
This patch moves that code to a different place, where explicit initialization
path is available.
This patch makes <suppress-import-lib> property
take effect as telling Boost.Build that no
import lib will be created.
Actually, I think the name is not good enough.
Also, it appears that NOENTRY is orthogonal to
import lib.
1. Fixing up a bit how the phone setup script location is calculated.
2. Reusing generate-setup-cmd rule in configure-really to avoid duplication and make cleaner.
3. Adding some more comments explaining.
MSVC setup scripts are very slow, so should not be used in build actions directly.
Rewrite these scripts into their fast equivalents and use those instead.
Add toolset initialization option <rewrite-setup-script> to customize/disable this new behavior.
1. Adds a new feature <windows-api> for specifying the WINAPI_FAMILY API set to target. Defaults to desktop, which is how builds before my changes.
2. A few small changes for adding ARM support.
3. Changes to call to correct vcvars setup script for Windows Phone 8.
