isn't it have to be -DARDUINO_ARCH_ARDUINOCORE_RENESAS ?
1 Like
@b707 found the culprit!
The macro comes from this part of the command pattern:
-DARDUINO_ARCH_{build.arch}
The build.arch property is predefined by the platform framework. The value is determined by the name of the architecture folder under which the platform is installed. So the cause of the problem is that you named your architecture folder ArduinoCore-renesas.
Beyond the problem of macro name limitations, you should also be careful to always name the architecture folder in your manual platform installations with the standardized architecture name (in this case renesas or renesas_uno). The reason is that the architecture name is a factor in library selection.
The specific name of the "vendor" folder of the platform installation doesn't have any technical implications so you should use this folder name to differentiate the manually installed platform in cases where you have also installed the same platform via Boards Manager. For example, I use this installation folder structure for my manual installation of the development version of the "Arduino AVR Boards" platform:
<sketchbook location>/
├── hardware/
│ ├── arduino-dev/
│ │ ├── avr/
│ │ │ ├── boards.txt
│ │ │ ...
│ │ ...
│ ...
...
I arbitrarily chose the convention of adding a -dev suffix to the standard vendor name for my installations of development versions of platforms. I see you do the same.
In the case of the arduino/ArduinoCore-renesas platform, just using renesas as the architecture folder name should be sufficient differentiation. The reason is that the Boards Manager distribution of the platform is split into board families (renesas_portenta, renesas_uno), so there won't be any name collision between a manually installed platform using renesas architecture and the Boards Manager installation even if you used the same vendor name arduino for the manual installation.
The developers use renesas as the architecture folder name of their manual installations since the manual installation provides support for all boards and thus it doesn't make sense to use one of the family-specific architecture names. For this reason, the developers add the renesas architecture to the architectures field of the metadata files of the official libraries in addition to the family-specific architecture names. I don't know how well the 3rd party library developers have followed this convention.
You can leave the arduino-dev folder named arduino-dev. It isn't mandatory in this specific case, but it can be useful anyway to serve as a single container for all your manual installations of platforms from the arduino vendor (some of which might require differentiation e.g., arduino-dev:avr vs. arduino:avr).
But yes, you should rename the ArduinoCore-renesas folder to renesas. After that, the warnings should no longer occur.
1 Like
You are welcome. I'm glad it is working now.
Regards,
Per
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.