Skip to content
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

Verify C++ Wasm extension walkthrough guide #24

Open
bianpengyuan opened this issue Nov 30, 2020 · 2 comments
Open

Verify C++ Wasm extension walkthrough guide #24

bianpengyuan opened this issue Nov 30, 2020 · 2 comments

Comments

@bianpengyuan
Copy link
Collaborator

We recently added a walk through guide for C++ Wasm extension development: https://github.com/istio-ecosystem/wasm-extensions/blob/master/doc/write-a-wasm-extension-with-cpp.md. Before sharing it more broadly, it would be great if we can get some feedback about it internally from folks who do not work on writing Wasm extensions day by day.

@douglas-reid @richardwxn It would be really nice if you could please take a look it. Thanks!

@bianpengyuan
Copy link
Collaborator Author

cc @mandarjog

@klarose
Copy link

klarose commented May 6, 2021

Thanks for putting this together! I've been trying to walk through this myself. I'm running into a few issues:

  1. The .bazelversion in the example repo does not always align with the version in the upstream istio repo where we fetch the latest envoy hashes as part of get-dep.sh. This leads to the script silently failing.
  2. The WORKSPACE file is insufficent: it does not load some of the required modules. Perhaps it'd be better to just point to the example.wasm one?
  3. I cannot get the integration test (example/test/example_test.go) to run. It cannot import the test module from this repo, which makes me suspect it intends to run as part of this repo. Since the walkthrough is geared towards somebody working in their own repo, it'd be helpful to either describe how to modify this file for your local repo, or move any test scaffolding out into its own go module.
  4. I had to add a go.mod to the root of my repo to even start running the integration test. I've never really worked in a mixed cpp/golang env before, so I'm not sure if that's necessary or normal (is there a better way to initialise the dependencies?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants