Change binary stripping settings for scikit-build-core #2980
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
…ies. If building in Release mode there is nothing to strip anyway.
garth-wells
approved these changes
Jan 11, 2024
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 does not change the default stripping policy of scikit-build-core (true).
The docker end user images are built by default in release mode without binary stripping. This leads to small binaries as there are no debug symbols in release mode.
The README is updated to add a scikit-build-core config flag to not strip debug symbols, so that it is possible to debug!
Also removes the broken CMAKE_CXX_FLAGS stuff as pointed out by @mhabera.
Resolves #2948.