I think I understand the issue here. We support emscripten “JavaScript libraries”, which are specially constructed JavaScript files. These are hooked in at compile time with the compiler option “–js-library”, which in turn means that it’s executed in order to obtain information about variables etc.
To my knowledge, you cannot hook in “plain” .js-files into the emscripten build.
As I see it, you have two options:
-
Create a Emscripten “JavaScript library” out of your file:
Documentation: [Interacting with code — Emscripten 4.0.0-git (dev) documentation]
Example: library_browser.js (more) -
Put the .js file in the
/res
folder, to add it to your bundle.
Then interact with that file, either via Native Extensions or Lua
Clarification, the DEF-2815 I created was regarding the "org.eclipse.core.runtime.AssertionFailedException: assertion failed: Marker property value is too long: ". I currently don’t think the “failure to execute js library” is something we can solve at this point.