Re: Non-portable paths in bbv1

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-08-30 02:43:11

Hi Johan,

>>
>> 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.
> 
> Thanks, now working myself through allyourbase/boost-base.jam.
> 
> // Johan

Maybe, it would make sense to go right to V2. It has an abstraction for
paths (in tools/build/v2/util/path.jam) which is used everywhere and might
make the task of VMS support simpler. You'd only need to add routines to
path.jam that handle conversion from VMS syntax to portable syntax and back
(in addition to making bootstrap works).

- Volodya