Subject: Re: [Boost-build] Baffling build properties
From: Dave Abrahams (dave_at_[hidden])
Date: 2010-11-18 04:56:58
On Thu, Nov 18, 2010 at 4:12 AM, Lars Viklund <zao_at_[hidden]> wrote:
> On Thu, Nov 18, 2010 at 02:44:17AM -0500, David Abrahams wrote:
>> Hmm... something looks fishy about the properties set up for
>> --build-type=complete in Jamroot. Seems like <link> and
>> <runtime-link> are supposed to always have the same value, but Jamroot
>> isn't ensuring that.
> Your assertion sounds incorrect to me.
> There is nothing wrong about having a dynamic runtime for a static
> library. Forcing dynamic linking of a library just because you have a
> dynamic runtime would be highly annoying, and unnecessary.
Understood, but IIUC --build-type=complete doesn't generate static
libraries that link to the dynamic runtime. Humm...
Reviewing what the BoostPro installer puts on the disk (carefully,
this time!) I see
threading=multi debug link=shared runtime-link=shared
threading=multi release link=shared runtime-link=shared
threading=multi release link=static runtime-link=shared
threading=multi debug link=static runtime-link=shared
threading=multi release link=static runtime-link=static
threading=multi debug link=static runtime-link=static
threading=single release link=static runtime-link=static
threading=single debug link=static runtime-link=static
which looks like the following build request to me:
However, that doesn't seem to be what the code in Jamroot is doing.
-- Dave Abrahams BoostPro Computing http://www.boostpro.com
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk