Mail Archives: djgpp/1997/11/25/07:43:44
From: | Christopher Croughton <crough45 AT amc DOT de>
|
Message-Id: | <97Nov25.134342gmt+0100.17029@internet01.amc.de>
|
Subject: | Re: Substituting \ for / in make
|
To: | eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
|
Date: | Tue, 25 Nov 1997 13:41:46 +0100
|
Cc: | djgpp AT delorie DOT com
|
In-Reply-To: | <Pine.SUN.3.91.971124171158.25038B-100000@is> from "Eli Zaretskii" at Nov 24, 97 04:20:33 pm
|
Mime-Version: | 1.0
|
Eli Zaretskii wrote:
>
> The variable itself should probably be mentioned, yes. I'm just not sure
> where: originally, it was designed as an internal hook. Its only use is
> to set up ported or portable programs. Since we don't have any docs
> which explains how to port, I don't know where it should be mentioned.
Hmm, perhaps in a document explaining how to port? <g> Seriously, a document
like that (probably as part of the DJGPP User Guide thingy) would be a
Good Thing(tm).
> The FAQ is not a good place, since almost nobody asks about DJDIR.
The answer to that is simple - I'll ask about it every week and then it
will become a Frequently Asked Question <g>.
> README.1ST is inappropriate IMHO, since it should be kept simple enough
> to get newbies off the ground.
Right, true.
> It seems that a section in kb.inf, under "Hidden Features", is one place
> that's appropriate. Now, if I only had additional 24 hours every day...
Why be so conservative? Ask for at least 48 <g>...
(From the time you seem to spend answering questions here, I'm surprised
you get anything else done anyway...)
> As for the fact that DJDIR converted to forward slashes, I'm not sure it
> needs to be documented at all. After all, if you understand the syntax of
> DJGPP.ENV (described in kb.inf) and look inside it, you should see it
> immediately ;-).
Does someone actually understand that syntax? I thought it "jest growed"
<g>...
Thanks, anyway...
Chris C
- Raw text -