TINYGO + WASI + wash build = YES PLEASE

[jordan-rash]

Feature or Problem

Trying to solve #512

Release Information

This adds the wasm_target value to the [tinygo] wasmcloud.toml section. Defaults to wasm but excepts wasm or wasi

Consumer Impact

Testing

I would definitely not code review this and set to auto-merge...i am highly skilled in Rust and it would be a waste of everyones time................

Built on platform(s)

• x86_64-linux
• aarch64-linux
• x86_64-darwin
• aarch64-darwin
• x86_64-windows

Tested on platform(s)

• x86_64-linux
• aarch64-linux
• x86_64-darwin
• aarch64-darwin
• x86_64-windows

[jordan-rash]

Disclaimer: if you ask my why I did something, the answer is 99% chance, "I don't know"

[brooksmtownsend]

@jordan-rash looks like it's correctly failing a test, assuming that the target is always going to be None, once that's fixed this should be good to go!

[jordan-rash]

@jordan-rash looks like it's correctly failing a test, assuming that the target is always going to be None, once that's fixed this should be good to go!

Ha, I'll try and figure that out tonight

[brooksmtownsend]

@jordan-rash bump! 😄

[vados-cosmonic]

Hey @ricochet just checking that you're fine using this by thurs without it merging (IIRC we weren't intending to cut a new release of wash for this, right?)

[vados-cosmonic]

Hey @connorsmith256 not sure why this branch is still showing conflicts (I still can't see what they actually are) but it works great on the PR to wasmcon-workshop.

Will everything survive another rebase? Tune in to the next commit to find out.

[connorsmith256]

Thanks @vados-cosmonic, I introduced another merge conflict with a different PR