Include the possible cross-compiler targets in the README #33
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
gravemalte
changed the title
|
Please don't put an exhaustive list in the README, this will change regularly. The authoritative source for that will always be checksums.sha256sum, as it varies by host platform. Instead, it would be nice if you could list the most popular targets (win/linux/mac/raspi) and what arch triple they correspond to. |
|
Done, please review |
jwalt
requested changes
Feb 14, 2025
jwalt
requested changes
Feb 14, 2025
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.
The sha256 file is
not included anymore in the shipping of the toolchainan auto generated file which is only available in the release download.This little change provides a better overview of the possible cross-compiler targets for new users.