Richard explained the issue(s) to you. I will only add that I really don't like the way this has to be dealt with most of the time. Thankfully, you are using VisualStudio so it is easier. I do this in a two-step approach. First, make sure the libraries you link with are either in a standard library directory for your installation (not preferred) or in a unique place where you installed them which I prefer. I sometimes uninstall the compiler and reinstall it and that can be a problem if you put other libraries in with it. The second step is I make a file with the link commands or add them in with the file that calls the functions of the library. To be more specific, I use #pragma statements to specify the libraries to link with. Here's what one looks like :
#pragma comment( lib, "ExtensionLib19DUS64" )
I like this because you can use conditional compilation to link with different libraries, depending on your situation. For me, the suffixes there all mean something. That one is the VS2019, debug, unicode, static RTL, 64-bit version of my extensions library. With conditional compilation macros I can link with the correct version always. I find this is a major PITA if you do it in the project file itself for every build option.
In your case, I recommend adding a series of pragma statements to specify exactly which libraries you want to link with. The library's documentation should tell you which ones those are. The pragmas can go in almost any module your code compiles, depending on your preference. I put them in a separate header for just the library in question, along with any ifdefs that might affect which library files are needed to link with.
Submit an article or tip