From: Vladimir Prus (ghost_at_[hidden])
Date: 2003-08-28 04:46:05
> > > 1) --version ALL by itself should return the version NO MATTER WHAT!!
> > > don't give me this junk about "wrong directory"
> >It's simply not possible. "--version" means "give me version of build
> > system used". It can only work if bjam can find the build system and it
> > does supports --version. V1 does not. It can be changes, but in general,
> > running
> > bjam --version
> >from arbitrary place of filesystem cannot work.
> ok, where's the option that says "give me the version of bjam"?
> > > C:\Projects\boost>bjam --v2 --version
> > > C:\Projects\boost\tools\build\kernel\modules.jam:203: in
> > > normalize-raw-paths rule NORMALIZE_PATH unknown in module modules.
> > > C:\Projects\boost\tools\build\kernel\modules.jam:252: in import
> > > C:\Projects\boost\tools\build\kernel\bootstrap.jam:50: in boost-build
> > > C:\Projects\boost\boost-build.jam:12: in module scope
> > >
> > > 3)
> > > C:\Projects\boost\tools\build\examples-v2>bjam --v2 --version
> > > C:\Projects\boost\tools\build\examples-v2\..\kernel\modules.jam:203: in
> > > normalize-raw-paths
> > > rule NORMALIZE_PATH unknown in module modules.
> > > C:\Projects\boost\tools\build\examples-v2\..\kernel\modules.jam:252: in
> > > import
> > > C:\Projects\boost\tools\build\examples-v2\..\kernel\bootstrap.jam:50:
> > > in boost-build
> > > C:\Projects\boost\tools\build\examples-v2\boost-build.jam:2: in module
> > > scope
> > >
> > > Happy??
> >No, not really. I believe your bjam version is out of date. As I've said
> > in
> >previous email:
> > >Victor, if that's the case, you should rebuild jam from CVS. Both
> > Boost.Build
> > >and Boost.Jam must be from the same time to work reliably. Either from
> > > some release of from the same CVS state.
> twice daily most days, at least once per day, I do:
> echo off
> date /T >> update.log
> time /t >> update.log
> cvs -z5 update -A -P -d >> update.log
> if errorlevel 1 goto OOPS
> bjam "-sTOOLS=vc7.1" >bjam.log
> on a Windows XP system.
> and then compile several of our current projects against the new results.
> if this does NOT build a new Boost.Build and Boost.Jam then maybe we should
> rethink (or at least restate) what "building boost" means.
The above is fine for Boost, but CVS HEAD of Boost.Build V2 requires CVS HEAD
of Boost.Jam. So, you should run boost_root/tools/build/jam_src/build.bat and
use the binary that is created.
> Do I need special things to build build and jam? why?? if they're part of
> boost, the "build all" should do it, right?
Well, http://www.boost.org/tools/build/index.html mentiones that you have to
install Boost.Jam before building boost. For building boost, prebuilt
packages exists. For testing V2, one has to compile Boost.Jam from sources.
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