What's the difference between "Add to project" and "#pragma comment(lib,"mylib.lib")"

Oh,my god~I've got panic~~~It's already 21 views,but no response~~...

My bet is that the lib you're including with #pragma comment is linked with a different version of the libraries.

For example, your project might be linking to the single threaded versions of the runtime libraries, while the library is linking to the multithreaded versions. Make sure they're the same.

If you're using Visual C++, then the setting is under Project Properties , C/C++, Runtime Library.

Quote:

Original post by Oxyacetylene My bet is that the lib you're including with #pragma comment is linked with a different version of the libraries. For example, your project might be linking to the single threaded versions of the runtime libraries, while the library is linking to the multithreaded versions. Make sure they're the same. If you're using Visual C++, then the setting is under Project Properties , C/C++, Runtime Library.

No,exactlly there is only 1 .lib file.Maybe you could do a test as I said.
e.g. using zlib in a MFC project.

The pragma approach is Microsoft (and probably Intel) compiler specific, if you want your code to be portable, you should either add the lib to the project or add the lib to the libraries variable on the project linking options.

You shouldn't link in the CRT to a library, let the main app link it.

#pragma comment(lib, ...) is an MS extention that's the same as adding the library to your link list.

Quote:

Original post by Kwizatz The pragma approach is Microsoft (and probably Intel) compiler specific, if you want your code to be portable, you should either add the lib to the project or add the lib to the libraries variable on the project linking options.

oh...my god...

Quote:

Original post by Kwizatz The pragma approach is Microsoft (and probably Intel) compiler specific, if you want your code to be portable, you should either add the lib to the project or add the lib to the libraries variable on the project linking options.

The rule is that unrecognized pragmas must be ignored. The problem is that two compilers could still interpret the same pragma in different ways.

Quote:

Original post by Fruny Quote: Original post by Kwizatz The pragma approach is Microsoft (and probably Intel) compiler specific, if you want your code to be portable, you should either add the lib to the project or add the lib to the libraries variable on the project linking options. The rule is that unrecognized pragmas must be ignored. The problem is that two compilers could still interpret the same pragma in different ways.

Right, I remember having problems with "#pragma once" when I started using GCC (2.95 or so) it used to ignore them, and hell broke lose.

My bad. [smile]

Quote:

Original post by Fruny The rule is that unrecognized pragmas must be ignored. The problem is that two compilers could still interpret the same pragma in different ways.

I'd love to see some other compilers implement #pragma curious_george, #pragma gpfault prettyplease and #pragma keeka!

Enigma