This repository has been archived by the owner on Mar 24, 2022. It is now read-only.
Partially address #282 - allow statically linked wasm modules #301
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
…ly excluded at compile time
|
This PR was closed as a byproduct of deleting the branch named |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This small change allows the first step in allowing use of statically linked wasm modules - allow use of symbols from the current binary. This works only if
I built this on another PR (for optionally excluding minisign) which modifies similar code so that there won't be merge conflicts. So please ignore the "combined diff of the 2 PRs/commits" and only see the diff of the one commit for this change.