-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 i can't locate it in the docs where it explains how not to build the debug libs, i found it where i could exlude certain libs, build oooonly some, or build not the threaded libs, if i missed it a kind nudge in the right direction would be appreciated, or if not in docs, a simple sample option to bjam would be highly appreciated thank you in advance for your efforts Daniel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCXcSmUpKYMelfdYERAibsAJ9Rh3nSBWCDPWI4xs28//8M0BxExACdEOo0 6k14l84CKaEeMwORIRdxvDM= =HHCY -----END PGP SIGNATURE-----
Daniel Goller wrote:
i can't locate it in the docs where it explains how not to build the debug libs, i found it where i could exlude certain libs, build oooonly some, or build not the threaded libs, if i missed it a kind nudge in the right direction would be appreciated, or if not in docs, a simple sample option to bjam would be highly appreciated
See http://www.boost.org/more/getting_started.html#Build_Install especially the text below the table. Or more specifically http://www.boost.org/tools/build/v1/build_system.htm#build For example: "bjam -sTOOLS=gcc -sBUILD=release". HTH, Markus
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Markus Schöpflin wrote: | Daniel Goller wrote: | |> i can't locate it in the docs where it explains how not to build the |> debug libs, i found it where i could exlude certain libs, build oooonly |> some, or build not the threaded libs, if i missed it a kind nudge in the |> right direction would be appreciated, or if not in docs, a simple sample |> option to bjam would be highly appreciated | | | See | | http://www.boost.org/more/getting_started.html#Build_Install | | especially the text below the table. Or more specifically | | http://www.boost.org/tools/build/v1/build_system.htm#build | | For example: "bjam -sTOOLS=gcc -sBUILD=release". thanks, looking at what that builds and what bjam builds on default would it be correct to say -sBUILD="release debug <threading>multi" is what bjam builds if -sBUILD is ommited (default)? | | HTH, Markus | | _______________________________________________ | Boost-users mailing list | Boost-users@lists.boost.org | http://lists.boost.org/mailman/listinfo.cgi/boost-users | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCXyjfUpKYMelfdYERAr6+AJ0eq8srD2v4eh1DcsmXBHQqpfthcgCfUFfj ofLkQKwq1/vb2Oq6XGxIHmc= =ashH -----END PGP SIGNATURE-----
Daniel Goller wrote:
thanks, looking at what that builds and what bjam builds on default would it be correct to say -sBUILD="release debug <threading>multi" is what bjam builds if -sBUILD is ommited (default)?
No. What it builds by default, at least the default at the boost-root, is either: "debug release <runtime-link>static/dynamic <threading>single/multi" when building on Windows, or "debug release <runtime-link>dynamic <threading>single/multi" otherwise. But depending on your system, and what the individual libraries support, some of those 16 combinations will not get built. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - Grafik/jabber.org
participants (3)
-
Daniel Goller -
Markus Schöpflin -
Rene Rivera