LDFLAGS Fix (and API bump) for ARM64-v8a and OpenSSL 1.1.1c #16
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
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.
Changes:
Result:
The CURL build under arm64-v8a completes successfully. The resulting libraries could then be used on an Android device, successfully connecting to a mapservice over HTTPS.
I noticed that I was required to also include the libcrypto.so.1.1 and libssl.so.1.1 in addition to the libcrypto.so and libssl.so files. It appears that the libcrypto.so and libssl.so files are now just symlinks to the .1.1 files.
I tested my android app against an ArcGIS MapServer (https://sampleserver6.arcgisonline.com/arcgis/rest/services/World_Street_Map/MapServer), and was able to use the GDAL to open a dataset, and clip a region successfully.