Date: Wed, 5 Nov 1997 12:18:27 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Nate Eldredge <eldredge AT ap DOT net>
cc: Mirek Prywata <mpry AT fuw DOT edu DOT pl>, djgpp AT delorie DOT com
Subject: Re: DJGPP +Novell:can I do anything more?
In-Reply-To: <199711050218.SAA14986@adit.ap.net>
Message-ID: <Pine.SUN.3.91.971105121804.460Q-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On Tue, 4 Nov 1997, Nate Eldredge wrote:

> First, try installing a disk cache so that the entire executable might not
> have to be loaded over the network each time.

This won't work: networked drives are NOT cached by disk caches (at
least not by SmartDrv and several others that I know of).  Disk caches
work either on the BIOS level (cache sectors) or on block device
driver level (IOCTL functions, Int 21h/AH=44h), and both of these are
unavailable with networked drives.

> Then edit the
> DJGPP.ENV to make anything that's located elsewhere be pointed to. Eg, if
> the include files live on the network drive, perhaps create an environment
> variable called MORE_DJGPP, point it at g:\djgpp, and set up DJGPP.ENV so
> that INCLUDE_PATH includes it.

A DJGPP installation which spans multiple directory trees is a
non-trivial setup.  However, at least in this case, there's no need to
edit DJGPP.ENV.  All of the environment variables pertinent to
compilation of C/C++ programs are set up in the *stock* version of
DJGPP.ENV in a way that makes addition of directories very easy: just
define an environment variable that names the additional directories
from the DOS prompt (or in AUTOEXEC.BAT).  DJGPP.ENV *appends* its
default values to the values that exist in the environment.  For
example, here's the line that defines C_INCLUDE_PATH on DJGPP.ENV from
djdev201.zip (that's where the C header are searched):

C_INCLUDE_PATH=%/>;C_INCLUDE_PATH%%DJDIR%/include;%DJDIR%/contrib/grx20/include

As you see, if C_INCLUDE_PATH is defined, it will be *prepended*
before the default.

As a general rule, I'd advise NOT to edit DJGPP.ENV unless there's
*absolutely* no other solution, even if you are advanced DJGPP user
and generally know what you are doing.  I can tell trench stories from
here to eternity, including from my own bitter experience, about
people who got badly burnt by this.  Instead of editing it, look at
its contents, try to see how can you change things without editing it,
read the docs of the program in point (maybe it allows additional
variables not set by DJGPP.ENV), ask here, and only then edit if no
other solution exists.