Stream: git-wasmtime

Topic: wasmtime / issue #7567 wasmtime 15.0.0 - how to build a s...

Wasmtime GitHub notifications bot (Nov 21 2023 at 15:09):

osokin opened issue #7567:

Hi,

I'm using libwasmtime, C API of wasmtime, to build a wasm module for NGINX Unit.
Previously it worked well by specifying crates/c-api/Cargo.toml configuration for cargo.
Since 15.0.0 that doesn't work anymore. Could you guide me how can I build a static library
for the recent version?

Thank you.

Wasmtime GitHub notifications bot (Nov 21 2023 at 15:29):

bjorn3 commented on issue #7567:

https://github.com/bytecodealliance/wasmtime/pull/7341 changed the layout. Looks like you now have to specify crates/c-api/artifact/Cargo.toml instead.

Wasmtime GitHub notifications bot (Nov 21 2023 at 15:45):

osokin closed issue #7567:

Hi,

I'm using libwasmtime, C API of wasmtime, to build a wasm module for NGINX Unit.
Previously it worked well by specifying crates/c-api/Cargo.toml configuration for cargo.
Since 15.0.0 that doesn't work anymore. Could you guide me how can I build a static library
for the recent version?

Thank you.

Wasmtime GitHub notifications bot (Nov 21 2023 at 15:45):

osokin commented on issue #7567:

Thanks for the quick reply, @bjorn3! That works!

Wasmtime GitHub notifications bot (Nov 21 2023 at 17:04):

pchickey commented on issue #7567:

Instead of using --manifest-path whatever/Cargo.toml, use -p wasmtime-c-api for your build scripts to be resilient against these sorts of changes.

Wasmtime GitHub notifications bot (Nov 21 2023 at 17:34):

osokin commented on issue #7567:

Instead of using --manifest-path whatever/Cargo.toml, use -p wasmtime-c-api for your build scripts to be resilient against these sorts of changes.

Thanks for the update, @pchickey! I'm going to update the build procedure according your recommendations.

Last updated: Nov 22 2024 at 17:03 UTC