Migrate runtime builds from Envoy repository to cpp-host #113

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.

Sign up for GitHub

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

Jump to bottom

Open

mathetake opened this issue Dec 6, 2020 · 0 comments

Labels

build

Contributor

mathetake commented Dec 6, 2020 •

edited

Loading

Runtime build issues/handling should be decoupled from host implementations, e.g. the link time symbol issue envoyproxy/envoy#14012

TODOs:

have BUILD files for WAVM and V8 (hopefully without gen_rules Migrate wee8 from genrule to BUILD file envoyproxy/envoy-wasm#206)
- V8: https://github.com/envoyproxy/envoy/blob/master/bazel/external/wee8.BUILD
- WAVM: https://github.com/envoyproxy/envoy/blob/master/bazel/foreign_cc/BUILD#L314-L342
have exactly the same lib targest as in https://github.com/envoyproxy/envoy/blob/master/bazel/external/proxy_wasm_cpp_host.BUILD
- ${runtime}_lib

Related to #49

The text was updated successfully, but these errors were encountered:

mathetake added the build label

mathetake mentioned this issue

Resolve symbol collisions among Wasm runtimes #139

Closed

mathetake mentioned this issue

build: refactor Bazel configuration towards multiple runtime tests #160

Merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment