Hello Dave,
I finally got a little bit of time to investigate recent strange behavior on the VeecoFTC regression tester and found that the build jamfile for the context library is halting Boost.Build during the regression tests. It appears that, when it can't find an appropriate architecture to use, it actually generates an argument error in try-one-generator-really. I attached the output of the bjam.log and perhaps it will be useful for investigating. Let me know if you would like me to try anything.
cross-compiling is a little bit problematic. Please note that Windows CE on ARM is not supported yet (if I find time I'll implement the calling conventions for this platform). File libs/context/config/x86.cpp identifies the x86 architecture (your cross-compiler environment is required to simulate WinCE on x86). x86.cpp contains macros defined by several compilers for x86. Regarding to http://msdn.microsoft.com/en-us/library/aa449784.aspx Windows CE defines _M_IX86 for this purpose - but this macro is already contained by x86.cpp - therefore I assume that your cross-compiler env. is not correct/complete. Maybe you can write a little test-app checking for this macro: #include <iostream> int main( int argc, char * argv[]) { #if defined (_M_IX86) std::cout << "_M_IX86 defined\n"; #else std::cout << "_M_IX86 not defined\n"; #endif return 0; } regards, Oliver