Mail Archives: djgpp/1998/09/27/18:45:41
In article <Pine DOT SUN DOT 3 DOT 91 DOT 980927130444 DOT 25393N-100000 AT is>, Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> writes:
>On Fri, 25 Sep 1998, bowman wrote:
>
>> One thing I did get
>> burned on: I believe it is 'autoconf' that goes looking for a shell in
>> /bin. The Cygwin bash didn't seem to want to play well with the djgpp
>> 'sed', IIRC.
>
>The Cygnus ports don't do anything to make the life of a Windows
>programmer easier wrt the Unix-style paths. The installation
>instructions explicitly tell to make sure /bin and /tmp exist on every
>drive on your system (it remains unclear how would you pull such
>tricks on networked drives ;-), and that sh.exe is copied to every
>such /bin directory.
I tend to agree with Eli Z. here. Further, I haven't found the UNIX-emulation
stuff to be very helpful...in fact, it is downright buggy and un-helpful.
There are others who have noticed the problem, and there is something called
MINGWIN that addresses it (more below.)
Regarding having Cygwin and djgpp on one computer, that is entirely possible
given a good understanding of how the DOS environment interacts with each
platform.
An optimal solution for Windows programming with free software seems to be
this:
the MINGWIN version of the Cygwin programming platform with the egcs compiler
at the core. Here are some URLs:
Cygwin:
www.cygnus.com/
MINGWIN:
http://www.fu.is.saga-u.ac.jp/~colin/gcc.html
egcs:
http://www.xraylith.wisc.edu/~khan/software/gnu-win32/egcs.html
wxWindows:
http://web.ukonline.co.uk/julian.smart/wxwin/
People have even compiled the free C++ cross-platform library, wxWindows using
this setup. All of these tools are developing rapidly, but they have only
gotten to the point of being usable in conjunction very recently.
--Ed (Myknees)
- Raw text -