What's the difference between libraries and includes?

[cpthk]

Many IDE today could set libraries directories and includes directories. What is the difference between them?

Thanks.

[WingedPanther]

You normally include header files, which are just source code. You link libraries, which are already compiled.

[cpthk]

there are also a place to link binaries, so what's the difference between binaries and libraries?

For example, in Dev C++, in the options:
wagjo.com/fileadmin/wagjo/images/boost/devc2.gif
(sorry, it's a link to a image, I cannot post a link or image yet)

[Mathematix]

Originally Posted by cpthk

Many IDE today could set libraries directories and includes directories. What is the difference between them?

Thanks.

The 'includes' provide the compiler with a way of determining where aspects of your code are defined. These 'includes' in conjunction with your preprocessor directives determine your translation units. The translation unit is that part of the code that is built into your executable.

During the build stage you will encounter a stage called 'linking' that refers to these libraries in order to 'resolve externals'. When there are conflicts or ambiguities between libraries and the includes that determine which libraries are to be included, you end up with 'unresolved externals' that don't give you very much information on what went wrong. Why not much information? Because the problem is ambiguous, so cannot be pinpointed by the linker.

[Mathematix]

Originally Posted by cpthk

there are also a place to link binaries, so what's the difference between binaries and libraries?

For example, in Dev C++, in the options:
wagjo.com/fileadmin/wagjo/images/boost/devc2.gif
(sorry, it's a link to a image, I cannot post a link or image yet)

See above for libraries. 'Binaries' are files that are not in a text format, so cannot be directly read by a text editor, for example. Binaries are files with a .exe, .dll or .obj extension, for example.