Boost logo

Boost :

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-07-18 15:19:57

----- Original Message -----
From: "Douglas Gregor" <gregod_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Thursday, July 18, 2002 1:26 PM
Subject: Re: [boost] Formal Review: Template Metaprogramming Library (MPL)

> On Thursday 18 July 2002 01:02 pm, Victor A. Wagner, Jr. wrote:
> > I guess I typed too soon (I should have read to the bottom of the
> > However doing
> > cvs update -rmpl_v2
> > essentially got rid of my entire boost installation...fortunately -A
> > appears to have gotten it back.
> >
> > What is the suggested method of keeping a single boost "tree" and
> > proposed libraries??
> It's not exactly easy to keep a single tree along with testing proposed
> libraries. I tend to keep a full checkout of Boost CVS and put proposed
> libraries into separate directories. When testing the proposed libraries,
> make sure to #include from the proposed library's path _before_ the main
> Boost CVS checkout.
> I have no idea how this would interact with the build system, but I'm
sure it
> isn't pretty :)


Of course it's trivial:

    mytest : foo.cpp bar.cpp
        : <sysinclude>$(BOOST_OVERRIDES) <sysinclude>$(BOOST_ROOT)


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