https://bitcointalk.org/index.php?topic=258618
Using -mt-1_52 instead of -mt-s-1_52 as it can be compiled with the --build-type=minimal boost option saving space and time.
https://bitcointalk.org/index.php?topic=258618
Using -mt-1_52 instead of -mt-s-1_52 as it can be compiled with the --build-type=minimal boost option saving space and time.
https://bitcointalk.org/index.php?topic=258618
Using -mt-1_52 instead of -mt-s-1_52 as it can be compiled with the --build-type=minimal boost option saving space and time.
Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/bc06d51f837717943e9720575196be23335b96d6 for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.
AFAIK -s is need because we have a static boos library, -d of course seems wrong.
From boost-win32.yml:
./bjam toolset=gcc target-os=windows threadapi=win32 threading=multi variant=release link=static --user-config=user-config.jam --without-mpi --without-python -sNO_BZIP2=1 -sNO_ZLIB=1 --layout=tagged --build-type=complete $MAKEOPTS stage
AFAIK -s is need because we have a static boos library, -d of course seems wrong.
--build-type=minimal outputs only a single library version with the -s- oppressed - at the advantage of being a little faster. It seems the library is identical. The cost is less clarity without the -s- tag so I will close this pull request and create a new one with -s-
b2.exe --build-type=minimal --with-chrono --with-filesystem --with-program_options --with-system --with-thread^ --layout=versioned^ -sNO_BZIP2=1^ -sNO_ZLIB=1^ variant=release^ toolset=gcc^ link=static^ threading=multi^ target-os=windows^ threadapi=win32^ cxxflags="%ADDITIONALCCFLAGS%"^ cflags="%ADDITIONALCCFLAGS%"^ stage