diff options
| author | SZEDER Gábor <szeder.dev@gmail.com> | 2019-02-25 15:21:36 +0100 |
|---|---|---|
| committer | SZEDER Gábor <szeder.dev@gmail.com> | 2019-07-04 22:19:18 +0200 |
| commit | d4ae799795d3c1f096d83b94e498715fbf9a1296 (patch) | |
| tree | bbd4b4ba25d2a2cf9c56c081921d8875cdbccd92 /examples/README.md | |
| parent | cf5d016746c82e72c501ee10dfd55be6bf937d83 (diff) | |
Build the ArduinoCore API
As part of the big modularizing efforts of the Arduino project they
split out the hardware-independent layer of the Arduino "language"
from the hardware-specific cores into the dedicated 'ArduinoCore-API'
repository. As described in 'ArduinoCore-API's README, the API source
files won't reside directly in the directory of the standard Arduino
core, i.e. in 'ARDUINO_CORE_PATH', but in its 'ARDUINO_CORE_PATH/api'
subdirectory. Consequently, Arduino-Makefile won't be able to build
any projects when using an Arduino core following the new directory
structure.
Prepare for the upcoming new Arduino core directory structure by
building all 'ARDUINO_CORE_PATH/api/*.cpp' source files as well. Out
of caution, look out for and build any .c source files in that
directory, too: though there are no .c source files in the
'ArduinoCore-API' repository at the moment, in the future there might
be. Furthermore, add this directory to the list of directories to be
searched for header files: though it's not necessary to explicitly and
directly include any header file from this directory ('Arduino.h'
includes all there is), some projects might nonetheless do so, and
their build would then break.
Note that a 'make clean' will be most likely necessary when
re-building a project after switching to the new directory structure.
Diffstat (limited to 'examples/README.md')
0 files changed, 0 insertions, 0 deletions
