rpi-rgb-led-matrix | three chains of 64x64 , 32x32 , 16x32 or similar RGB LED

The problem is that, after a long battle with downloading the library that I am trying to use, after installing a compiler, creating a file, and finding the right command to run and include paths I get undefined reference to errors.

There are already numerous questions and answers on SO pertaining to such problems, especially What is an undefined reference/unresolved external symbol error and how do I fix it?

Possible fixes that I found:

• 1. Link .cpp files in a strict order when compiling: sudo g++ main1.cpp main2.cpp
• 1. [SO question with answers saying roughly the same as the previous]

Not typically relevant. Although link order of different objects / libraries is significant, that rarely affects the case when all the needed C and / or C++ source files are specified in the same compilation command.

• 1. The need of a makefile

Using make does not inherently solve the problem, and it is certainly not necessary for solving the problem. Writing a makefile that provides for a successful build, whether directly or via a build tool such as CMake or the Autotools, requires you to understand at least at a high level how compilers and linkers work, what their inputs and outputs are, and what their arguments and options mean.

• 1. What cpp files to link if I have just one ?

You do not link a .cpp (directly) at all. You compile it and link the result to any needed libraries and any other objects. g++ will try to do that all in one step by default, in which case the process is conventionally called "compiling", not "linking", even though both functions are performed. g++ can be made to compile only, without linking, by specifying the -c option to it (which is common in makefiles, as it turns out), and it will happily link objects and libraries without compiling anything if you don't name any source files to it.

Anyway, your case is not at all that of just one .cpp file. It is your one .cpp file plus all those of the library you are trying to use.

• 1. Do I need to link all the .cpp and .h files that the library has ?

You do not need to compile (directly) or link any .h files. But if you want to use the library whose sources you downloaded, you do need to compile all the sources, and you probably should link them into an actual library. Furthermore, unless you produce and use a static library, you should also install the library you build. It looks like the library sources include a makefile, so you would be well advised to use make to perform those steps.

• 1. I don't understand a thing about makefile or why it even exists.

A makefile is the input to make. A well-written one defines rules for how to build one or more "targets", and expresses the prerequisites (generally original sources or other targets) for doing so. make uses these, together with a set of built-in rules, to figure out what steps to take to build the target(s) you ask it to build, and also what steps it can skip. It is typical, for example, to write makefiles so that if you build a multisource project, modify only one source file, and then build again, only the modified source gets recompiled.

This may seem trivial when you're used to projects with only a handful of sources, but it becomes important in larger projects, where full rebuilds are expensive -- many hours, in some cases. But even if a full build takes only a few minutes, if you really only needed to spend a few seconds then that adds up to a lot of wasted time over a full day of work.

Overall, then:

When do I need to use/have a makefile?

Never. But providing a good one and using make to build your project has these among its advantages:

• memorializing all the needed build commands, including options and arguments, in a persistent, actionable form, and therefore
• providing for consistent, automated builds.

Those can also be achieved by a simple build script, but make also can give you

• faster builds by building only those pieces that are out of date, and
• built-in knowledge of how to build certain kinds of targets from corresponding sources.