Mail Archives: djgpp/1995/06/18/04:11:55
> Currently the include search path includes several nonexistent directories
> (such as /usr/include) that must be holdovers from a unix copy.
This is normal and shouldn't give you any trouble.
> Second, I
> want to put include files I make myself in a separate directory, such as
> /djgpp/pgd/include, and add it to the path. I also want it to search for
> libraries in /djgpp/lib rather than having to specify the full pathnames
> on the command line.
You should have a file named DJGPP.ENV in your /djgpp directory. This file
names the environment variables and their values which go32 puts into the
environment before running your program. The format and syntax of this file
is documented in the README.DOC or README.DJ file in the djgpp directory,
under the chapter named ``About the environment''. Whatever you need to
change, change there, as the variables there might in certain cases override
the values set from AUTOEXEC.BAT (it depends on the definition of the variable
in DJGPP.ENV and is explained in README.DOC). In your AUTOEXEC.BAT you should
have only a single line:
set DJGPP=c:/djgpp/djgpp.env
> There are several environment variables such as COMPILER_PATH but setting
> these in autoexec.bat seems to have no effect, for whatever odd reason
> (and yes, I rebooted to make them take effect!)
This might be because the variables from DJGPP.ENV take precedence, or you've
used an incorrect variable. E.g., COMPILER_PATH is only to tell gcc where
should it look for the executables of the compiler passes (cpp, cc1, as and
ld). If you cannot fix these problems through DJGPP.ENV as suggested above,
post a more detailed list of the variables you need but cannot change.
> Coming on top of the missing archives (txi and gpp) this is annoying.
I would suggest to yell at the company which sold you that CD-ROM. Selling
a package without a means to read the docs is a misservice, especially when
those tools are free.
- Raw text -