Mail Archives: djgpp-workers/1998/07/08/04:54:52
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.
- Raw text -