vincent

Quick update: Try linking static libfmt.a in SDK build.rs but still get error, still trying to find possible causes. ``` = note: /usr/bin/ld: /home/vincent/workspace/_docker/_ctr/test_wasmedge_static_link/target/debug/deps/libwasmedge_sys-bb01cfa1ba8bae59.rlib(section.cpp.o): in function `WasmEdge::Loader::Loader::loadSection(WasmEdge::AST::Component::CoreTypeSection&)': section.cpp:(.text+0x3952): undefined reference...

~~Yes~~ Not yet, wait for the next WasmEdge 0.14.1 release, which will include commit a498fb1.

Got the message, I’ll pin our colleague responsible for releasing the WasmEdge SDK to check when they can help release the Rust crate that includes lib version 0.14.1.

The missing wasi-nn headers in the wasiNNTest for the burn plugin require this part to be rewritten, which will take some time. Considering the priority, I keep only the release...

I have added a "flexibility" section to the original description, providing users with customization options.

After https://github.com/containerd/runwasi/pull/877, the upstream now supports the wasi_nn plugin. However, support for various plugins is still limited due to https://github.com/WasmEdge/WasmEdge/issues/4003 related to auto_detect triggering. The current mechanism for using plugins...

Waiting for #3830.

I will double-check this, but in my memory, the current WasmEdge should be fine with plugins when using the dynamic linking WasmEdge approach. The upgrade to WasmEdge 0.14.1 (which requires...

I think using the plugin in a simple example will be fine, and I will submit a PR along with a showcase as soon as possible (e.g., using wasi_nn only)....

After https://github.com/containerd/runwasi/pull/877, the upstream now supports the wasi_nn plugin. However, support for various plugins is still limited due to the issue mentioned earlier related to auto_detect_plugin function. Check out the...