Repository navigation
Conversation
Member
Author
|
Closing: measured against Sumidoku's profile — the dsymutil storm scales with the number of large linked test binaries (45+ there vs ~9 medium ones here), so the pain doesn't justify the profile change on this repo. Easy to revisit if macOS build memory ever becomes an issue. |
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
1 participant
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.
macOS's default
split-debuginfo = "unpacked"runsdsymutilon every linked artifact, each scaling with the binary (this workspace links several large test binaries). Withoffthe debug info stays in the binary, lldb keeps working, and the release/profiling profiles are untouched. Same change as Sumidoku/Sumidoku#174.