On Jun 18, 8:05???am, David Wilkinson <no-re...@effisols.com> wrote:
Cartoper:
If you are linking a static library to your project, both your project and the
library must be built using the same version of the compiler, and the same
settings. You need to recompile your library using VS2005 (or VS2008).
David,
What you say is most definitly logical and normally I would not argue,
except... I DO have a VS2005 that is statically linking to a VC6
library and it links and runs just fine.
I think all would be well, IF I can fix the Manifest Tools options.
The project that compiles and runs fine has this Manifest Tools
options:
/nologo /out:.\Debug\RunJustFine.exe.embed.manifest /notify_update
And the one that will not load looks like this:
/nologo /outputresource:".\Debug\mod_willNotLoad.so;#2"
I don't mind hacking the .vcproj file, but I compared the two and
neither one has anything that looks like it set the manifest tools
options, so I am assuming that both are simply using default options.
Again the mod_willNotLoad.so is a DLL and the RunJustFine.exe is an
executable.
1. Does your .lib have a plain C interface, and/or just classes with all pure
virtual functions? In that case it could work.
2. When I look at your link errors like
LIBCMTD.lib.
But I also see MSVCR80.dll. If this is the debug build why do you not have