From 79511433644fc3e428e4e5619dab1da160cf6fb6 Mon Sep 17 00:00:00 2001 From: Christof Petig Date: Tue, 25 Jun 2024 23:15:02 +0200 Subject: [PATCH] readme update --- crates/cpp/tests/README.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/crates/cpp/tests/README.md b/crates/cpp/tests/README.md index e30819224..27ef59264 100644 --- a/crates/cpp/tests/README.md +++ b/crates/cpp/tests/README.md @@ -1,14 +1,14 @@ -This folder contains examples on how to use the caninical ABI without +This folder contains examples on how to use the canonical ABI without a wasm32 target. The `native_strings` folder contains an example of passing strings, with the guest in C++ and Rust, the host in C++, and in the w2c folder an -example of a wasm component transpiled to C and then executed natively. -The wamr folder creates a fully binary compatible shared object linking to +example of a wasm component transpiled to C and then executed natively. +The wamr folder creates a fully binary compatible shared object linking to wasm-micro-runtime and interpreting the wasm binary. -Please note that this demonstrates that native compilation, wasm2c and wamr are +Please note that this demonstrates that native compilation, wasm2c and wamr are binary compatible and fully exchangeable. Sadly the [w2c2](https://github.com/turbolent/w2c2) bridge code generation isn't yet complete. @@ -19,5 +19,5 @@ both guest and host defined ones. This doesn't include a wasm2c deployment. The `native_mesh` folder shows an example with resources and more than one component. Optimizing this is work in progress. -The `meshless_resources` folder experiments with directly linking -two components in a shared everything environment. +The `meshless_resources` and `meshless_strings` folders experiment +with directly linking two components in a shared everything environment.