Dev-Cpp 4.9.9.2 - VS4.2/MFC - stdafx.h

[urbansound]

Hi,

I looked over the FAQ's and searched the forums as well as some Google searches on this.

I'm finding conflicting comments as to whether or not current Rev levels 4.9.nn of Dev-Cpp with integrated Mingw should or should not handle compiling pre-.NET versions of VS 4-6 codes.

I have had great success on some smaller DLL packages, but as I progress toward more complete program and/or GUI apps, it's heading up-hill.

For one, I am not a C++ programmer, so I'm a little out of the water to begin with, but here's what's happening...

I have a standard VS C++ version at 4.42 library level, with MFC, running on XP Home. (I tried 2005 Express .Net conversion for these and it does not do MFC conversions at all)

The programs I'm testing on were developed in VS C++ 6.n.

My hopes were to use the MingW integrated Dev-CPP to overcome differences, if the Dev-Cpp/MingW handles these code and compilation levels.

First, I don't know if I should have Dev-Cpp reference the MSMFC includes/libs etc, or does the minimalistic Mingw support for MFC level compilations itself or indirectly at all?

The struggling compilations seem to be finding, (among other things), that a first header is setting up StdAfx.h, (mixed case), versus other calls beyond it using strictly lower case references, (stdafx.h).

So, I'm unclear if I'm simply hoping to do something that is virtually a lost cause, or if I just need to focus on learning how to properly integrate the mix on these with the IDE and compiler?

Some example output is below and thank you for any advise, good or bad. ;-)

Mike

Compiler: Default compiler
Building Makefile: "C:\Dev-Cpp\Projects\MxmanangerAPI\ManagerAPISample\Makefile.win"
Executing make clean

rm -f dialogs/MailSendDlg.o ManagerAPISample.o ManagerSheet.o dialogs/newssenddlg.o PageDaily.o PageDealer.o PageExposure.o PageJournal.o PageLogs.o PageMailbox.o PageMain.o PageMargin.o PageMW.o PageNews.o PageOnline.o PageOrders.o PagePlugins.o PageReports.o PageRequests.o pagesummary.o PageSymbols.o PageUsers.o dialogs/requestdlg.o StdAfx.o dialogs/symbolchangedlg.o dialogs/userbalancedlg.o dialogs/usergroupdlg.o dialogs/userhistorydlg.o dialogs/usernewdlg.o dialogs/userupdatedlg.o

ManagerAPISample_private.res ManagerAPISample.exe g++.exe -c dialogs/MailSendDlg.cpp -o dialogs/MailSendDlg.o -I

"C:/Dev-Cpp/lib/gcc/mingw32/3.4.2/include" -I"C:/Dev-Cpp/include/c++/3.4.2/backward" -I"C:/Dev-Cpp/include/c++/3.4.2/mingw32" -I"C:/Dev-Cpp/include/c++/3.4.2" -I"C:/Dev-Cpp/include" -I"C:/Devel_all/MSDEV/include" -D__GNUWIN32__ -W -DWIN32 -DNDEBUG -D_WINDOWS -D_AFXDLL

In file included from dialogs/MailSendDlg.cpp:6:
dialogs/..\stdafx.h:10:64: afxwin.h: No such file or directory
dialogs/..\stdafx.h:11:46: afxext.h: No such file or directory
dialogs/..\stdafx.h:12:82: afxdtctl.h: No such file or directory
dialogs/..\stdafx.h:14:71: afxcmn.h: No such file or directory
dialogs/..\stdafx.h:16:51: afxsock.h: No such file or directory

In file included from dialogs/MailSendDlg.cpp:7:
dialogs/..\ManagerAPISample.h:8:5: #error include 'stdafx.h' before including this file for PCH

[Wayne Keen]

"First, I don't know if I should have Dev-Cpp reference the MSMFC includes/libs etc, or does the minimalistic Mingw support for MFC level compilations itself or indirectly at all?"

No, you should not be trying to use MFC with MinGW.

Wayne

[urbansound]

Thanks Wayne,

"No, you should not be trying to use MFC with MinGW.

Wayne "

Well, after some fumbling around and verifying the MingW win32 package integrity, it made no sense to me that these shouldn't be able to function together. That doesn't mean that there won't be some bumping around along the way to make things work, but I've now been successful in converting VC++ MFC 6.0 DLL's, Consoles and GUI projects at this point, to boot that I only have 4.2 rev level MFC libs. 8-O Mind you they're fairly small apps.

Clearly that doesn't represent that it's an intended clean solution but MingW's minimalistic doesn't disallow it any more than they don't post that it's feasible to consider, so out of shear ignorance, I've found it works, likely only due to the MingW's win32 compliance levels achieved.

That doesn't say anything about licensing or redistribution of course, but that I did have fair success to this point in making it happen.

Thankfully, this is was a rare occasion of need. ;-)

Mike

[Wayne Keen]

"That doesn't say anything about licensing or redistribution of course"

Therein lies the major rub. MFC is Microsoft proprietary.

Wayne

[urbansound]

I guess what surprises me is the extent of effort MingW group went through to develop the minimalistic, as big a task as that must have been, but then didn't reproduce an equivalent to reproduce MFC, which by comparison seems much smaller of a task.

Anyhow, for the small effort I needed to accomplish for my own needs, the process worked out well and learning to use Dev-C++ to help, was a real joy. The IDE identified the projects for import, converted them nicely and with the extent of integrity Dev-C++ reads back GCC results, made the task for a newbie, a fun challenge.

Thank you for your remarks.

Mike