Why file_system build on msvc 6.5 is only dynamic?
Hi All I got filesyetm from the CVS and build it using bjam (no args with VCVARS32.BAT of msvc 6.5) Only the folder: runtime-link-dynamic was created under bin/lisbfs.lib/msvc. Other libraies (i.e. thread) build by default also runtime-link-static. What should I do to do the build with static run time library? Thanks Daniel
"Daniel Yerushalmi" <yg-boost-users@m.gmane.org> writes:
Hi All I got filesyetm from the CVS and build it using bjam (no args with VCVARS32.BAT of msvc 6.5)
Only the folder: runtime-link-dynamic was created under bin/lisbfs.lib/msvc. Other libraies (i.e. thread) build by default also runtime-link-static.
What should I do to do the build with static run time library?
bjam -sBUILD="<runtime-link>dynamic" ...whatever... should work. -- David Abrahams dave@boost-consulting.com * http://www.boost-consulting.com Boost support, enhancements, training, and commercial distribution
"David Abrahams" <dave@boost-consulting.com> wrote in message news:u7ke5ohze.fsf@boost-consulting.com...
"Daniel Yerushalmi" <yg-boost-users@m.gmane.org> writes:
Hi All I got filesyetm from the CVS and build it using bjam (no args with VCVARS32.BAT of msvc 6.5)
Only the folder: runtime-link-dynamic was created under bin/lisbfs.lib/msvc. Other libraies (i.e. thread) build by default also runtime-link-static.
What should I do to do the build with static run time library?
bjam -sBUILD="<runtime-link>dynamic" ...whatever...
should work. Thanks it worked (I used bjam -sBUILD="<runtime-link>static")
but now I want to build the filesystem using the multi-threaded run time library (static version). In the thread library the created path is: boost_thread.lib\msvc\debug\runtime-link-static\threading-multi (The difference is that the default library is LIBCD - in the way it is build now and maybe the compiler switch are not OK) I want to do something equivalant... (in my opinion it should by default to build all the four (eight including debug/release) option.... ) (I tried to read the build system doc but it is rather long :( )
-- David Abrahams dave@boost-consulting.com * http://www.boost-consulting.com Boost support, enhancements, training, and commercial distribution
Info: <http://www.boost.org> Wiki: <http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl> Unsubscribe: <mailto:boost-users-unsubscribe@yahoogroups.com>
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
"Daniel Yerushalmi" <yg-boost-users@m.gmane.org> writes:
"David Abrahams" <dave@boost-consulting.com> wrote in message news:u7ke5ohze.fsf@boost-consulting.com...
"Daniel Yerushalmi" <yg-boost-users@m.gmane.org> writes:
Hi All I got filesyetm from the CVS and build it using bjam (no args with VCVARS32.BAT of msvc 6.5)
Only the folder: runtime-link-dynamic was created under bin/lisbfs.lib/msvc. Other libraies (i.e. thread) build by default also runtime-link-static.
What should I do to do the build with static run time library?
bjam -sBUILD="<runtime-link>dynamic" ...whatever...
should work. Thanks it worked (I used bjam -sBUILD="<runtime-link>static")
Uh, right, sorry.
but now I want to build the filesystem using the multi-threaded run time library (static version).
-sBUILD="<runtime-link>static/<threading>multi"
In the thread library the created path is: boost_thread.lib\msvc\debug\runtime-link-static\threading-multi
(The difference is that the default library is LIBCD - in the way it is build now and maybe the compiler switch are not OK)
I don't know what you mean by that.
I want to do something equivalant... (in my opinion it should by default to build all the four (eight including debug/release) option.... )
Talk to Beman about it; he's the filesystem guy. BTW I'm pretty sure there are only six combinations, since the DLL runtime is always MT-enabled.
(I tried to read the build system doc but it is rather long :( )
I'll try to help, but my patience may be proportional to your willingness to read the docs ;-) -- David Abrahams dave@boost-consulting.com * http://www.boost-consulting.com Boost support, enhancements, training, and commercial distribution
At 05:29 PM 12/19/2002, David Abrahams wrote:
"Daniel Yerushalmi" <yg-boost-users@m.gmane.org> writes:
...
I want to do something equivalant... (in my opinion it should by default to build all the four (eight including debug/release) option.... )
Talk to Beman about it; he's the filesystem guy. BTW I'm pretty sure there are only six combinations, since the DLL runtime is always MT-enabled.
I don't think the issue of exactly which libraries (all six, fewer?) to build is an isolated filesystem issue. Rather, it is part of the larger install issue. By that I mean that we now have a good way to do builds, and it will get even better with Boost.Build V2. But to some extent, that is a capability, not a complete solution. The complete solution would deliver a completely installed set of libraries, ready to go for your compiler. At first glance, that seems easy. But remember that most of the expectation-raising examples we are all familiar with work for only one compiler and one operating system, and are custom-built for that compiler and O/S. So a general solution is a tough nut to crack. --Beman
"Beman Dawes" <bdawes@acm.org> wrote in message news:4.3.2.7.2.20021219221810.01ac1910@mailhost.esva.net...
At 05:29 PM 12/19/2002, David Abrahams wrote:
"Daniel Yerushalmi" <yg-boost-users@m.gmane.org> writes:
...
I want to do something equivalant... (in my opinion it should by default to build all the four (eight including debug/release) option.... )
Talk to Beman about it; he's the filesystem guy. BTW I'm pretty sure there are only six combinations, since the DLL runtime is always MT-enabled.
I don't think the issue of exactly which libraries (all six, fewer?) to build is an isolated filesystem issue.
Rather, it is part of the larger install issue.
By that I mean that we now have a good way to do builds, and it will get even better with Boost.Build V2. But to some extent, that is a capability, not a complete solution. The complete solution would deliver a completely installed set of libraries, ready to go for your compiler.
At first glance, that seems easy. But remember that most of the expectation-raising examples we are all familiar with work for only one compiler and one operating system, and are custom-built for that compiler and O/S. So a general solution is a tough nut to crack.
--Beman
Info: <http://www.boost.org> Wiki: <http://www.crystalclearsoftware.com/cgi-bin/boost_wiki/wiki.pl> Unsubscribe: <mailto:boost-users-unsubscribe@yahoogroups.com>
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
participants (1)
-
Beman Dawes -
Daniel Yerushalmi -
David Abrahams