ci: add wasm OpenSSL dependency for httpfs#546
Draft
adsharma wants to merge 1 commit into
Draft
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
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.
Summary
Adds a pinned prebuilt OpenSSL dependency for the wasm package build and wires it into the static
httpfsbuild path.Current status
This is intentionally a draft PR. The branch preserves the work so we can continue later, but CI is not green yet.
The latest CI attempt confirms that CMake can now find OpenSSL for the wasm target:
The remaining blocker is that the current prebuilt
jedisct1/openssl-wasmartifact is configured withOPENSSL_NO_SOCK, socpp-httplibfails whenCPPHTTPLIB_OPENSSL_SUPPORTtries to useBIO_new_socket.Validation
git diff --checkBIO_new_socketcompile issue described above.