Core changes:
- Multiple improvements in Python port, from Aaron Boman.
- Clearer error reporting for target name clases and invalid
metatarget references, from Vladimir Prus.
Visual Studio:
- Initial support for Windows 8 phone and store applications,
from Steve Gates.
- Faster builds, via caching setup script invocations,
from Juraj Ivančić.
- Support for custom DLL manifests and dlls without import libraries,
from Bernhard B.
Tools:
- Improved clang support, from Edward Diener.
- Support for Intel 15, from John Maddock.
This patch fixes 3 issues:
- Adds support for Intel-15 so MSVC version can be auto-selected.
- Changes GLOB to path.glob as for some reason the GLOB rule always
fails when used in this context (discovered when testing this patch).
- Changes selection logic for target-types variable - previous code
used the value of PROCESSOR_ARCHITECTURE to detect this, but that
appears to only tell you which sub-system bjam is running in. For
example on my system bjam is a 32-bit app (default for an msvc build),
but I only have the Intel 64-bit compiler installed (under /intel64/).
New logic checks whether the intel64 compiler exists and uses that if
it is - Intel's installer won't install this on 32 bit platforms in
which case the glob fails and things fall back to the ia32-intel64
cross compiler when address-model=64 is specified.
- create a b2.<whatever> index for O(1) package/module searching.
- make the .pyc's sit next to their respective files; preventing
pollution of workspace
- restore the __file__ variable for imported files
- prevent importing the same module twice under two separate names;
also preventing running initialization code twice (registering types
and features)
- create an __init__.py for the contrib directory
- requires Python 2.3 or newer for pkgutil
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.
When docutils is not configured at all, produce an
error message as opposed to trying to invoke Python
without providing a script to run.
Even better would be to search for docutils in common
places, and do so even without explicit 'using', but that's
beyond 30 mins I have right now.
Unbreak msvc initialization with versions less than 11.
There was an incorrect condition causing a search for phone support to be run, and fail,
on msvc versions known not to have such support in the first place.
