Add simple header-only logger with macros

[margheritamilani]

Introduce log.hpp for enable or disable logging at
runtime with the specif macro.

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (1/10)

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (2/10)

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (3/10)

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (4/10)

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (5/10)

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (6/10)

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (7/10)

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (8/10)

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (9/10)

[github-actions]

⚠️ Clang-Tidy found issue(s) with the introduced code (10/10)

[EddyTheCo]

The class Log is very simple it only allows to enable/disable logs at runtime.
Enabling/disabling the logs at runtime it is mostly done by reading a config file or in the main function.
The class is publicly visible in the API and LCM_LOG only use one standard output stream(cerr,cout,clog...).

In my opinion if what we want is a simple turn on,off of the logs I will go for enabling/disabling the logs at compile time.
The consumer of the library can decide if enabling the logs by setting a CMake variable.
This variable can be set before doing FetchContent_MakeAvailable(GDbusCpp) so consumers can easily change if they want to see the logs of this project libraries.
The logs can be turned on in the development package but turned off in the runtime package.
I would try to separate the logs by standard output stream.

[AndreaRicchi]

The class Log is very simple it only allows to enable/disable logs at runtime. Enabling/disabling the logs at runtime it is mostly done by reading a config file or in the main function. The class is publicly visible in the API and LCM_LOG only use one standard output stream(cerr,cout,clog...).

In my opinion if what we want is a simple turn on,off of the logs I will go for enabling/disabling the logs at compile time. The consumer of the library can decide if enabling the logs by setting a CMake variable. This variable can be set before doing FetchContent_MakeAvailable(GDbusCpp) so consumers can easily change if they want to see the logs of this project libraries. The logs can be turned on in the development package but turned off in the runtime package. I would try to separate the logs by standard output stream.

No, @EddyTheCo, we cannot force the user to recompile the entire library to see logs. The idea is correct; it involves simple logging that can be enabled at runtime.

[EddyTheCo]

Will be nice if an issue is opened describing why this change/enhancement is needed.

[EddyTheCo]

From the code part it looks good to me.
I do not know the reason why this change is needed nor there is an issue explaining it.

In my opinion creating a log class to activate/deactivate the logs for a single library at runtime introduce much logic to the library that is not needed nor is the purpose of this repo/library.

An Amarula::Log class and library should be created and linked to this library or for simplicity enable/disable logs at compile time for this library.

[AndreaRicchi]

From the code part it looks good to me. I do not know the reason why this change is needed nor there is an issue explaining it.

In my opinion creating a log class to activate/deactivate the logs for a single library at runtime introduce much logic to the library that is not needed nor is the purpose of this repo/library.

An Amarula::Log class and library should be created and linked to this library or for simplicity enable/disable logs at compile time for this library.

This is needed because we cannot force the user to have prints that his not requesting. Since there is no need for logging level or more complex logic at the moment, this is a simple way to disable/enable prints. And again, we cannot force the user to recompile the library every time to enable or disable the logs.