Repository navigation
moved to different CBoringSSL - #13
Merged
Merged
Conversation
…ess to required functions anymore
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
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.
due to swift-nio-ssl now not giving access to required functions anymore I moved to a fork of Adam Fowler’s big-num. It provides a cut down version of BoringSSL and most importantly: doesn’t force me to pin swift-nio-ssl to something compatible.
Originally I didn’t want to, but due to binary size alone I might end up making a wrapper for libsecret in the future. This is more of a fix for the current issue.