Re: Non-portable paths in bbv1

From: David Abrahams (dave_at_[hidden])
Date: 2004-08-27 07:42:34

"Johan Nilsson" <johan.nilsson_at_[hidden]> writes:

> I figured I'd just repeat part of my previous posting, which might be of
> more general interest.
>
> The path specification in boost-build.jam is defined using slashes, causing
> problems (at least) under VMS, see result of invocation:
> ------------------
> $ mcr [.bin_vms]bjam.exe -n
> Unable to load Boost.Build: could not find build system.
> ---------------------------------------------------------
> DISK$USER1:[JNI.POSNET.DEPS.BOOST]boost-build.jam attempted to load the
> build system by invoking
>
> 'boost-build tools/build/v1 ;'
>
> but we were unable to find "bootstrap.jam" in the specified directory
> or in BOOST_BUILD_PATH (searching
> DISK$USER1:[JNI.POSNET.DEPS.BOOST]tools/build/v1).
>
> Please consult the documentation at 'http://www.boost.org'.
> ------------------
>
> Apart from this; are there more known places where paths are specified using
> "/" directly (foreseeing further problems)? I'm using bbv1 from the 1.31
> release.

The design intention was that forward slashes should always work
portably in Jamfiles, and that if-and-when someone started trying to
build Boost on VMS, we would build the neccessary path translation
code into the build system. So, the solution is to hack the contents
of tools/build/v1/*.jam, not individual Jamfiles.

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com