>This is true for a static library but the import library for a DLL won't >contain references to the CRT - the main problem with a C++ import >library is that the symbol mangling has changed - there are probably >issues with class layout changing between compiler versions too Yeah, that's what I was trying to say with:
"(well, a LIB for DLL, maybe; but, it's better to just regenerate the LIB from the DLL with the latest librarian)." ... but I wasn't very clear. I don't know the details, but I've actually run into a DLL that wouldn't link with an application compiled with a different version of VC. I've never run into a situation where a LIB (non-import-library) compiled with one version of VC worked when linked with another version of VC. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
