Has anyone come across this issue?
There seems to be a behavioral difference (and possible bug) in visual
strudio 2003 when building a vc.net solution through IDE and building the
same solution through command line using "devenv". The linker seems to be
failing when build is invoked through command line.
Here are the differences: (There are additional references to .lib files in
cmdline invoked version which are not there in IDE invoked version; even the
path to the last 2 .libs is not correct). As a result the build of the
solution fails with error:
Linking...
LINK : fatal error LNK1181: cannot open input file
'\Build\build\bin\Release\ErrorStr.lib'
Here are the response files that are generated by devenv:
linker response file when solution build is invoked from command-line:
[
/OUT:"..\..\..\..\bin\Release/BlueMinder.dll" /INCREMENTAL:NO /NOLOGO
/LIBPATH:"D:\Build\Work_Streams\Utility\Lib" /DLL /DEBUG
/PDB:"..\..\..\..\bin\Release/BlueMinder.pdb" /FIXED:No kernel32.lib
user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib
ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib
"\Build\bin\Release\ErrorStr.lib" "\Build\bin\Release\EventStr.lib"
".\Release\BlueMinder.obj"
]
linker response file when solution build is invoked from IDE:
[
/OUT:"..\..\..\..\bin\Release/BlueMinder.dll" /INCREMENTAL:NO /NOLOGO
/LIBPATH:"D:\Build\Utility\Lib" /DLL /DEBUG
/PDB:"..\..\..\..\bin\Release/BlueMinder.pdb" /FIXED:No kernel32.lib
user32.lib gdi32.lib winspool.lib comdlg32.lib advapi32.lib shell32.lib
ole32.lib oleaut32.lib uuid.lib odbc32.lib odbccp32.lib
".\Release\BlueMinder.obj"
]
Thanks for any comments or suggestions for alternatives in achieving the
build through commandline.
Thanks
