From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Using $(HOME) in makefile
Date:	5 Jul 2000 18:02:54 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	19
Message-ID:	<8jvt8e$7n5$1@nets3.rz.RWTH-Aachen.DE>
References:	<200007051631 DOT LAA03097 AT darwin DOT sfbr DOT org>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 962820174 7909 137.226.32.75 (5 Jul 2000 18:02:54 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	5 Jul 2000 18:02:54 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Jeff Williams <jeffw AT darwin DOT sfbr DOT org> wrote:

> But I neglected to say that whatever value HOME has for `make',
> it should (ideally) be understood by any program that uses HOME to
> find its startup files (e.g., gnuplot, vim, elvis).  These do not
> understand `/dev/c'; `c:' is usually understood as a relative path;
> and `c:/' will choke any program expecting DOS-style backslashes.

There's always still the choice to set up HOME as an environment
variable with backslashes, and reverse the slashes for all or
particular DJGPP-compiled ones in djgpp.env, just like it's done with
%DJGPP% or %DJDIR%, too.

OTOH, I'd expect most programs using $HOME at all to be able to cope
with Unix-style slashes, too --- it's a Unix-style environment
variable, after all.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -