bug: Unexpected error when running get-string example about wasmedge

[hydai]

@q82419 Please check if our previous bugfix is making this issue disappear.

[PinappleUnderTheSea]

@q82419 Please check if our previous bugfix is making this issue disappear.

Commits after 8be2282 did not mention these files or cases

[q82419]

Hi @PinappleUnderTheSea ,

I tested on the latest master and it works well.

# At the path of WasmEdge
$ WASMEDGE_PLUGIN_PATH=build/examples/plugin/get-string/  ./build/tools/wasmedge/wasmedge --string="HELLO_WORLD" test.wasm
HELLO_WORLD

Please check again. Thanks!

[PinappleUnderTheSea]

Hi @PinappleUnderTheSea ,

I tested on the latest master and it works well.

# At the path of WasmEdge
$ WASMEDGE_PLUGIN_PATH=build/examples/plugin/get-string/  ./build/tools/wasmedge/wasmedge --string="HELLO_WORLD" test.wasm
HELLO_WORLD

Please check again. Thanks!

sorry to trouble, I do not know WasmEdge well. I tried:

 ./build/tools/wasmedge/wasmedge --string="HELLO_WORLD" test.wasm

but the terminal shows:

unknown option: string

Is there something I ignored?

[q82419]

Maybe you didn't build from master, or didn't assign the correct plug-in path.
The option is for the plug-in, the example get-string plug-in registered the option string, so that when loading the plug-in, this option can be accepted by the CLI.

[PinappleUnderTheSea]

WASMEDGE_PLUGIN_PATH=build/examples/plugin/get-string/  ./build/tools/wasmedge/wasmedge --string="HELLO_WORLD" test.wasm

It works!!! Thanks a lot.