Sync FindCrypto. Add option to force crypto linkage #2829
Merged
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.
Description of changes:
Syncs FindCrypto from S2N, and adds option to force usage of static or dynamic crypto.
The reason these options are being introduced is to force the SDK to use a static or dynamic libcrypto independent of
BUILD_SHARED_LIBARIES
. Currently ifBUILD_SHARED_LIBARIES
is set to OFF there is no way to force the SDK to use a dynamic libcrypto.running with something like
will result in static crypto being chosen over dynamic if dynamic is present
will result on dynamic crypto being used even though we are building statically
Check all that applies:
Check which platforms you have built SDK on to verify the correctness of this PR.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.