Explicitly specify the static build of AWS-LC for linking #374
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:
In case a customer does not use
build.gradle
to build ACCP and have a separate flow for building AWS-LC, we introduce a property that can be pass to CMake that identifies the static build of AWS-LC. When shared objects for AWS-LC are also built,OPENSSL_CRYPTO_LIBRARY
defaults to the shared object. In such cases, one can setOPENSSL_CRYPTO_LIBRARY_STATIC
so that the static build would be used for linking.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.