From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-05-08 06:46:00
From: "Peter Steiner" <peter.steiner_at_[hidden]>
> On Wed, 8 May 2002 12:03:00 +0400, Vladimir Prus wrote:
> > Peter Steiner wrote:
> >> Then I tried the following settings:
> >> /1/ set BOOST_ROOT=c:\l\jam
> >> /2/ set BOOST_BUILD_PATH=c:\l\jam\tools\build
> >> /3/ set BOOST_BUILD_PATH=c:\l\jam\tools\build\new
> >> /4/ set JAMBASE=c:\l\jam\tools\build\new\build-system.jam
> >> /5/ set JAMBASE=c:\l\jam\tools\build\build-base.jam
> >> /6/ set JAMBASE=c:\l\jam\tools\build (with build-base.jam copied to
> >> jambase.jam)
> > I believe that /2/ an /3/ should work if you invoke bjam.exe, not
> > is not documented in build_system.htm but "jam.exe" just implements
> > behaviour (this is recent change).
> Yes, /2/ and /3/ work with bjam
> > I don't remember that 4-6 ever worked.
> That's a pity. What would then be the best approach to get something
> I'd like to have as few environment variables as possible and be able to
> each of them from the command line.
^---------------- ?? I think there's a verb missing right here.
We are deemphasizing the use of command-line variables for boost.build v2.
If you're trying to set the JAMBASE programmatically from an environment
variable I might suggest a forwarding script, jjam.bat:
jam -f%JAMBASE% %*
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