Mail Archives: djgpp/2000/06/22/07:30:50
On Wed, 21 Jun 2000 16:38:28 +1000, Leon AT caresystems DOT com DOT au wrote:
>> I was just wondering what is better: Djgpp or
>> Cygwin. I planning to do C programming in dos.
>
>for dos - djgpp
>for windows - mingw32
>for xplatform (ie unix compatibility issues) -
>cygwin
>
>i use mingw32 - but since djgpp and mingw32
>both ports of gcc stuff - find useful to be on both
>groups.
I use Mingw (the current name for mingw32) binaries
under Win9x/NT/2k, so my DJGPP2-target compiler is
Mingw-hosted. Mixing DJGPP2 and Mingw executables can
simply cause there a big mess... When binutils, make,
gcc, gdb, unix-utilities etc. all are Win32-hosted,
there aren't problems (unless one doesn't take the
currently impossible Mingw-to-DJGPP2 degugger as a
problem...)
I use DJGPP2 binaries under DOS/Win3.1x/Win32s as the
'console apps' and 'Mingw32s' binaries as the 'GUI apps'.
So my Mingw-targeted GCC is DJGPP2-hosted and my GDBs
with a GUI are Mingw-hosted. Mixing DJGPP2 and 'Mingw32s'
binaries there seem to work ok, so using e.g. the
shareware WinEdit96 as the IDE/editor for a toolkit
and compiling, running the program and starting
Insight under WinEdit96 (giving the debuggee name to
it) is possible. Again, getting a Mingw-to-DJGPP2
debugger is a problem --- debugging DJGPP2 programs
under Insight-GUI would be nicer than using the text-
based interface...
I don't like Cygwin at all... If one needs a Unix,
Linux is just much better than NT+Cygwin. It is aimed
to those "puppets controlled by the MS threads", ie.
doing just what MS orders (and MS currently says that
any support for DOS, Win3.1x and Win32s is very, very
bad...). Mingw hasn't these restrictions, although
its maintainers might also try to claim otherwise...
Perhaps they just don't like to add Win32s to their
supported-list... After all, when I can drive with a
10 years old car, why running a 5 years old computer
would be such a sin, as MS and the computer sellers
claim...
Cheers, Kai
- Raw text -