Boost logo

Boost :

From: David Abrahams (dave_at_[hidden])
Date: 2007-05-16 13:10:36

on Tue May 15 2007, Douglas Gregor <> wrote:

> Users of Boost.Build are isolated from this change are isolated from
> the effects of this change due to usage-requirements. usage-
> requirements are very cool, but they hide the fact that this change
> causes real trouble for people not using Boost.Build. The very simple
> line
> g++ mytest.cpp -I $BOOST_HDRDIR -L $BOOST_ROOT/lib -
> lboost_unit_test_framework-gcc33-mt-d
> fails to link. That's bad for at least two reasons: (1) it's the
> first line that someone is likely to write when trying out the unit
> test framework, and it's not going to work; (2) it's the line that
> most non-BBv2 build systems would produce, because using -L and -l
> are the common ways to link against a static library in the Unix
> world. Not the *only* way, but the common way. There also doesn't
> seem to be any documentation that tells users that this change was
> made, or how to link to the Boost unit test framework on a *nix system.

(3) It's what the getting started guide tells users to do.

Dave Abrahams
Boost Consulting
Don't Miss BoostCon 2007! ==>

Boost list run by bdawes at, gregod at, cpdaniel at, john at