From: Markus Schöpflin (markus.schoepflin_at_[hidden])
Date: 2002-12-04 04:48:02
Vladimir Prus wrote:
> I'm in process of implementing new system libraries interface and
> have a couple of question on runtime-link feature.
> 1. What should it do? Will it affect the way toolset runtime is linked,
> or default linking for all system libraries.
I think the runtime-link feature is most important on WIN32 platforms
where it selects the approriate C runtime library to link to. (Single
threaded lib, multi threaded lib or multi threaded dll.) IMO this
shouldn't be mixed with default linking of system libraries. I have no
idea if this feature is relevant for any other platform, but for WIN32
it's absolutely essential.
> 2. Why it's symmetric in V1? I'm using V2 quite extensively now
> (though on small projects), and I got accustomed to paths like
> I certainly don't want "runtime-link-dynamic" to be added to this
> nice path!
I don't known an answer for this question but I could imagine it's
because it is so incredibly important on WIN32 platforms. Under normal
circumstances you never ever want to mix different runtime link models
because you usually end up with different heaps for your memory.
Thinking further about this, there are circumstances where it is ok to
mix different runtime link models, if you know what you are doing. So
we probably need a way to say the following: I'm building an exe
(using <runtime-link>dynamic) but I want to link to another lib I've
built which uses <runtime-link>static. Will this be possible?
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