OpenEuphoria

I just giftwrapped EC.EXE and threw it out the window.

• Posted by Mike The Spike <mtsreborn at yahoo.com> Feb 05, 2001
• 480 views

EC.EXE, and ECW.EXE for that matter, piss me off
bigtime.
For the moment, they work perfectly for me on the
following platforms;
EC.EXE - DJGPP
ECW.EXE - LCCWin

But I just installed Borland, and re-installed my
cracked Watcom version, and guess what?
ECW.EXE for Watcom outputs an emake.bat for LCC.
That's weird, SINCE I DON'T HAVE PATH=D:\lcc\ in my
autoexec.bat.

Even if I pass 'ecw.exe -wat myprog.exw', the
emake.bat file produced is for LCC, not Watcom.
Even 'ecw.exe -bor myprog.exw' causes an emake.bat for
LCC to be spawned.

This is annoying, since I have to compile by hand now.
Why is this, since I don't have LCC in my autoexec.bat
file.

ECW.EXE for Borland does the same!

The old Translator versions didn't do this.

Anyone else had this problem?


Mike The Spike