of the 'toolset.configure' framework. The new rule supports two special
version values:
- 'all': configures all detected versions of Visual C++ with default
settings;
- 'default': configure the default detected version of Visual C++. It
prefers newer versions to older ones.
'msvc.init' is still completely valid and should be used until
'toolset.configure' will be introduced. 'msvc.init' provides the same
functionality as 'msvc.configure' does.
Patch from Alexey Pakhunov.
[SVN r31093]
of the 'toolset.configure' framework. The new rule supports two special
version values:
- 'all': configures all detected versions of Visual C++ with default
settings;
- 'default': configure the default detected version of Visual C++. It
prefers newer versions to older ones.
'msvc.init' is still completely valid and should be used until
'toolset.configure' will be introduced. 'msvc.init' provides the same
functionality as 'msvc.configure' does.
Patch from Alexey Pakhunov.
[SVN r31093]
targets. In that case, we used to create a long list of targets and searched
it whenever new target is registered. Now the list is for each path/name
combination, so is much shorter.
[SVN r31054]
targets. In that case, we used to create a long list of targets and searched
it whenever new target is registered. Now the list is for each path/name
combination, so is much shorter.
[SVN r31054]
Patch from Alexey Pakhunov.
What this patch does is allows to match absense of optional feature in
the 'flags' rule. For example:
flags msvc .SETUP <architecture>/<address-model>64 : " x86_amd64" ;
flags msvc .SETUP <architecture>ia64/<address-model> : " x86_ia64" ;
This will produce "x86_amd64" when the <address-model> is set to 64
and <architecture> is not set. Likewise, for <architecture>ia64 and unset
address model.
Without this patch, we'd have two choices:
- adding 'default' to the list of feature values. But that would
add 'architecture-default' to the target path. Ick!
- creating top-level variable .SETUP with default value, and only
matching configurations with fully-specified feature values. But
this won't handle the case above: we really need to check
which one of two features is unspecified.
[SVN r31036]
Patch from Alexey Pakhunov.
What this patch does is allows to match absense of optional feature in
the 'flags' rule. For example:
flags msvc .SETUP <architecture>/<address-model>64 : " x86_amd64" ;
flags msvc .SETUP <architecture>ia64/<address-model> : " x86_ia64" ;
This will produce "x86_amd64" when the <address-model> is set to 64
and <architecture> is not set. Likewise, for <architecture>ia64 and unset
address model.
Without this patch, we'd have two choices:
- adding 'default' to the list of feature values. But that would
add 'architecture-default' to the target path. Ick!
- creating top-level variable .SETUP with default value, and only
matching configurations with fully-specified feature values. But
this won't handle the case above: we really need to check
which one of two features is unspecified.
[SVN r31036]
