How to build only these binaries?
I want to only build both debug and release statically linked binaries. What are the build options to build just these on windows, linux and mac? To clarify, binaries which would link directly inside my executable (the libs that won't need any dll or so). On windows I am using /MT in my projects, so the libs should also statically link to msvc runtime. When using --build-type=complete it generates 5GB of binaries, which for 32-bit and 64-bit on windows, mac and linux together ends up taking a lot more space than I can afford.
To build static libs use "link=static" option and use --with-xxxxx ot --without-xxxxx to build or exclude libs you want., where xxxxx is lib name like "regex" or "serialization" etc. -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Sachin Garg Sent: Friday, October 03, 2008 12:32 PM To: boost-users@lists.boost.org Subject: [Boost-users] How to build only these binaries? I want to only build both debug and release statically linked binaries. What are the build options to build just these on windows, linux and mac? To clarify, binaries which would link directly inside my executable (the libs that won't need any dll or so). On windows I am using /MT in my projects, so the libs should also statically link to msvc runtime. When using --build-type=complete it generates 5GB of binaries, which for 32-bit and 64-bit on windows, mac and linux together ends up taking a lot more space than I can afford. _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Oh well and use --help to get more.... -----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Sachin Garg Sent: Friday, October 03, 2008 12:32 PM To: boost-users@lists.boost.org Subject: [Boost-users] How to build only these binaries? I want to only build both debug and release statically linked binaries. What are the build options to build just these on windows, linux and mac? To clarify, binaries which would link directly inside my executable (the libs that won't need any dll or so). On windows I am using /MT in my projects, so the libs should also statically link to msvc runtime. When using --build-type=complete it generates 5GB of binaries, which for 32-bit and 64-bit on windows, mac and linux together ends up taking a lot more space than I can afford. _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
Thanks, I can use a little more help on understanding the --help output :)
My understanding of --help output is that,
For getting both release and debug static windows binaries (with /MT)
I need to do
release debug link=static runtime-link=static
And for linux/mac build, I should be using
release debug link=static runtime-link=shared
(Because, IMHO, on linux the c++ runtime shouldn't be linked
statically, right? And I am guessing Mac works a bit like linux).
Is it ok to specify both debug and release like that? And I am
assuming that threading=multi is the default, so doesn't needs to be
specified. And is my syntax correct, because the --help output says
"<link>static" etc and I am not sure what this syntax means.
My complete command line will look like, on windows,
bjam release debug link=static runtime-link=static
--stagedir=".\win_x86" stage
My apologies if I am sounding stupid, but do let me know if I am
missing something.
Thanks again.
On Fri, Oct 3, 2008 at 10:16 PM, Terdale, Shantibhushan
AMDG Sachin Garg wrote:
Is it ok to specify both debug and release like that?
Sure.
The default is both threading=single and threading=multi.
And is my syntax correct, because the --help output says "<link>static" etc and I am not sure what this syntax means.
Your syntax is correct. The <link>static syntax is used inside Jamfiles. In Christ, Steven Watanabe
and what about single-threaded builds? when are they really needed? As far as I understand, by default multi-threaded variant is used. Single-threaded variant is used when: 1) we need some extra performance 2) we are sure just one thread will use the particular library am I right? Thanks.
participants (4)
-
Roman Shmelev -
Sachin Garg -
Steven Watanabe -
Terdale, Shantibhushan