Boost logo

Boost-Build :

Subject: Re: [Boost-build] --build-type=complete
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2011-04-01 10:36:19


On 03/29/2011 06:25 PM, Dave Abrahams wrote:
> At Tue, 29 Mar 2011 17:27:10 -0700,
> Steven Watanabe wrote:
>> On 03/28/2011 01:05 PM, Dave Abrahams wrote:
>>> I'm finding that if I build Boost on Windows with
>>> --build-type=complete I don't get statically-linkable binaries for
>>> anything but Boost.Test. To get a "real" complete build, I'm using
>>> debug release
>>> threading=multi/link=shared,static/runtime-link=shared
>>> threading=multi,single/link=static/runtime-link=static
>>> on the command line. Is this intended?
>> It works for me with the trunk and iostreams only.
>> (bjam --with-iostreams --buld-type=complete)
>> I also tried with 1.46.0 (bjam --buld-type=complete -j8)
>> Both were with msvc-10.0express.
>> a) What is the exact command that you
>> used which didn't work?
> Trying to reconstruct it; I think this is accurate:
> bjam --user-config=I:\\user-config.jam --build-dir=I:\\1_46_1-installer\\build --stagedir=I:\\1_46_1-installer\\stage --debug-configuration -j2 --build-type=complete stage toolset=msvc-10.0express,msvc-9.0express,msvc-8.0express,msvc-7.1

Well, I still can't reproduce it. I can't duplicate this
exactly, but I did try with multiple toolsets, and I'm
still getting static libraries. So, either ther's
something interesting in your user-config.jam, or one of
the toolsets I don't have or MPI is causing a problem,
or something else I haven't thought of. I might be
able to trace this if you can provide the output
with --debug-building (It'll be huge. I usually use
--with-iostreams to test the build scripts just to
limit the amount I have to deal with.).

In Christ,
Steven Watanabe

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at