From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-09-14 09:11:13
Toon Knapen wrote:
> >>IIUC a toolset is a set of tools and settings(options) for those tools
> >>such that these tools can be used to transform sources into executables.
> > No, not exactly. Toolset is a file in v2/tools ;-) It can define
> > generators (=tools), but it can also define targets, like stlport.jam
> > does.
> But I have many external dependencies like blas. Should I make a
> <dependency-name>.jam for each of them.
If some of them can contain only a single library, you can declare them in
If many of them are multu-library, then creaing 10 .jam files may be
inconvenient. In that case you can create some rule which will implement
either of two approaches I've outlined in the last email. Users will be able
to call that rule from user-config.jam, for example:
use-prebuilt-lib-set ublas : a b c d e ;
The implementation of 'use-prebuilt-lib-set' can be placed in a module which
will be loaded in user-config.jam with "import".
> And do they have to be placed in
> the boost/tools/build/v2/tools/ or can they live also elsewhere ?
You can add any directory to BOOST_BUILD_PATH (either in environment or in
boost-build.jam) and place your extensions there.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk