feat: add optional Unix-only BoringSSL symbol prefixing #1
Conversation
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
Can't build with clang-12 to libc++ mismatch
jmayclin
reviewed
Dec 18, 2025
Owner
Author
|
Once this is approved+merged, I’ll update aws/s2n-tls#5659 to pull from main instead of this branch. main keeps the fork up to date via https://wei.github.io/pull/ |
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.
PR Description
This PR adds an optional prefix-symbols feature to boring and boring-sys that prefixes all BoringSSL libssl/libcrypto symbols to avoid collisions with OpenSSL or other BoringSSL variants.
What this does
Adds a prefix-symbols Cargo feature.
Unix-only build logic that:
Why
This enables BoringSSL to safely coexist with OpenSSL build inside the same process - necessary for interoperability testing with s2n-tls