From: David Abrahams (dave_at_[hidden])
Date: 2004-08-23 10:23:09
Vladimir Prus <ghost_at_[hidden]> writes:
> for quite some time, the <link-runtime>static option was broken on gcc. Some
> investigation revelated that this options is not completely separate from
> <link>static. If an application uses DLLs in some way, it should link to the
> shared runtime (specifically, libc).
> There's a email discussion between me and a libc maintainer that I base this
> view on:
> Based on that, I've modified gcc.jam so that it issues a reasonable error
> message if the user tries to use <link-runtime>static with DLLs.
Does this apply to gcc on all platforms, or just ELF/Linux?
I can't tell from the thread whether this is the issue, but: although
there are similar guidelines under Windows, if you are careful about
resource management it's possible to use the static runtime with
> If everything's OK, the '-static' option is added. As the result,
> it's now really possible to create all-static binaries on gcc with
> I've also removed the code which tries to distinguish between static
> and shared searched library. I don't think that code was very robust
> or even used.
-- Dave Abrahams Boost Consulting http://www.boost-consulting.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