VC ++ generates release

 

Build-batch build-select the corresponding release version, and click all reconstruction on the right to generate the release version.

 

Q: Why is the following error in the release version correct during batch creation?

-------------------- Configuration: musicfan-Win32 release --------------------
Linking...
Musicfandlg. OBJ: Error lnk2001: unresolved external symbol _ mciwndcreatea
Release/musicfan.exe: Fatal error lnk1120: 1 unresolved externals
Error executing link.exe.
Musicfan.exe-2 error (s), 0 warning (s)
A: I have encountered a similar problem. When I compile the link to generate the release file, the above error occurs, but it can be passed in debug,
Find the library where debug is needed through the Internet, and use the release library because I
A vfw32.lib library file is linked in the project, but this file is not linked in the release, causing an error.
The solution is to select the settings for drop-down box option under project/settings.
Win32 release, select the link item on the right, and then add the library file to be linked
The box under object/library modules.

No wonder ~~ The libraries called by debug and releas are different ~.

OK!

 

 

 

Generally, the software developed under VC is not enough to have only one EXE file. It usually requires other resources, which are usually stored in the dynamic link library (. DLL), you need to install them on the target machine before running, and some components need to be registered before they can be used. The installer (such as Install Shield) does this. Simple installation program production software some development tools (such as VB, Vc, etc.) are carried, complex installation programs need some professional installation and production software to make, you can first try to use the former.

Source: http://www.programbbs.com/bbs/view20-21484-1.htm