serialization library as dependency

David Abrahams wrote:
> "Reece Dunn" <msclrhdhotmail.com> writes:
> > David Abrahams wrote:
> >> 
> >> Isn't "$(BOOST_ROOT)" just
supposed to be "boost"?  Or am I missing
> >> something?
> >
> > (2) You import the $(BOOST_ROOT) library names in
a parent Jamfile
> > of the one you are referencing the boost//library
in. I can't recall
> > exactly how to do this, but I think it is
something like:
> >
> >    using-project boost : $(BOOST_ROOT) ;
> 
> It's 
> 
>      use-project boost : /path/to/boost/root ;

Thanks.

> > You could have:
> >
> >    alias boost : $(BOOST_ROOT) ;
> >
> > and
> >
> >    exe test : [ glob *.cpp ] boost//thread ;
> >
> > I believe that would work. Either way, I think you
need
> > $(BOOST_ROOT) somewhere when you are not in a
child of
> > $(BOOST_ROOT).
> 
> I guess my point is that you don't really need
$(BOOST_ROOT)
> anywhere.  That variable was a requirement for BBv1 in
some cases, but
> now it's obsolete... and yet, people cling to it.

I wasn't aware that $(BOOST_ROOT) was a V1 thing and that
it is
obsolete.

One advantage to using BOOST_ROOT is that if you have a
project
that is dependant on Boost checked into CVS, Perforce or
some other
source control system in such a way that the project and
Boost could
be anywhere on the system, if you want that project to use
Boost,
BOOST_ROOT is the easiest way to avoid issues. If you check
in to
the SCM:

   use-project boost : c:/boost ;

then this prevents the developer(s) working on that project
from
having Boost somewhere else (and prevents Unix/Mac
development!)

I would say having:

   use-project boost : $(BOOST_ROOT) ;

at the root of your project (or some other environment
variable)
is the best you can do in this situation. I like being able
to say:

   /boost//thread

etc. in BBv2.

- Reece
____________________________________________________________
_____
Try Live.com - your fast, personalized homepage with all the
things you care about in one place.
http://www.live.com/ge
tstarted
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Reece Dunn wrote:
> I would say having:
> 
>    use-project boost : $(BOOST_ROOT) ;

+1

I'm doing this for Windows, Linux and SGI... and several
boost 
versions, withour changing the code in Subversion/CVS

Kevin

-- 
| Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this
     |
| Senior Technology                     | My employer for
certain |
| And Network Systems Architect         | Not even myself   
     |

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Reece Dunn wrote:
> I would say having:
> 
>    use-project boost : $(BOOST_ROOT) ;

+1

I'm doing this for Windows, Linux and SGI... and several
boost 
versions, withour changing the code in Subversion/CVS

Kevin

-- 
| Kevin Wheatley, Cinesite (Europe) Ltd | Nobody thinks this
     |
| Senior Technology                     | My employer for
certain |
| And Network Systems Architect         | Not even myself   
     |
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On Tuesday 27 June 2006 01:23, Kevin Wheatley wrote:
> Reece Dunn wrote:
> > I would say having:
> >
> >    use-project boost : $(BOOST_ROOT) ;
>
> +1
>
> I'm doing this for Windows, Linux and SGI... and
several boost
> versions, withour changing the code in Subversion/CVS

Another solution is to put:

  use-project boost : /system/specific/path ;

in user-config.jam (which can contain everything ordinary
Jamfiles can).

Whether this is more or less convenient that using
environment variable is a 
matter of personal preferencee.

- Volodya

-- 
Vladimir Prus
http://vladimir_pru
s.blogspot.com
Boost.Build V2: http://boost.org/boost-
build2
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build