Is there way to use embind and have multiple "modules" or "namespaces" bundled in one WASM package?

[ayanb73]

I have a project that I want to be it's own standalone WASM module, but I'd also like to include it in bigger projects by compiling it in. However, it would get really messy if all of that was accessed via the same exported interface.

[sbc100]

The names which embind exports are fixed at compile time and embedded in the static constructors of the wasm module.

You could imagine compiling your code twice, once for direct use and once for indirect usage. For example when you compile standalone.wasm you might define -DEMBIND_EXPORT_NAMESPACE= (empty) and then when build libembedme.a (the library other authors would use to link your code into their wasm module then you could define -DEMBIND_EXPORT_NAMESPACE=myprog.

I think you would need to compile twice anyway since there is no easy way to embed one fully linked wasm into another (i,.e. you probably want to use the static library method).

Within your code you could then have the EMSCRIPTEN_BINDINGS export functions in the EMBIND_EXPORT_NAMESPACE namespace. I assume this is possible, but I don't know exactly how that that part would work. @brendandahl would know. (Sorry if this is actually your question and therefore I have not answered it).