-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix WAVM support. #47
Conversation
Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: John Plevyak <jplevyak@gmail.com>
…to wavm Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: John Plevyak <jplevyak@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks fine, but is the any way to actually test it?
Shouldn't this be linked against WAVM in this repo? (Same for V8, really)
yes, we should test in this repo. Currently the tests are in envoy-wasm and I have a PR I am working on which will enable those tests for WAVM. Created issue: #49 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you at least open the PR in envoy-wasm so that we can verify that this builds on the CI, before merging this? Right now I cannot even tell if this compiles.
Will do. |
Signed-off-by: John Plevyak <jplevyak@gmail.com>
The attached PR uses these changes to allow WAVM to be used in envoy-wasm. |
Signed-off-by: John Plevyak <jplevyak@gmail.com>
Signed-off-by: John Plevyak jplevyak@gmail.com