Re: Re: Problems bootstrapping/building bjam under OpenVMS

From: Johan Nilsson (johan.nilsson_at_[hidden])
Date: 2004-08-12 01:37:08

"Rene Rivera" <grafik.list_at_[hidden]> wrote in message
news:411B0096.9030306_at_redshift-software.com...
> Michael Stevens wrote:
>
> > Hello Johan,
> >
> >>Hmmm .. talking to myself. Rene - I could try go generate some kind of
> >>diffs against 1.31.0 for the affected files, if that would help.
> >
> > I is probably worth noting that there has been a fair bit of development
on
> > bjam since 1.31.0 Most of this is new buitin's but it would probably be
> > better to create a diff against the current CVS.
>
> I concur. A patch against the current CVS makes it much easier to apply.
>

I fully understand that. Unfortunately I don't have internet access on the
VMS machines and going through some extra steps to get the source available
there, that's why I'm a bit reluctant to do that. When I get the time I'll
post patches either against the 1.32.0 release or current CVS. It probably
won't happen the next couple of weeks.

I'd still like some kind of opinion on how to resolve the '#include
"../native.h"' problem for the stuff in [.modules]. I see a few options:

1. Use '#if defined (VMS)' in the modules (worst option, IMHO):

#if defined(VMS)
# include "[.-]native.h"
#else
# include "../native.h"
#endif

2. Use include paths for the compiler + no path in module sources; e.g. "cxx
/include=([])" + #include "native.h"

3. Move the modules to the same directory as the other jam sources and
rename them; e.g. mod<whatever>.h

// Johan