From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-05-08 07:23:55
Peter Steiner wrote:
> On Wed, 8 May 2002 12:48:43 +0400, Vladimir Prus wrote:
> > Can you explain what are trying to achive? Do you want to specify
> > location of build system? Or to run jam on arbitrary file?
> I have a complex project (only C source code, no C++) that needs to be
> compiled with different compilers (MSVC and some cross compilers for
> embedded systems). For now I'm using dmake with tons of included
> makefiles, which is too complicated and error prone.
> The reason for different compilers is the comfort of debugging on the
> PC. Some selfcontained modules can be tested on the PC before
> integrating them with the cross compiler to the embedded system.
> I like the boost approach with toolset jamfiles for specifying the
> compiler independently of the project itself. Usually I would like to
> have a default toolset for most of the targets (I'm not sure about an
> overall default), so that I can just type "jam target" in the directory
> of a subproject without the need for setting up different environments
> for each subprojet
So, you want to be able to specify default toolset for building some targets?
Unfortunately, at this stage you cannot specify default toolset for a target.
On the other hand, you can specify it for a project. In Jamrules you can write
TOOLS ?= borland ;
I'm not sure that it will be enough for you, though -- do you need to be able
to link together targets with different default toolsets?
> It would be fine to have a global location of the build system, but that
> should not be tied to BOOST_ROOT, because there are other C++ projects
> using boost.
In fact, BOOST_ROOT is going to disappear. User is now able to specify the
location of build system by either
- creating at project root a file called "boost-build.jam" with the content
boost-build <path_to_build_system> ;
- or setting BOOST_BUILD_PATH
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