Boost :

From: David Abrahams (david.abrahams_at_[hidden])
Date: 2001-10-04 11:17:23

----- Original Message -----
From: <williamkempf_at_[hidden]>

> There are very few projects currently using the Boost.Build system,
> so AFAIK the only one that failed to compile for you was
> Boost.Threads. This was a minor oversite during the process of
> moving Boost.Threads onto the trunk and I'll correct this in the CVS
> repository ASAP. In the mean time there are two ways to build
> Boost.Threads available to you. Modify \$(BOOST_ROOT)/Jamfile to
> include the following at the end:
>

I don't think that will work until I update the Build System. Making this
work (if you use <include>\$(BOOST_ROOT) in your subproject) depends on
fixing the "relative include" problem we've been discussing. Aww, heck, it's
been lingering so long and it's an easy hack; I'll try to fix that this
afternoon.

Note that this technique doesn't affect anything unless you're trying to
build from the top level.

> Or, run Jam directly in the \$(BOOST_ROOT)/libs/thread/build directory
>
> > Do you use SGI iostreams provided by STLPort or native iostreams?
> >
> > > I was particularly interested in using the new
> > > Boost.Threads. However, when I tried to manually subinclude
> > > libs/thread/build in \$(BOOST_ROOT)/Jamfile, I get many
> compilation
> > > errors because \$(BOOST_ROOT)/boost/thread is not in my Include
> > path..
> > >
> >
> > Try modifying the jam file. After replacing \$(BOOST_ROOT)
> > with ../../.. the includes paths were set up ok.

That's what I'd expect, under the current situation.

> This shouldn't be happening (and doesn't for me). Be sure to run Jam
> with -f??\boost\tools\build\allyourbase.jam.

I'm really surprised to hear that. You can invoke a build from the top level
(\$(BOOST_ROOT)) and it works??

-Dave