Boost logo

Boost-Build :

From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-09-28 02:01:12

On Tuesday 27 September 2005 18:20, Kevin Wheatley wrote:
> Kevin Wheatley wrote:
> > Now all I have to do is implements my own Jam file for the boost
> > installed tree and it might not take a minute or two to start building
> > ... :-)
> So as a result of my posting that link a few days ago, I've been
> experimenting with a toy project of mine and getting it to build under
> Windows (VC 7.1) using BBv2. It links in a couple of the Boost
> libraries that are built using the normal install (filesystem, thread,
> test, etc).
> Whan I use-project and point it to the extracted BOOST_ROOT, i.e. the
> full source, bjam takes well over 1 minute to sit there and decide
> that nothing needs to be done. If instead I make my own Jamroot file
> and add some prebuild libs corresponding to something similar to what
> Jason Stewart mailed a few days ago, the time taken to bjam falls by
> over 60s to something on the order of 15-20s. Clearly this is an
> interesting point for future improvement as has already been
> suggested.

Please go to Boost's top Jamfile.v2 find the "install" or "install-headers"
target (depends on Boost version), locate the

[ glob $(dirs)/$(patterns) ]

in the target definition and remove that text. Then try again and report the

> Related to this, is there a way to make a use'd project auto-magically
> add say an <include> to my project requirements, in particular if I am
> not using any targets from the other project directly. this would be
> the case with a header only Boost library for instance where I would
> want the boost project file to be referenced...
> exe mytool : foo.cpp : <include>/boost ;
> basically I want useage-requirements when I reference the project or
> something similar.


exe mytoo : foo.cpp : <use>/boost//headers ;

> in a similar manner is it possible to use the project id as a base
> point to start looking for directories...
> lib mylib : [glob *.cpp ] :
> <include>/myproject/subproject//directory/to/include ;
> That way I get the rename-ability of using project ids and relative
> paths...

No, it's not possible I'm afraid.

Vladimir Prus
Boost.Build V2:

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at