A zillion LNK4204 warnings...
-
"... is missing debugging information for referencing module; linking object as if no debug info." Here's what I'm doing: 1) I have a third-party library that I am building as a separate solution. It generates .lib and .pdb files. 2) I have a library that I've written that I use in all my solutions. So, logically, I should be able to take the third-party .lib and .pdb files and add the .lib to my .lib's dependency chain (Properties->Librarian->General->Additional Dependencies) and build and everything should be okay. But it isn't. For whatever reason, despite specifically generating a unique name for the .pdb file for the third-party .lib, I still get LNK4204 warnings. Is there a way to get the linker or librarian to include the contents of another .pdb file into another executable/library .pdb file?
-
"... is missing debugging information for referencing module; linking object as if no debug info." Here's what I'm doing: 1) I have a third-party library that I am building as a separate solution. It generates .lib and .pdb files. 2) I have a library that I've written that I use in all my solutions. So, logically, I should be able to take the third-party .lib and .pdb files and add the .lib to my .lib's dependency chain (Properties->Librarian->General->Additional Dependencies) and build and everything should be okay. But it isn't. For whatever reason, despite specifically generating a unique name for the .pdb file for the third-party .lib, I still get LNK4204 warnings. Is there a way to get the linker or librarian to include the contents of another .pdb file into another executable/library .pdb file?
Does the third party lib uses default pdb file name.
-
Does the third party lib uses default pdb file name.
From my original message, "despite specifically generating a unique name for the .pdb file for the third-party .lib, I still get LNK4204 warnings" If it were that simple I wouldn't be asking.