- Forum
- Windows Programming
- What's the difference between the 'Use o
What's the difference between the 'Use of MFC'?
When I deal with Win32 project on VC2008, there are three options for "Use of MFC":
1st, Use Standard Windows Libraries
2nd, Use MFC in a Static Library
3rd, Use MFC in a Shared DLL
What should I notice when one of them is selected?
1st, Use Standard Windows Libraries
2nd, Use MFC in a Static Library
3rd, Use MFC in a Shared DLL
What should I notice when one of them is selected?
Some time ago I read somewhere that MFC was only shared DLL. I guess that changed? Or maybe I was just plain wrong.
Anyway:
The first option means that you won't be using MFC.
The second option means that you wnat to use MFC but you want the MFC code to be included in the resulting executable. This allows your EXE freedom because it won't depend on DLL's in the system. This option will make your EXE bigger in size.
The third option means that you want to use MFC and that you will be dynamically linking to the MFC dll's (or dll, singular, not sure). This makes your EXE smaller in size, but you then depend on the MFC runtime files (the mentioned dll's) to be in the target PC. This is not as troublesome as you might think, though.
Experiment with both. Each has its own application.
Anyway:
The first option means that you won't be using MFC.
The second option means that you wnat to use MFC but you want the MFC code to be included in the resulting executable. This allows your EXE freedom because it won't depend on DLL's in the system. This option will make your EXE bigger in size.
The third option means that you want to use MFC and that you will be dynamically linking to the MFC dll's (or dll, singular, not sure). This makes your EXE smaller in size, but you then depend on the MFC runtime files (the mentioned dll's) to be in the target PC. This is not as troublesome as you might think, though.
Experiment with both. Each has its own application.
Topic archived. No new replies allowed.