From:	Charles Terry <cterry AT plinetl DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: why won't my .exe program run properly until I set env var?
Date:	Sun, 01 Feb 1998 20:24:01 -0800
Organization:	All USENET -- http://www.Supernews.com
Lines:	43
Message-ID:	<34D54A60.1061@plinetl.com>
References:	<slrn6d0feb DOT lt6 DOT davep AT hagbard DOT demon DOT co DOT uk> <19980129095701 DOT EAA26346 AT ladder02 DOT news DOT aol DOT com> <34D151D6 DOT 789D AT cs DOT com>
Reply-To:	cterry AT plinet DOT com
NNTP-Posting-Host:	17887 AT 206 DOT 168 DOT 149 DOT 183
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

John M. Aldrich wrote:
> 
> Fist1000 wrote:
> >
> > I definitely agree. I have Turbo C++ 3.0, Watcom C/C++ 10.6, TASM5, and DJGPP
> > V2 all installed and I have several different batch files to setup the
> > environment to work under each, for example: set_dj2.bat, set_tc3.bat,
> > set_wat.bat, and set_t5.bat.
> >
> > Whenever I want to develop under a specific compiler, I just run the necessary
> > batch file.
> 
> I think this could be defined as a pathological case, since a "normal"
> user will usually only have one or at most two compilers on a single
> machine.  In any case, the setting for the DJGPP variable, which is the
> most important one, shouldn't affect other compilers in any way.  The
> only setting that could affect them is the PATH, causing the wrong
> programs to be run for a command line compiler, and in this case a batch
> file to change the PATH is probably a good idea.
> 
> I haven't seen this personally, but I understand that some IDE-based DOS
> compilers that have a separate command-line functionality require that
> the INCLUDE_PATH, LIBRARY_PATH, and similar variables be set in the
> system environment, instead of reading them from a file like DJGPP apps
> do.  Aside from leading me to question whether these compilers are
> really "easier to use" than DJGPP, this sort of situation would probably
> also require some sort of batch file to set or unset the variables.
> More to the point, this finagling would have to happen anyway regardless
> of whether DJGPP is one of your compilers.
> 
> I seem to have proven your point.  :-)  But I would be interested to
> find out how many people who read this list use more than two compilers
> on the same computer on a frequent basis.
> 
That looked like a poll- so Turbo C++(though less all the time),
Masm611, and gcc.
Masm is the only one that uses the env variables so no problem for me.
As to the path issue I use Borlands grep with all my work so I need that
path,
but I also use (DJ)cpp which both djgpp and turbo have. Just set the DJ
path before the
TC path 
Charles Terry

- Raw text -