Libraries usually have header files, source code and a way to build (compile them). Header files usually are in directory named /include.

When you are compiling your project, it happens in two steps: compiling each .cpp into separate binary file and linking these binary blobs into single executable.

Header files describe (forward declare) stuff that is available in .cpp and that binary blob.

To compile .cpp file, you need all header files it uses (ft2build.h).

To link all binary blobs together, you need that compiled library (libfreetype.a) - it is a binary blob.

You have to add freetype's /include directory to your project's "include path list". When done, you can use "#include <ft2build.h>" to compile your files.

You have to add compiled "libfreetype.a" to your project's "link libraries" list. It will be linked into final executable.

Libraries usually have header files, source code and a way to build (compile them). Header files usually are in directory named /include.

When you are compiling your project, it happens in two steps: compiling each .cpp into separate binary file and linking these binary blobs into single executable.

Header files describes (forward declares) stuff that is available in .cpp and that binary blob.

To compile .cpp file, you need all header files it uses (ft2build.h).

To link all binary blobs together, you need that compiled library (libfreetype.a) - it is a binary blob.

You have to add freetype's /include directory to your project's "include path list". When done, you can use "#include <ft2build.h>" to compile your files.

You have to add compiled "libfreetype.a" to your project's "link libraries" list. It will be linked into final executable.

Basic workflow with libraries:

Libraries usually have header files, source code and a way to build (compile them). Header files usually are in directory named /include.

When you are compiling your project, it happens in two steps: compiling each .cpp into separate binary file and linking these binary blobs into single executable.

Header files describes (forward declares) stuff that is available in .cpp and that binary blob.

To compile .cpp file, you need all header files it uses (ft2build.h).

To link all binary blobs together, you need that compiled library (libfreetype.a) - it is a binary blob.

You have to add freetype's /include directory to your project's "include path list". When done, you can use "#include <ft2build.h>" to compile your files.

You have to add compiled "libfreetype.a" to your project's "link libraries" list. It will be linked into final executable.