On Sun, Nov 26, 2006 at 01:54:19PM -0500, Greg Folkert wrote: > > Joe, for that reason I have always suggested and done Cygwin > installations. It allows for the *nix commands. Does present much of the > ability. There are many other things that can be installed on a Windows > machine that allows for many things that are missing on them... as a > "Stock" Windows machine. > When I had to use windows regularly myself, I used Cygwin. Where I work now I am required to use windows occasionally, but thankfully all the windows machines have Exceed and I can bring up an xterm on a Unix or Linux server to get my real work done. Anyhow, my biggest beef with Cygwin was the limitations. Several years ago, when I was working on my undergraduate thesis, I was writing a small simulation. It had to run on Windows and Linux (I am a Linux guy and my advisor was a Windows guy). Enter Cygwin and wxWindows. I installed Cygwin on my laptop and then downloaded wxWindows. I needed a static build and a shared build, so I open up two xterms, unpack wxWindows and start the two builds. After a few hours, both failed with an error like "Ran out of environment space." Now, I don't know if that speaks to a limitation in Cygwin or in Windows, but it is annoying. I ended up restart the builds and doing them serially. Regards, -Roberto -- Roberto C. Sanchez http://people.connexer.com/~roberto http://www.connexer.com
Attachment:
signature.asc
Description: Digital signature