From: fist1000 AT aol DOT com (Fist1000)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: why won't my .exe program run properly until I set env var?
Date: 29 Jan 1998 09:57:06 GMT
Lines: 27
Message-ID: <19980129095701.EAA26346@ladder02.news.aol.com>
NNTP-Posting-Host: ladder02.news.aol.com
Organization: AOL http://www.aol.com
References: <slrn6d0feb DOT lt6 DOT davep AT hagbard DOT demon DOT co DOT uk>
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

>> > 1. Start up a DOS window from windows95
>> > 2. Run the batch file (which has
>> > set djgpp=c:\djgpp\djgpp.env
>> > set path=c:\djgpp\bin;%path%)
>> > 3. Start programming
>> 
>> This is silly.  If you plan to do a lot of programming in DJGPP, you
>> should set the environment variables in your autoexec.bat so they always
>> exist.  I can't think of any possible reason why this wouldn't work
>> better.
>
>While, on the whole, I'd agree with you (DJGPP is my DOS C compiler of
>choice) there are times when you don't want to do it. For example, if you
>have more than one GNU development environment (DJGPP, GCC-Win32,
>GCC-Win32-prc, ...).
>
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.

- Aegis (fist1000 AT aol DOT com)