What are the differences between use MFC in a static library and use MFC in a shared DLL?

 

If you select use MFC in a shared DLL,Your compiledProgramDoes not contain the MFC library, so the file will be relatively small, but if your program is directly moved to a machine without MFC installed, it may lead to the failure to find the mfc dll.

If you select use MFC in a static library,Then, the compiled program directly contains the library that calls the MFC. The file may be larger, but it can be directly moved to other machines for running.

The former is a dynamic connection,Release the DLL file with MFC.

The latter is a static link,Release DLL files without MFC.

If there is only one executable file, use the former, and the execution speed is high, but the file size is relatively large.
If there are multiple executable files, use the latter,Because DLL files are shared, the total volume of files is reduced.
A single file is also small. Load execution blocks, but the running speed is slightly slower than the former.

Used in a static Library:
Use the Lib file. Lib is a compiled binary file that can be statically linked with your project to become an EXE.
Used in a shared dll:
Using the DLL file, the function is hidden inside the DLL file. After your project is compiled into an EXE file, the DLL is called during running.