Date: Thu, 22 Apr 1999 11:23:58 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: DJ Delorie <dj AT delorie DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: [binkley AT sst DOT ncsl DOT nist DOT gov: djgpp and ld]
In-Reply-To: <199904201441.KAA10263@envy.delorie.com>
Message-ID: <Pine.SUN.3.91.990422112332.15748E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 20 Apr 1999, DJ Delorie wrote:

> > Because ${DJDIR} works even for those who do NOT install it in /djgpp
> > (like myself ;-).
> 
> For packages that can dymanically find where djgpp is installed,
> great.  We're all set.  For the rest, which hard-code a static path, I
> suggest we hard-code /djgpp instead of /usr/local or whatnot.

In my experience, the absolute majority of GNU packages only use
--prefix to put it and its derivatives into Makefile's, and only in
conjunction with "make install" or in creating absolute path names of
programs used by the Makefile.  For these, ${DJDIR} is The Right
Thing (tm), since it *is* dynamically resolved when the package is
rebuilt.

For the small number of packages I saw that use --prefix to hard-code
path names into the binaries, I also make a point to use
--prefix=c:/djgpp, or change the program to resolve ${DJDIR} at run
time.