Advertisement

Why is Visual Studio so hateful when warning about defaultlib conflicts?

Started by May 20, 2020 11:51 PM
2 comments, last by fleabay 4Β years, 6Β months ago

The most notorius being

LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of other libs; use /NODEFAULTLIB:library

So somehow a .lib file got into my project that I downloaded or incorrectly built. Not sure when or how it happened but I just noticed it after a full rebuild.

Why in the world can't Visual Studio just tell me what .lib file is the problem? Why do I have to crawl through library files with a command line utility to see which one is the problem? WHY???

πŸ™‚πŸ™‚πŸ™‚πŸ™‚πŸ™‚<←The tone posse, ready for action.

Maybe it's challenging you to write a program to find the culprit?

Advertisement

Alberth said:
Maybe it's challenging you to write a program to find the culprit?

πŸ™‚πŸ™‚πŸ™‚πŸ™‚πŸ™‚<←The tone posse, ready for action.

This topic is closed to new replies.

Advertisement