It's written into "platforms" field of library.properties, IMHO is much more clearer than digging into the code
The goal is to allow to compile the same sketch (without changes) across multiple architectures so, to allow this, there should be a common header and multiple implementations (one for each architecture).
Thank you for taking the time to answer our questions.
How this key library.properties
file is going to be maintained?
Let's take the following case:
The library.properties file initially contains
- maker A releases a board based on architecture archA and updates the file accordingly
- maker B releases another board based on architecture archB and modifies the file to fit its needs
Who is going to ensure the file integrity and consolidate all the platforms to obtain
We might end up with many different versions of the library.properties