lnk4098 and msvcr71.dll and msvcr71d.dll in release build

[jigi]

My release dll build has both these versions.. release build to QA, it looks like its failing out on both those dll's[viewed thru depends.exe]. what do i do.Am using vC++ .net

Settings:
code generator -> Multi-threaded DLL (/MD)
additional dependency ->user32.lib
gdi32.lib
winspool.lib
comdlg32.lib
advapi32.lib
shell32.lib
ole32.lib
oleaut32.lib
uuid.lib
odbc32.lib
odbccp32.lib

ignore specific library -> libcmtd.lib
delay load dlls ->opengl32.dll
comdlg32.dll
oleaut32.dll
winmm.dll
wsock32.dll
winspool.dll

verbose
/OUT:"Release\\FujifilmUploadClient1.dll" /NOLOGO /LIBPATH:"C:\Qt\3.3.4\lib" /LIBPATH:"../../../Libraries3rdParty\tiffio\qTiffio\Debug" /LIBPATH:"..\..\..\Libraries3rdParty\Tiffio\qTiffio\Release" /DLL /NODEFAULTLIB:"libcmtd.lib" /DEF:"C:\Qt\3.3.4\extensions\activeqt\control\qaxserver.def" /DELAYLOAD:"opengl32.dll" /DELAYLOAD:"comdlg32.dll" /DELAYLOAD:"oleaut32.dll" /DELAYLOAD:"winmm.dll" /DELAYLOAD:"wsock32.dll" /DELAYLOAD:"winspool.dll" /SUBSYSTEM:WINDOWS /BASE:"0x39D00000" qt-mt.lib qaxserver.lib opengl32.lib glu32.lib kernel32.lib user32.lib gdi32.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib imm32.lib winmm.lib wsock32.lib winspool.lib delayimp.lib ..\..\..\Libraries\WebServiceAPIClientPlain\Build\WebServiceAPIClientPlain.lib ..\..\..\Libraries3rdParty\curl-7.13.0\lib\Release\libcurl.lib QTTiff.lib kernel32.lib user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib "\Qt\3.3.4\lib\qt-mt.lib" "\Native\Main\Libraries3rdParty\curl-7.13.0\lib\release\libcurl.lib" DelayImp.lib

[jonnin]

the dll versions with a d on the end are debug enabled dll versions. You do not need them for your release version unless you tampered with the wrong settings in release (if you did, put it back to default and do not turn any debugging on!).

I am unclear on what you did to create this output? If your Q/A team does not have the compiler installed, and you provide the exe, then you need to also provide the dlls. If ANY of the dlls has a d as the last letter in the name for example named.dll then your release is using debug dll's. Fix that, and then provide the Q/A with a version that uses release dll's and provide the dll's (you can either try to unravel it or stick it on a cleanly installed windows machine and let it complain -- add each dll as it asks -- then if it does not run properly you will have to unravel it from there). You cannot test on a machine that has the compiler installed or it will find all the dll's and you will not know what the end user will need.