Remove target restriction from component manifest#1
Merged
Conversation
The targets list reflected hardware the component had been tested on, not a technical limitation — the library is pure C++ with no chip-specific code. Omitting the list makes the component available on all current and future ESP-IDF targets.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Removes the
targets:list fromidf_component.ymland bumps the version to 1.1.3. The list reflected hardware the component had been tested on, not a technical limitation — the library is pure C++ with no chip-specific code. Omitting it makes the component available on all current and future ESP-IDF targets (esp32c2/c5/c61/p4 and beyond).Prompted by cleishm/idfxx#55, where the same restriction propagated into dependency resolution for idfxx components.