Sorry, first part of the post is a rant... Details at the bottom. Skip to QUESTION if you don't want to read my rant. I'm a team member of several open source projects which originally where linux only. "Porting" them to other unix-list operating system was pretty easy. Now the win32 people are coming on board and there is much angst between 'nix developers and the win32 developers. 1 project, the code base forked. Poor suckers like me, are left integrating win32 features/bug fixes/etc back into the 'nix code. Which is not perfect solution but works. Another project foked as well, but no attempt has been made to merge feaures/fixes/etc back into each tree. So, there is major duplication of effort on both code bases. This sucks, imho. The salvo of insults goes. Fire: We are linux developers, why would we develop for Win32 platform? Return fire: Win32 controls 98%(?) of desktop. Want users, need Win32 port. Talking to the more rational developers (in both camps). It really boils down to editors(!!!). Ok, development environment. Linux people can't stand MS/GUI/IDE stuff and the Win32 guys can't stand vim/emacs/make/CLI stuff. To solve the Win32 problem, I have these developers install cygwin and all it's tools. Not perfect, but it "enforces" coding that makes porting back to Linux easier. Plus the Win32 guys get to keep their devel environment. QUESTION Is there a way to go the other way? Can I generate Win32 (cygwin) executables under on my linux box in my linux development environment? I looked at gcc cross-compiling, but couldn't figure out how to generate Win32 bins. I've done this for i386->Sparc, but the same technique doesn't work for Win32. Any ideas? -- Bob Tanner <tanner at real-time.com> | Phone : (952)943-8700 http://www.mn-linux.org, Minnesota, Linux | Fax : (952)943-8500 http://www.linuxjustworks.com | Linux Just Works! Key fingerprint = AB15 0BDF BCDE 4369 5B42 1973 7CF1 A709 2CC1 B288