Re: Re: Re: Problem building bjam using build.jam (VMS)

From: Johan Nilsson (gclbb-jamboost_at_[hidden])
Date: 2003-09-17 08:52:59

"Vladimir Prus" <ghost_at_[hidden]> wrote in message
news:200309171545.27874.ghost_at_cs.msu.su...
> Johan Nilsson wrote:
>
> > > Could you please try applying the attached patch?
> >
> > You did read the part about "voodoo logic", "black magic" and "woe be to
> > people who mess with this code" in pathvms.c, right? :-)
>
> Yep. That comment is applicable to the entire jam, to a certain extent.
But,
> of course, it easy for me to say ;-)
>
> > Anyway, the patch worked insofar as to producing the desired result,
e.g.
> > $("[.binvms]":P) == ""). However the semantics doesn't seem to be
identical
> > under windows where $("./binvms":P) => ".". Haven't tried under unix.
Would
> > [.binvms] => [] => "" be a better choice?
>
> I think you are right -- seems this way on unix too.

Ok.

>
> > Maybe consulting the perforce
> > jamming list would be a good idea?
>
> I almost given up with the idea to get any feedback on jamming list,
> unfortunately. Maintainers usually keep silence.

Too bad, I think some of the people lurking there have a better
understanding of VMS than myself.

>
> > It was also possible to run 'jam -fbuild.jam", but the next problem was
> > that the ".rm" action isn't defined for VMS (which is straightforward to
> > fix).
>
> Strange, I see
>
> if $(VMS) { actions piecemeal together existing .rm. {
> DELETE $(>[--2]:J=";*, ") $(>[-1]);*
> } }
>
> in build.jam. Do you have an older copy?
>

The one I've got is from the 1.30.2 zip file from sourceforge.

> > When I started looking through the build.jam file, however it looks
> > like it isn't terribly platform independent (only Windows and unices
> > supported?). Did any Mac users try "jam -fbuild.jam"?

[snip]

> >
> > Is the above also the case when running Boost.Build (I hope not, but I
> > haven't come that far yet).
>
> I think that the problem is that Boost.Build does not support DEC C/C++ at
the
> moment. However, when/if that support is implemented (which should not be
> very hard), it easy to create syntax that compiler wants.
>

In build.jam you don't use the 'real' bjam toolsets - only the minimum stuff
defined inside the jamfile itself, right?

What I call DEC C++ is actually supported, but only under unix - i.e.
tru64cxx(65)-tools.jam. Most of the settings there should be available under
the VMS version, just using a different command-line syntax. I guess porting
those toolsets shouldn't too much of a hassle.

// Johan