$include_dir="/home/hyper-archives/boost-build/include"; include("$include_dir/msg-header.inc") ?>
From: Rene Rivera (grafik.list_at_[hidden])
Date: 2003-12-20 18:09:06
Bronek Kozicki wrote:
> On Sat, 20 Dec 2003 15:27:25 -0600, Rene Rivera wrote:
> [...]
> Many thanks for full explanation!
>
>
>>No. It only builds one version for each target, that links against the dynamic
>>C++ runtime.
>
>
> Does it mean that all (or some ?) boost libraries are built with 2
> targets (static library and dynamic library) ?
Most are built with 2 targets.
>And of course it doesn't
> make sense to build dynamic library linked statically to runtime.
That one is up for discussion as you saw from John's, Dave's, and my posts.
Dave and I hold that it does make sense under some small set of circumstances.
>> * debug, runtime-link-static, threading-single (base)
>
>
> Hm, if I call bjam -sTOOLS=mingw -sBUILD="release debug", I get this:
>
> boost_date_time.dll\mingw\debug\boost_date_time-mgw-d-1_31.lib
> boost_date_time.dll\mingw\debug\boost_date_time-mgw-d-1_31.dll
> boost_date_time.dll\mingw\release\boost_date_time-mgw-1_31.lib
> boost_date_time.dll\mingw\release\boost_date_time-mgw-1_31.dll
> libboost_date_time.lib\mingw\debug\libboost_date_time-mgw-d-1_31.lib
> libboost_date_time.lib\mingw\release\libboost_date_time-mgw-1_31.lib
>
> which would mean that base is runtime-link-dynamic ?
Oops, you are correct... my mistake there :-)
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera_at_[hidden] - grafik_at_[hidden] - 102708583_at_icq