Mail Archives: djgpp/2001/07/25/09:29:55
On Wed, 25 Jul 2001, ANW wrote:
> > Do you have any reason to believe that this particular program is
> > compatible with DJGPP? It seems to me it isn't, in which case you will
> > need to modify the sources slightly to get it to compile.
>
> No, I have no reason to believe that the Linux program would be
> compatible with DJGPP. But as I mentioned in my earlier reply to Martin
> Strlmberg, those two "missing" files are actually residing in a few of
> my folders!?
As I wrote in another message, those headers are not what this program
expects. That is certainly true for sys/io.h, but might also be so for
getopt.h.
> > > PATH=G:\AMZI4\BIN;F:\EIFFEL45\BENCH\SPEC\WINDOWS\LIB\MSC;F:\BP\BIN;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\DOS;C:\PROGRA~1\OUTLOOK\OFFICE;E:\EMACS20.3.1\BIN;I:\JDK1.3\BIN;
> > > H:\ELJ-WIN32\SMALLEIFFEL\BIN;H:\ELJ-WIN32\LCC\BIN;G:\DJGPP\BIN
> >
> > This is slightly sub-optimal: the DJGPP bin subdirectory should ideally
> > be much closer to the beginning of PATH, to avoid problems with picking
> > wrong versions of the preprocessor, Make, and other utilities. Other
> > than that, your installation is correct.
>
> Agreed. But wouldn't the same logic apply to one of my other compilers
> as well? May be using "batch" files to set the path and invoke the
> compiler instead of "setting the path in AUTOEXEC.BAT" would be better?
Yes, if you have more than one compiler installed, it is indeed advisable
to use batch files to switch from one development environment to another.
Alternatively, you could define several desktop shortcuts, one each for
every compiler you use, which open a DOS box, and make each shortcut run
a different batch file when you click on that shortcut.
- Raw text -