This change allows top-level scripts to determine which
toolchain was used by Boost.Build engine bootstrap process.
Top-level script of Boost C++ Libraries will be updated
separately.
Minor changes in feature.py.
Prevent hard error when creating a property from string,
in case string references an unknown feature.
Removed unused var.
Add support for --hash.
Removed porting error which flattens property set into strings.
Fix tag rule for searched libs.
Resurrect c++-template-depth feature.
Fix some porting errors in msvc.py. Created a new action which
allows us to change sources for target as well as decide on
the actions name at the last moment. This is nee
Fix some porting errors in common.py.
Ported boost.jam module.
Fix syntax errors in rc.py and midl.py.
Fix a bug causing invalid composite features due to a missing
expand call.
Fix mixed slash/backslash in actions.
Fix some trivial syntax/runtime errors in stage.py.
Fix increasing indent when running --debug-generators.
If we have to wait for, e.g. 65 jobs, first we create a thread which waits for first 63.
The remaining two can be waited on by the same WFMO call which waits for thread
completion. This will avoid creating 2 threads in this case.
Windows WaitForMultipleObjects() can wait on max. 64 handles. This limitation is overcome by splitting the handle set into parts which are of adequate size, and spawning a thread which does the waiting.
It needs further work, to avoid $prefix/share/boost-build/src
and put everything directly under $prefix/share/boost-build
and to put examples under $prefix/share/doc/boost-build or
similar.
Since history has been rewritten on that branch, and
since rewriting history on 'master' is kinda unnecessary
excercise, I've manually created a commit that has current
tips of both 'master' and 'develop' as parents, but uses tree
from 'develop' with no modifications, using this:
git commit-tree cb54f66965
-p 87098597c0
-p dc428e2ab3
It might have been possible to force 'git merge' to do same,
but I could not figure it out.
