Mail Archives: djgpp/1998/03/10/02:19:21
On Sun, 8 Mar 1998, Eli Zaretskii wrote:
> On 6 Mar 1998, Esa A E Peuha wrote:
> Some packages ported to DJGPP include instructions to edit DJGPP.ENV,
> and Groff and TeX are among them. In these cases, you indeed should
> edit the environment file as instructed.
> > Maybe the "standard" version of DJGPP.ENV should be updated more often than
> > the whole DJGPP distribution. Actually I could make it available on my web
> > site, if that's a good idea.
> I'm not sure. People who change their DJGPP.ENV frequently usually
> know what they are doing. And those who don't might get confused by
> what they find on your site. But it might be worth a try.
It's at
http://www.helsinki.fi/~peuha/english/djgpp/
and there's also a modified info/dir file. Any comments are welcome.
> > Could these programs use DJDIR to compute the default paths instead
> > of using hard-coded "c:/djgpp/..."?
> This would require a change to the way these packages handle the
> default pathnames. Most of the packages put the default pathnames
> into header files as fixed strings. There is no easy way to change
> this into something that will expand relative to %DJDIR% at run time,
> without extensive changes to the configuration process. Where such
> changes are relatively easy (e.g., in Make and Id-utils), they are
> done.
Do you mean header files generated by the configuration process? But even
then I don't really see the problem. A piece of djgpp-specific code can
get the value of DJDIR at startup (and use "c:/djgpp" if DJDIR is not
set), and then concatenate it with relative paths into global arrays which
can then be used like the header-defined fixed strings. Am I missing
something here?
Esa Peuha
student of mathematics at the University of Helsinki
http://www.helsinki.fi/~peuha/
- Raw text -