You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey! I'd like to build a basic compiler (for now) for a programming language, which will compile the code into a WASM module. I'd like that module to be runnable in wasmer as well as in the browser. I considered building the API for my language's runtime in another WASM (which I'm going to compile from Rust). And then I'd like to statically link the language's runtime with the user's WASM and produce a single WASM on the output.
My questions are:
what the role of the compiler in wasmer? It produces an item, which only wasmer can instantiate? Or it's possible to serialize it into a WASM module, which I could run in the browser later?
Is it possible to statically link WASM modules using wasmer or in another way? How to do this if so?
Can I achieve it using Artifact::generate_object and then link the objects into a single WASM?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey! I'd like to build a basic compiler (for now) for a programming language, which will compile the code into a WASM module. I'd like that module to be runnable in wasmer as well as in the browser. I considered building the API for my language's runtime in another WASM (which I'm going to compile from Rust). And then I'd like to statically link the language's runtime with the user's WASM and produce a single WASM on the output.
My questions are:
Artifact::generate_object
and then link the objects into a single WASM?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions