I have a Visual C++ 2003 project which depends on a 3rd party static library. My visual c++ project also compiles to a static library. I have referenced the 3rd party library from my project by editing the project properties, adding the 3rd party library's directory to the Additional Library Directories (e.g. ./LibDir) and the library's name to the Additional Dependencies (e.g. 3rdParty.lib).
On my machine this works as I expected, adding this to the linker command line:
/LIBPATH:"LibDir" 3rdParty.lib
On my colleague's machine it adds this to the linker command line:
/LIBPATH:"LibDir" 3rdParty.lib "LibDir\3rdParty.lib"
This causes the 3rd party library to be linked twice, resulting in lots of errors and warnings.
This problem isn't specific to this library - it seems that whichever 3rd party library we try to include in this way on my colleague's machine ends up being added to the command line twice.
What is causing the difference in behaviour between his machine and mine?
UPDATE: I've now tested this on a third machine, which demonstrated the same behaviour as my colleague's machine, i.e. referencing an additional dependency causes it to be added twice to the linker command line (this difference happens when I open the exact same project files on each machine).
The only difference I can think of between my machine and the other two, is that I installed VC++ 2003 on my machine a couple of years ago and on the other two machines this week.
Also, it seems that this only happens if my project is compiled to a library - if it is compiled to an exe the 3rd party library only gets added to the linker command line once.
Any ideas...?