gcc-arm-none-eabi: build common embedded archs instead of everything (~6x faster) - #20
Merged
Merged
Conversation
Member
Author
|
Builds fine on buildbot (25mins on an 8 core machine) |
This was referenced Jun 20, 2026
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.
So the
gcc-arm-none-eabitakes like an hour and a half, which mostly is fine as it runs concurrently, but the reason its doing that is because its building newlib / libstdc++ for like 70+ different architectures. This is a bit much for now.This change builds only for 6-7 common embedded architectures that this package plans to support. Adding more is trivial. This should speed up the build and the amount of work that needs to get done.