Re: Re: Non-portable paths in bbv1

From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-08-30 05:41:09

Johan Nilsson wrote:

>> > I already got bootstrapping to work (if you're talking about building
>> > jam0.exe + jam -fbuild.jam) with some minor modifications to sources,
>> > build_vms.com and build.jam.
>>
>> Great. Do you have the build system files loaded when you put VMS path in
>> boost-build.jam?
> 
> ??

I mean, when you invoke bjam, it looks for boost-build.jam and tries to load
the build system from the path found there. Does this part work?

> 
>> That, and some code in v2/kernel/modules.jam is the only
>> code which does not use path abstraction and which needs to be tweaked.
> 
> Oh, you mean I must use a native VMS path inside boost-build.jam, or?

Yes, I think that boost-build.jam might very well use platform-specific
syntax. If the path specified there is absolute, then it definitely should
use VMS syntax. For relative path slash separated syntax can be made to
work, but I'm not sure if that's the most important thing. You can just
hardcode absolute VMS paths in all boost-build.jam files and make
everything else work. 

>> Of course, whether to work with V1 or V2 is up to you.
> 
> Depends on which version requires the least amount of work to get going
> :-)

In that case, I think V2 looks more reasonable. You would need to

1. Put a VMS path to tools/build/v2/kernel in some boost-build.jam (for
example, tools/build/v2/boost-build.jam) and make sure the build system is
loaded. For V2, it means that tools/build/v2/kernel/bootstrap.jam is loaded
(you can add 

ECHO "LOADED" ;

to it)

2. Then kernel/bootstrap.jam and kernel/modules.jam might need to be fixed
where they use hardcoded slashes. E.g.

BOOST_BUILD_PATH += $(whereami:D)/$(subdirs) ;

would become

BOOST_BUILD_PATH += $(subdirs:R=$(whereami:D)) ;

3. Then, add VMS support to utils/path.jam. Hopefully, this will be enough.

- Volodya