Date: Wed, 8 Jul 1998 11:54:43 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Martin Str|mberg <ams AT ludd DOT luth DOT se>
cc: djgpp-workers AT delorie DOT com
Subject: Re: compiling syslinux-1.40
In-Reply-To: <6nu17i$kqc$1@news.luth.se>
Message-ID: <Pine.SUN.3.91.980708115412.5286R-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On 7 Jul 1998, Martin Str|mberg wrote:

> :       #define _PATH_DEFPATH   "c:/djgpp/bin;c:/dos;c:/windows;/usr/bin;/bin"
> :       #define _PATH_CONSOLE   "/dev/tty"
> :       #define _PATH_DEVDB     "c:/djgpp/var/run/dev.db"
> :       #define _PATH_LOCALE    "c:/djgpp/share/locale"
> 
> Well I disagree; there's no standard DJGPP directory, hardcoding them
> to c:/djgpp is BAD.

There's no other way to do it, given that DOS/Windows lack
standardized directory trees.  Almost all DJGPP port of GNU packages
have been doing this for years, albeit without paths.h: they all have
some path like c:/djgpp/something hard-wired into them, and then rely
on environment variables set from DJGPP.ENV to take care of the actual
place where to look for files.

> Consider that when there are there people will use
> them and then when this program is moved to another machine, it wont
> work because the path which is compiled into the program doesn't
> exist!

We do it already, as I said above.

And if a program is compiled on Linux, then moved to another Linux
machine, it runs the risk of not working as well.

> But perhaps DJGPP compiled program handles this correctly
> automatically?

Automation is only possible if you make thos path names relative to
%DJDIR% and expand %DJDIR% at run time.  This usually means changing
the original code of an application.  Some DJGPP ports do that
already, but most don't.

Please keep in mind that paths.h is a last fallback in case no
environment variable overrides it.

> Perhaps this thread should move to DJGPP-WORKERS?

Done.