If this is a .lib file, a static link library, then you still don't know anything about CRTs. He was not connected yet. You can learn about the intention of the original programmer, use a hexadecimal viewer to look in the .lib file, Notepad will be fine too. You will see the original command line that was used to compile the .obj files embedded in the .lib file. Just search for "cl.exe", you will have a good idea which version of the compiler was used from the path to cl.exe. And you can see the command line options to see if / MD or / MT works. And with the / O switch, it's important to have an idea of ββwhether you have a Debug or Release build.
If this is a DLL file, then dumpbin.exe / import is your best bet. The dependency on the msvcrxxx.dll file will be visible, and xxx the version number, for example "120". If you see this, the name will tell you if / MD or / MDd is used, "d" is added for the CRT debug version. If it is missing, then you know that / MT or / MTd was used, there is no hint of creating a fragrance.
Following the recommendations of the library owner is always better, you may run into big problems when CRT settings or library build settings do not meet your requirements. With a nonzero coefficient that you must set for it to update, YMMV.
Hans passant
source share