Qt is very nice but I don't want to compile on MinGW and I'm too much of a nigger to get a Qt license. wxWidgets isn't bad either but since I have the full-blown VS2008pro with a valid license, might as well use MFC, it has a better IDE and it's more common (read maintainable).
>>17
My problem is that I already have a VS project and I don't want to code raw cxx files, because then I lose the MFC wizards and I have to add message maps by hand. Also resource editor, etc.
Your protip gave me an idea though... I'll build the VS project as usual, then I'll write a script to copy only the cpp files into another directory (as cxx files or whatever cmake wants) and call cmake followed by nmake. That should let me have an automated build and still keep my project and its MFC shit. Thanks.
I think though that if you're making an MFC example, you should make people build it with VS directly, because it makes no sense to build a project with VS, code, destroy the project, rebuild it with cmake, and finally compile the new project cmake made to get a binary. That's a waste of time, you don't need to support other build platforms since MFC apps will obviously be built on VS 6.0+.
Nobody in their right mind would frost an MFC with their Leenux.