osokin opened issue #8966:
Hi,
I was using
wasmtime-c-api
cargo build target to build Wasmtime C API for previous releases.For 22.0.0 that behavior is changed with the 566669eed20a12e8ed552abc60c51043f7702559 commit.
Could you guide me what's right approach to generate Wasmtime C API and wasmtime/conf.h file.
Thank you.
osokin edited issue #8966:
Hi,
I was using
wasmtime-c-api
cargo build target to build Wasmtime C API for previous releases.For 22.0.0 that behavior is changed with the 566669eed20a12e8ed552abc60c51043f7702559 commit.
Could you guide me what's right approach to generate Wasmtime C API and
wasmtime/conf.h
file.Thank you.
clason commented on issue #8966:
Duplicate of #8890 (TL;DR: use
cmake
to build wasmtime-c-api.)
alexcrichton commented on issue #8966:
Indeed this is a duplicate of https://github.com/bytecodealliance/wasmtime/issues/8890, so I'm going to close this in favor of that.
@osokin are you able to use CMake to build the C API? And/or use the release artifacts from this repository?
alexcrichton closed issue #8966:
Hi,
I was using
wasmtime-c-api
cargo build target to build Wasmtime C API for previous releases.For 22.0.0 that behavior is changed with the 566669eed20a12e8ed552abc60c51043f7702559 commit.
Could you guide me what's right approach to generate Wasmtime C API and
wasmtime/conf.h
file.Thank you.
osokin commented on issue #8966:
@alexcrichton Well, using
cmake
adds complexity to thedevel/libwasmtime
port in FreeBSD ports tree, takes some time for the update.
alexcrichton commented on issue #8966:
If you'd like most of us in this repo are not all that familiar with CMake so if you know of ways to improve things PRs would definitely be welcome. For example running
cargo fetch
during the cmake configuration phase I think would make sense and might fix the issue you brought up
Last updated: Nov 22 2024 at 17:03 UTC