Re: [Dev-C++] Fw: Dev-C++ looking for MSVCRT.DLL
Open Source C & C++ IDE for Windows
Brought to you by:
claplace
|
From: afpTeam <af...@sb...> - 2007-01-31 21:37:17
|
----- Original Message ----- From: "Daniel D." <dan...@gm...> To: "afpTeam" <af...@sb...>; <dev...@li...> Sent: Wednesday, January 31, 2007 4:13 PM Subject: Re: [Dev-C++] Fw: Dev-C++ looking for MSVCRT.DLL > Some points : > > 1. being a MS technology, MFC will scarcely help beyond Windows and VS. I keep finding mixed opinions as to whether or not calling into MFC from MingW should or shouldn't work. The MingW project shows msvcrt capability to exist which I thought would spoof or at least borrow on the MFC libs themselves, but then it seems to choke when running into MFC, so I can tell if the support is or isn't functional. I adopted a little project that was written in VS C++ 06 and I have only 04 rev. libs on board for one thing. I was hoping to keep the original project in it's basic native form and write "around" the differences, if practical. So far I have 14 errors and many are dependency issues, as stupid as glorified printf's, but in this case it looks to be coming down to socket threading issues which are not necessarily trivial to just "write around". > 2. you may probably have to rewrite the project, so that to make no use of > the MFC :( Yeah. It looks like hacking it up may be more trouble than it's worth, where if I could have created a maintainable crossover, the project would make sense to take on, where a re-write would be a little too much for the value of the effort. > 3. just wonder why would you use a different IDE anyway, as long as your > system remains Windows I would prefer to move away from M$ dependency and continue to look for cross platform ways of dealing with Windows applications. I really don't want to pay to upgrade old MFC libs for one little project, nor do I want to stay in VS C++. Express 2005 conversion to C++ would have been nice but of course Bill broke that off in our tailpipes by excluding MFC and other critical support unless you purchase the 2005 pro version of C++. I don't mind writing in C# 05 Express from scratch, when someone needs it but otherwise I continue to work toward MingW and keep most of my efforts closer to Linux based life, onboard the Win box as most of what I produce for my own purposes will be .Net Mono/standard M$. I'm having pretty good luck maintaining cross portability with some fairly substantial apps this way. Thanks for your words. Mike > > DD > /***************************************** > these are just my personal opinions and thoughts > *****************************************/ > ----- Original Message ----- > From: "afpTeam" <af...@sb...> > To: <dev...@li...> > Sent: Wednesday, January 31, 2007 7:31 PM > Subject: [Dev-C++] Fw: Dev-C++ looking for MSVCRT.DLL > > >> Hi list, >> >> I'm trying to build a pre-existing VS C++ 6.0 project in the current >> 4.9.9.2 >> MingW Dev-C++ IDE and sadly for starters, I only have 4.nn MFC libs on >> board my XP system. >> >> Dev-C++ imported the solution/project. >> I pointed the project includes directory at the MFC includes directory. >> >> The IDE identified the following macros for the project: >> >> Compiler: >> -D__GNUWIN32__ -W -DWIN32 -DNDEBUG -D_WINDOWS -D_AFXDLL >> >> C++ compiler: >> -D__GNUWIN32__ -W -DWIN32 -DNDEBUG -D_WINDOWS -D_AFXDLL >> >> Linker: (is empty) >> >> When I run compile, I get the following errors: >> >> ////////////////////// >> In file included from C:/Devel_all/MSDEV/mfc/include/afx.h:27, >> from C:/Devel_all/MSDEV/mfc/include/afxwin.h:19, >> from dialogs/..\stdafx.h:10, >> from dialogs/MailSendDlg.cpp:7: >> C:/Devel_all/MSDEV/mfc/include/afxver_.h:128:3: #error Please use the >> /MD switch for _AFXDLL builds >> C:/Devel_all/MSDEV/mfc/include/afxver_.h:133:3: #error Please use the >> /MD switch (multithreaded DLL C-runtime) >> ////////////////////// >> >> When I follow them out I get... >> >> MailSendDlg.cpp says: #include "..\stdafx.h" >> stdafx.h:10 says #include <afxwin.h> (MFC core) >> afxwin.h:19 says #include <afx.h> >> >> afxver_.h 128 says >> #if defined(_AFXDLL) && !defined(_DLL) >> #error Please use the /MD switch for _AFXDLL builds >> #endif >> >> afxver_.h 128 says >> #ifndef _MAC >> #if defined(_AFXDLL) && !defined(_MT) >> #error Please use the /MD switch (multithreaded DLL C-runtime) >> #endif >> #endif >> >> It seems a little odd that the compiler is sending back a response >> related >> to "ifndef _MAC" so perhaps I have to find a way to tell the compiler to >> ignore this one? >> >> Apparently then I need to tell gcc to compile and link in MSVCRT.DLL to >> support threading, either static or at runtime? >> >> Admittedly this is a lack of familiarity on my part in how to tell >> Dev-C++ >> and GCC to make this inclusion. >> >> So what is the best way to have Dev-C++ tell the comipler to manage this? >> >> Thanks, >> >> Mike >> --- avast! Antivirus: Outbound message clean. Virus Database (VPS): 000709-1, 01/31/2007 Tested on: 1/31/2007 4:37:03 PM avast! - copyright (c) 1988-2007 ALWIL Software. http://www.avast.com |