-
Notifications
You must be signed in to change notification settings - Fork 6.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add module and toolchain-bundled Picolibc synchronisation policy #58006
Merged
carlescufi
merged 4 commits into
zephyrproject-rtos:main
from
stephanosio:picolibc_sync_policy
May 25, 2023
Merged
Add module and toolchain-bundled Picolibc synchronisation policy #58006
carlescufi
merged 4 commits into
zephyrproject-rtos:main
from
stephanosio:picolibc_sync_policy
May 25, 2023
Conversation
This file contains 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
This commit adds "Zephyr SDK version compatibility" section to the Zephyr SDK documentation, which provides a link to the "Zephyr SDK Version Compatibility Matrix" and describes the recommended Zephyr SDK version. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the documentation to link, instead of the latest, the specific release of Zephyr SDK referenced in the documentation because the latest version is subject to change and may not be compatible with the particular Zephyr release. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the link to the "Zephyr SDK Releases" page to point to the "Tags" page instead of the "Releases" page because: * "Tags" page is easier to browse by version. * Download links are not properly rendered on the "Releases" page due to a GitHub limitation (release body preview content length limit). Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit clarifies that the toolchain-bundled Picolibc in the Zephyr SDK must also be updated when updating the Picolibc module. Signed-off-by: Stephanos Ioannidis <[email protected]>
60 tasks
keith-packard
approved these changes
May 18, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, will require updating for each Zephyr release to keep the SDK version up to date, of course.
cfriedt
approved these changes
May 25, 2023
carlescufi
approved these changes
May 25, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 series adds the policy for keeping the Picolibc module and the toolchain-bundled Picolibc in sync.
Related to zephyrproject-rtos/sdk-ng#673
Part of #49922