LNK4221:
You get this warning when you add resources to a static library. Okay, but what does that really mean?
LNK2001: unresolved external symbol, "symbol"
We have all seen this one, first thing I always check is the vcproj to ensure I told the linker to use someLib.lib; seems obvious, but it is easy to forget. In fact, I just did this very thing. And that simple mistake is captured here in this blog entry in hopes you will not have to make the mistake as often; don't fool yourself - we'll all still forget it sometimes....
LNK2005: symbol already defined in object
Just ran into this again... and #6 of MSDN's fixes is to add /FORCE:MULTIPLE to the linker comand line options, and make sure that uuid.lib is the first library referenced. but it did not help so my issue was something else.
Subscribe to:
Post Comments (Atom)
I am refactoring a library and getting LNK2019 unresolved external symbol 'symbol' referenced in function 'function'
ReplyDeletewhen linking the library into the unittest ... and realized that some object files were not being generated for the simple lack of the files being added to the vcproj, even though the files were present for compilation...