Wenyong Huang

BTW, the PR https://github.com/bytecodealliance/wasm-micro-runtime/pull/3650 was merged, had better rebase your code with main branch.

@lucasAbadFr thanks for the update! It seems that you have basically implemented the feature and all the CIs run succeeded, so is it ready for code review?

> I am working on getting WASI support working on Zephyr and came across this thread. Are there any plans to complete and merge this PR? I'm happy to contribute,...

> @wenyongh that works for me. Great! I think @lucasAbadFr is busy and may not be able to response quickly, so I merged this PR to branch `dev/zephyr_file_socket`, please help...

> @wenyongh please feel free to jump in. I hope I've wrote down everything we've discussed. > > From what we know, we are hoping this feature will cover: >...

> i'm reasonably familiar with the convention as i have implemented it for other runtime. https://github.com/yamt/toywasm/tree/master/libdyld > > i have even considered to port it to wamr. the main obstacle...

> Are there any users relying on the multi-module support today that can not easily port to dynamic linking (i.e. recompile their code while upgrading WAMR)? Given that mult-module is...

> Not sure what do you mean by the `host managed heap`? I was initially thinking we could just export `malloc` from the module and call it from WAMR when...

> Ah ok, yes I'm familiar with the app heap concept, just didn't know that you're talking about the same thing - thanks for clarifying. However, I think using app...

@loganek Thanks for the explanation and the experiment. Agree to investigate more and make a good decision. For the malloc function, if it isn't exported by wasm module and libc...