Subject: Re: [Boost-bugs] [Boost C++ Libraries] #1744: [getting started] No information on building static libraries with bjam under Windows
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-06-27 00:18:54
#1744: [getting started] No information on building static libraries with bjam
under Windows
-------------------------------+--------------------------------------------
Reporter: tychom_at_[hidden] | Owner: grafik
Type: Bugs | Status: new
Milestone: Boost 1.36.0 | Component: Documentation
Version: Boost 1.35.0 | Severity: Problem
Resolution: | Keywords: bjam build static windows
-------------------------------+--------------------------------------------
Comment (by grafik):
Replying to [comment:14 dave]:
> Replying to [comment:12 grafik]:
> > Replying to [comment:9 dave]:
> > > What about
> > >
> > > * Change the single variant we build and the autolink code to be
consistent with the docs
> > > * Change the single variant we build and the docs to be consistent
with the autolink code
> > >
> >
> > Because the `link=static` variant is not the most widely used one,
AFAIK.
>
> Wait a sec; that reasoning doesn't address the 2nd bullet in my list of
two, does it? I presume that autolink doesn't specify static libs by
default?
You presume incorrectly ;-) Currently autolink defaults to link=static.
And hence matches the docs. Or rather the docs match autolink. Which is
why I asked about the risk of changing the autolink code at this point. I
think it's a high risk to do so now. And it's why I'm suggesting building
both link=static and link=shared as the "quick fix".
Hm, I should check precisely what is the default for autolink.
--
Ticket URL: <http://svn.boost.org/trac/boost/ticket/1744#comment:15>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:49:58 UTC