other unsupported platforms like Itanium gracefully fail - your build env is broken because you build WinCE for x86 but _M_X86 is not defined (but MSDN describes that it should - see link in my previous post). Am 03.12.2012 05:24 schrieb "David Deakins" <ddeakins@veeco.com>:
On 12/2/2012 10:10 AM, Oliver Kowalke wrote:
The _M_IX86 is not defined.
do you compile for ARM vor X86?
However, I am actually less concerned about whether or not Boost.Context
is functional on WinCE/ARM. What doesn't seem right is that Boost.Context is aborting the entire regression test sequence by generating a run-time error in the jamfilile.
the jam file dos not special things, it provides only the alternatives. you can specify --without-context in order to exclude context from build.
This problem is actually occurring as part of the automated trunk regression testing, not a local build, so it is slightly more inconvenient to specifically exclude this library from the test suite.
However, I think there is a fairly simple fix to allow the build of Boost.Context to fail gracefully in the event that the architecture is unsupported. Supplying a default 'fall back' alias for asm_context_sources to be used when no other alias matches should keep the Boost.Build file from throwing an hard error. Please see the attached patch.
Thanks, -Dave
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost