05-08-2012 02:07 PM - edited 05-08-2012 02:08 PM
No, I haven't and I didn't bother because I got 1.42 working fairly well now. I had a quick look but figured the way bjam works was changed for some reason.
BTW: One thing I forgot. boost/detail/endian.hpp needs to be updated to support ARM:
#elif defined(__i386__) || defined(__alpha__) \
|| defined(_M_X64) || defined(__bfin__) \
// Add it here:
# define BOOST_LITTLE_ENDIAN
# define BOOST_BYTE_ORDER 1234
I think this might also be true for later versions.
05-21-2012 06:20 PM
Here's the bjam setup I'm using. If you discovered a better configuration please lest me know.
bjam -a -q -j4 --prefix=%DRIVE%\boost --build-type=minimal --build-dir=%DRIVE%\boostBuild_%BOOSTVER% --layout=system toolset=qcc target-os=qnxnto threadapi=pthread --
variant=release link=static threading=multi runtime-link=shared --without-python --without-mpi install >build.log 2>&1