JacekCz wrote: First of all, rarely is "xxxx.h" a library, even if all the holy arduino people say so.
A library can be a header and it is not that rare. There is nothing stopping you from putting everything into the file "xxxx.h" and including this file in your own project. You just need to use the appropriate macro instructions so that you don't have the problem of redefinitions.
TDA2593 wrote: As far as I know "Secrets.h" is not a standard library in Arduino and I don't think it can be "normally" downloaded, installed. It allows to store confidential data in a special file.
How to deal with it? How does it work
Can it be uncommented? Because I did, but I can't connect to the router.
The "secret.h" file is not a library but has a project configuration function implemented in a rather twisted and incorrect way. Generally such things are not placed in a repository and this file should be generated usually from the "secret.h.in" file where the placeholders are located. Such an example using cmake where from the file "config.h.in" with the following contents:
the file "config.h" is generated:
This happens when using "cmake" for the first time and the name of this configuration file "config.h", should be found in ".gitignore". When using other tools (e.g. "./configure" from Autotools) this pattern "xxx.h.in -> xxx.h" is also used. Configurations could be entered from your finger as a macro when calling gcc, then you do not need to include "secret.h":
this prevents sensitive data from being placed in the code, but with this way of configuring the project, it is worth ensuring that the compiler provides all the necessary macros, e.g. something like this:
The ArduinoIDE is crippled and there is rather no option to generate the appropriate configuration for the project and ask the user for data. That's why in the "examples" for a given library there should be a tutorial on how to create such a file and inform the user not to smoke a fool and put it in the repository.
