Upgrade to a more recent version of Zephyr.#197
Draft
MMcM wants to merge 2 commits intoswiftlang:mainfrom
Draft
Conversation
This shows some new incompatibilities.
Contributor
I noticed this as well when I tried a newer Zephyr. Now the big question is- what is the best way to deal with these bit field changes? I redefined these macros as an enum on the Swift side, but maybe there's another way. |
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
2 participants
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.
This shows some new incompatibilities.
Specifically, zephyrproject-rtos/zephyr@c4c1d92#diff-d31e6c0e092586b6cc791077b8aaee7c14737ad84e51d4ef943000d062842ece changed the GPIO bit-fields to be function macros in
4.2, breaking the bridging header.