Build libghostty-vt for baseline CPUs - #7
Merged
Conversation
To avoid over-optimizing for the build machine and to support more machines (such as Raspberry Pi 5), we need to set the cpu flag to baseline in the zig build. Fixes AnswerDotAI#6
Contributor
|
Many thanks! :) |
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.
To avoid over-optimizing for the build machine and to support more machines (such as Raspberry Pi 5), we need to set the cpu flag to baseline in the zig build.
This follows Ghostty's guidance for distributable builds and avoids build-machine CPU assumptions on every platform.
Verified on a Raspberry Pi 5: the previously crashing
Terminal(80, 24)constructor succeeds, and the unchanged existing test suite passes (9 passed).Fixes #6
Cc: @jph00