GCC For Windows NT?
mr.potatohead asks: "I had been using cygwin to compile some UNIX programs (gd, for example) to be used in an NT environment. We all know Red Hat has bought Cygnus. RH is now charging for this once free product. So what's a geek stuck working for the man to do? Is there a good gcc option for those of us wasting away on NT?"
From the website,
Haven't gotten around to using it yet, but for people who have a hard time replicating the Unixish environment that the Cygwin compiler wants, it might be good.
"For I am a Bear of Very Little Brain, and Long Words Bother Me"
As far as I know, Cygnus is still free, and you can access the original web pages, and cvs trees as normal at the old homepage of http://sourceware.cygnus.com.
:-). We don't want you to have to switch over twice.
Cygnus used to charge previously for the product as well; if you want nice manuals and stuff then you pay, which makes perfect sense.
To quote directly from the Cygnus webpage itself:
How does Red Hat's acquisition of Cygnus affect this site?
For now, very little. We thought about "conducting a process of re-engineering and re-branding with the aim of integrating our free software community outreach programs into our corporate objectives". But then we said "naah, let's just continue to have a great site to develop free software and work on making it even better".
In particular, we plan to be careful about changing the host name sourceware.cygnus.com or anything else which may require you to update your habits, CVS/Root files, etc. The name will have to change but before we go changing things around we'd kind of like to at least have a plausible guess about what we are going to change them to
Incidentally, you may also want to check out AT&T's UWIN, at http://www.research.att.com/sw/tools/uwi n/ as well; very cool, does much the same thing.
HTH.
Anil
You could try Mingw32 - a port of GCC which uses MSVCRT.dll or MSCRT.dll runtime libraries instead of CYGWIN.dll and thereby avoids any licensing issues which you might run into by having to distribute CYGWIN with all your binaries. I've used it successfully for porting some of my own code without any real problems (just hiccups caused by using function names which are already used by MS libraries but not by Linux ones, or by defines which are already set up on Windows such as NOERROR or NO_ERROR).
Cheers,
Toby Haynes
Anything I post is strictly my own thoughts and doesn't necessarily have anything to do with the opinions of IBM.