Mail Archives: djgpp/1999/06/15/04:10:28
On Tue, 15 Jun 1999, Johan Venter wrote:
> Have you seen the code to gccw32?
No.
> It just adds the environment variables, and spawn()'s a copy of gcc.
> The djggp.env parser then sees that the variables have already been
> defined in the environment, and appends the added directories in the
> djgpp.env file to the currently defined variables.
> My critisim is that this requires that the djgpp.env variables all
> begin like this:
>
> C_INCLUDE_PATH=%/>;C_INCLUDE_PATH%
Most (if not all) of them do, precisely for this reason.
> This may not be the case on some users computers, for example I know
> some people that DELETED that part of the variable because they
> didn't think they needed it because they don't define those
> variables manually.
We have a long history of telling users not to edit their DJGPP.ENV
files. If they have to do it because something in DJGPP.ENV is wrong,
then I think we should find a way to correct DJGPP.ENV. But if they
edit the environment file simply because they think this will solve
their problems, even though the instructions tell them not to edit the
file, then caveat the user.
> All I wanted to do was think of a better way to add these variables,
> and I think I've found one.
In my experience, whatever clever way you can come up with, there will
be some user that will break it because they think they know better.
I still think that if there's a way to add something to DJGPP.ENV to
make life easier for RSXNT users, it is best to do so than to invent
some new file or a new program.
- Raw text -