I have spent some time to explore the dynamic linking in emscripten/wasm 
and I have a couple of questions for my understanding.

As I see I have following options to load dynamically:


   1. Use `Module.dynamicLibraries` and provide a list of side modules that 
   are being loaded and linked during the *start up* of the main module. So 
   if one of the side modules is big, the start up takes longer.
   2. `dlopen` and `dlsym`: this needs the modules to be available in the 
   file system.
   3. `loadDynamicLibrary` during run time. Can asynchronously fetch 
   another side_module a link during run time


So the questions:

   - Is `3` the only way to prevent loading the side modules only when 
   needed?
   - For `2`: Do I need to expose all my side module functions with `extern 
   "C"` so that `dlsym` finds them?
   - To me, `3` seems to win by far: I only load the modules when I need 
   them, and I don't have to worry about `extern "C"` and the function 
   signatures/returns

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to