Open kriswuollett opened 1 year ago
I'm not sure what's going on here, but two things I noticed when looking at the package:
staticlib
and cdylib
, and we probably filter it out in a few places in: https://github.com/bazelbuild/rules_rust/blob/44aec0a793492ec9ffbef1c7ea7697043fd38750/crate_universe/src/metadata/dependency.rswasmtime
which conflicts with another crate in the workspace, which plausibly is confusing something somewhereI'd probably start instrumenting around those two things, to debug this further
(To be explicit - we expect subcrates to work fine, but this one seems specially broken in some way)
Using the following does not result create a
@crate_index//:wasmtime-c-api
target:I'd expect that it would have created a target that provides headers and library outputs that would be usable from a C/C++ target as shown in c_calling_rust, but it does not:
Is producing subcrate target an unimplemented feature? What would be the workarounds in the meantime if not supported? Vendor in
wasmtime-c-api
myself? Just write my own C API wrapper that exposes what I need? The Wasmtime C API is the example I'd like to make work.