Use native cargo `wasm32-wasip2` target rather than `cargo-component`

[kate-goldenring]

Before the wasm32-wasip2 target was added to Rust, cargo-component did a lot of the heavy lifting to enable rust developers to create p2 components. Now, it is more advantageous to directly use Rust tooling. The docs should be updated to use cargo build --target wasm32-wasip2 plus manual use of wit-bindgen and wkg. This will also better familiarize users with the ecosystem and provide more impetus to get more functionality into the Rust ecosystem

[vados-cosmonic]

Related issue bytecodealliance/cargo-component#399

[vados-cosmonic]

Possible way forward here according to @macovedj -- we can use the --target flag for cargo component

Create a new WebAssembly component package at <path>

Usage: cargo component new [OPTIONS] <path>

Arguments:
  <path>  The path for the generated package

Options:
  -q, --quiet                  Do not print log messages
  -v, --verbose...             Use verbose output (-vv very verbose output)
      --color <WHEN>           Coloring: auto, always, never
      --cache-dir <CACHE_DIR>  The path to the cache directory to store component dependencies [env: CARGO_COMPONENT_CACHE_DIR=]
      --config <CONFIG>        The path to the pkg-tools config file [env: CARGO_COMPONENT_CONFIG_FILE=]
      --vcs <VCS>              Initialize a new repository for the given version control system (git, hg, pijul, or fossil) or do not initialize any version control at all (none), overriding a global configuration [possible values: git, hg, pijul, fossil, none]
      --bin                    Create a CLI command component [default]
      --lib                    Create a library (reactor) component
      --proxy                  Use the built-in `wasi:http/proxy` module adapter
      --edition <YEAR>         Edition to set for the generated crate [possible values: 2015, 2018, 2021]
      --namespace <NAMESPACE>  The component package namespace to use [default: component]
      --name <NAME>            Set the resulting package name, defaults to the directory name
      --editor <EDITOR>        Code editor to use for rust-analyzer integration, defaults to `vscode` [possible values: emacs, vscode, none]
  -t, --target <TARGET>        Use the specified target world from a WIT package
      --registry <REGISTRY>    Use the specified default registry when generating the package
      --no-rustfmt             Disable the use of `rustfmt` when generating source code
  -h, --help                   Print help

Unrecognized subcommands will be passed to cargo verbatim after relevant component bindings are updated.

[vados-cosmonic]

Echoing some discussion during the docs meeting, it might make sense to get the feel of current cargo component maintainers here before we move forward -- and be extra sure that we should switch to Rust + wkg + wit-bindgen etc rather than using a single amalgamated tool

[kate-goldenring]

The maintainers of cargo-component have suggested moving away from using it as a tool. This should now be prioritized.

[catamorphism]

@vados-cosmonic I'd be happy to work on this if you're not actively working on it.

[vados-cosmonic]

Hey @catamorphism thanks! Work on this is actually done but there are bigger questions about the organization of the guide in general -- see the discussion in #310 !

[vados-cosmonic]

We could easily merge the current code, but I really don't think we should be mixing creating a basic component and all the other complicated stuff we do afterwards in the same tutorial, basically. This is something that probably needs to get discussed though.

[catamorphism]

Ah, didn't see the pending PR. I'll take a look at the discussion.

[vados-cosmonic]

This is done as of #310