Am 30.04.2015 um 13:57 schrieb Olaf van der Spek:
On Mon, Apr 6, 2015 at 4:08 PM, Olaf van der Spek
wrote: On Mon, Apr 6, 2015 at 3:53 PM, Beman Dawes
wrote: No. I'm rerunning now with --build-type=complete
Failed, with the same errors you reported.
That's a cautionary tale!
Marshall,
We need to start asking RC testers to use --build-type=complete
Why doesn't it default to complete (on Windows)? Where's build-type documented anyway?
All I found was " For instructions on how to build only specific variants, please ask on the Boost.Build mailing list."
Somebody?
You can call "b2 --help" (or "bjam --help") in the Boost-source directory and will get the information you are looking for: --build-type=<type> Build the specified pre-defined set of variations of the libraries. Note, that which variants get built depends on what each library supports. -- minimal -- (default) Builds a minimal set of variants. On Windows, these are static multithreaded libraries in debug and release modes, using shared runtime. On Linux, these are static and shared multithreaded libraries in release mode. -- complete -- Build all possible variations. Additionally, you might find some more useful information about boost.build here: http://www.boost.org/build/doc/html/bbv2/overview.html Best regards, Deniz