Linux.com: From MFC to GTK: A Developer's JourneySep 26, 2000, 07:36 (2 Talkback[s])
(Other stories by Ryan Gordon)
"The Microsoft Foundation Classes are going to be 90% of your porting headache. Games generally don't use the MFC, so usually most the bulk of that porting work is focused on generating Linux-based graphics and sound drivers to integrate into the codebase. This is why the editors take longer: you have to deal with an almost-certain code rewrite when you encounter MFC code."
"You might be able to eliminate this headache almost completely with the aid of support libraries such as Twine or MainWin, but then you get new headaches to replace the old one. MFC 4.2, an ancient version, is the last code revision Microsoft legally permits you to compile for non-Windows platforms. The source to newer revisions of MFC comes with the Visual Studio product from Microsoft. Your conscience and your lawyers can decide if you should try your luck with these."
"Legality aside, don't forget your end users; not only are win32 wrappers considered to be "cheating" by the Linux community, no one wants to run a native Linux application that looks like a native Windows application. After all, if we wanted to use Windows programs, we'd just run Windows in the first place and save all this hassle. Your users demand more from you. Do not cheat them out of it."