Mail Archives: djgpp/2013/12/21/09:15:18
On 21.12.2013 12:07, Juan Manuel Guerrero wrote:
> These are:
> /dev/env/DJDIR/net/watt/inc for headers.
> /dev/env/DJDIR/net/watt/lib for libraries.
Not really. They're actually something like
d:\somewhere\djgpp\net\watt\inc
d:\somewhere\djgpp\net\watt\lib
> set C_INCLUDE_PATH=/dev/env/DJDIR/net/watt/inc
> set LIBRARY_PATH=/dev/env/DJDIR/net/watt/lib
It's been an astonishingly long time since I thought about this, but I
I'm not convinced you're supposed to put /dev/env/DJDIR type paths into
the external configuration, i.e. into host system environment variables.
Note how none of the other directories in the gcc -print-search-dirs
output is using /dev/env/DJDIR paths, but rather absolute paths with
driver letters.
If memory serves, back in the day I used to put such not-quite-standard
include and library paths into djgpp.env. As an additional benefit,
that avoids burdening the environment variable space.
> I have read the gcc info doc and it tells that LIBRARY_PATH is a
> colon separated list of directories to search for linker files if
> they cannot be found using GCC_EXEC_PREFIX.
Well, for DJGPP you better make that a semicolon-separated list of
absolute paths.
> I have assumed that these directories are absolute paths and not
> relative paths to the current partition or am I missing something?
The gcc info doc doesn't know about DOS. On Unix, which is what it does
know about, there's only one directory tree, and thus all paths are
either absolute (if they start with a /), or relative to the current
working directory (if they don't).
On Microsoft platforms these look like "d:\dir" and "dir", respectively.
But "thanks" to drive letters, these platforms have a two more types
of path specifications: paths relative to the current working drive, but
otherwise absolute ("\dir"), and paths relative to _another_ drive's
current working directory ("d:dir"). Those have their uses, too, but
hardly for use in static configuration like environment variables.
- Raw text -