Switch to using PlatformIO's advanced scripting for building ESP-IDF version #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the project builds an example project that makes use of a modified version of the ESP-IDF HomeKit SDK as a component. This results in static library files being generated which we can extract and link to our Arduino projects. Whilst this works, it's cumbersome and makes it difficult to make changes to configuration variables in the SDK.
This updated version makes use of PlatformIO's advanced scripting to clone the ESP-IDF HomeKit SDK repo and add the modifications for ESP-IDF v3.x. This'll result in the project using the library from source like most libraries and make it much easier to add build flags.
Using advanced scripting this way also means I don't need to host copies of the SDK's source in this repository, or in a fork, since the changes for the port are minimal.
The packages uploaded to PlatformIO's repository and used by the Arduino IDE will contain the complete library, as the build script will be run before packaging.