Message-Id: <199904280446.EAA96618@out5.ibm.net>
From: "Mark E." <snowball3 AT bigfoot DOT com>
To: djgpp-workers AT delorie DOT com
Date: Wed, 28 Apr 1999 00:47:00 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: v2.03: wrapping up
X-mailer: Pegasus Mail for Win32 (v3.01d)
Reply-To: djgpp-workers AT delorie DOT com

> I think using "-imacros" to include
> sys/version.h will solve this cleanly and reliably.
> 
> The problem is that there seems to be no way of having specs expand
> environment variables (last time I looked),

> Could someone please look at the latest GCC/EGCS sources and 
see if
> there is some way of including a header whose name is relative to 
the
> include directory?

It's still true in the latest sources. One solution that looks promising is 
to define a custom spec. Cygwin has a custom spec in their 
configuration to hold the mingw32 include path. I see no reason why 
we couldn't apply the same method to create a custom DJGPP spec to 
hold the value of $DJDIR or whatever value is preferred. The problem 
is the cut off date of feature submissions for egcs 1.2 was a few days 
ago. Of course there's no reason we couldn't add it in for our 1.2 and 
submit it so it gets in to 1.3. 

A special filename that evaluated to $DJDIR would also work (e.g. 
/dev/djgpp like Andris suggested a few days ago) or if there were 
someway of evaluating a env. variable in a filename (e.g. 
/dev/env/djdir/). Problem is such a feature, if added, would have to wait 
for 2.04. But egcs 1.2 is scheduled to come out in July, and I can't 
imagine that 2.04 would be out by then.

--- 
Mark Elbrecht, snowball3 AT bigfoot DOT com
http://snowball.frogspace.net/