Re: [Boost-bugs] [Boost C++ Libraries] #1744: Change in default build variants broke "Getting Started"

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #1744: Change in default build variants broke "Getting Started"
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2008-07-09 09:00:03

#1744: Change in default build variants broke "Getting Started"
-------------------------------+--------------------------------------------
  Reporter:  tychom_at_[hidden]  |       Owner:  grafik                   
      Type:  Bugs              |      Status:  reopened                 
 Milestone:  Boost 1.36.0      |   Component:  build                    
   Version:  Boost 1.35.0      |    Severity:  Regression               
Resolution:                    |    Keywords:  bjam build static windows
-------------------------------+--------------------------------------------

Comment(by dave):

 Replying to [comment:12 grafik]:
 > Replying to [comment:9 dave]:
 > > Well, that's an embarrassment!
 >
 > To say the least :-(
 >
 > > 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. Note, I have no real personal opinion as to which one to default to
 other than trying to satisfy the majority ;-)

 I guess I was thrown by Rene's answer here, which seemed like an answer to
 a "why...?" question...

 > > I guess it goes without saying that inexperienced first-time users
 need the most help.
 >
 > Very true. And this is why we decided the single default to be
 link=shared, because the variant that seemed to be used by most third
 party applications and libraries that use Boost. Which, from the
 experience answering how to build, is what I got asked about most often.
 I.e. the most common question I get is "I'm trying to build X which wants
 Boost library Y.dll/so. How do I build that?". And this is from sitting on
 IRC for two years now. Which is where many such new users end up asking.

 ...which reminds me why the GSG used static libs when we were building
 both kinds: one less chance of problems such as failure to set
 {{{LD_LIBRARY_PATH}}}.  What additional changes will be needed to make the
 instructions work if it's a .so?  Various *nixes have different variables
 for shared library search IIRC.

-- 
Ticket URL: <http://svn.boost.org/trac/boost/ticket/1744#comment:26>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.