Boost logo

Boost :

Subject: Re: [boost] [RangeEx] Range & RangeEx
From: Neil Groves (neil_at_[hidden])
Date: 2008-09-12 08:52:30

On Fri, Sep 12, 2008 at 1:41 PM, Robert Jones <robertgbjones_at_[hidden]>wrote:

> On Fri, Sep 12, 2008 at 1:28 PM, Neil Groves <neil_at_[hidden]>
> wrote:
> >
> > This sort of thing should work, but of course it's missing closing
> > parenthesis as posted.
> >
> So it is - no worries, that wasn't real code, just text in an email.
> My ignorance is a little more basic I'm afraid, more to do with the
> mechanics of 'installing' range_ex.

I am not aware of an official procedure for installing libraries from the
Vault. So I just made up my own for Boost.RangeEx. What I do is:

1. rename the boost/range folder to boost/_range.
2. copy the range_ex code into the boost folder so it becomes the
boost/range library that is found when building.

It isn't possible to have both versions in the same application since this
would violate the One Definition Rule.

Once you have done this you should not need to set any additional compile
switches or adjust anything else in your build.

Of course, once the Boost.RangeEx has been reviewed and hopefully accepted
it'll become part of Boost.

This works for me with g++ 4.4 and MSVC 8 and 9

> If I take the zip from the vault and unzip in the same directory as my
> client code I end up with Range_Ex directory, and the path to range.hpp
> is
> Range_Ex/boost/range/range.hpp
> whereas my client code has an include directive of
> #include "boost/range.hpp"
> so using a command line of
> g++ -IRange_Ex mycode.cpp
> doesn't find the range_ex range.hpp header.
> Is this how I'm supposed to be doing it?
> Thanks, Rob.
> --
> ACCU - Professionalism in programming -
> _______________________________________________
> Unsubscribe & other changes:

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