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
if(GLFW.active.cursorPosFunc){((a1,a2,a3)=>{throw'Internal Error! Attempted to invoke wasm function pointer with signature "vidd", but no such functions have gotten exported!'})(GLFW.active.id,Browser.mouseX,Browser.mouseY);}
I'm sort of lost here, I can register glfwSetCharCallback and other callbacks work fine,
all callback functions are declared exactly the same way, and yet that 'throw' code is being generated specifically for the glfwSetCursorPosCallback.
This happens when building a side module:
I tried the following flags:
-sSIDE_MODULE=1
-sUSE_GLFW=3
-sEXPORT_ALL
-sLINKABLE
The callbacks and the glfw functions are in a library which is linked to the side module,
the code loads the side module at runtime.
The text was updated successfully, but these errors were encountered:
Note that when you build side module there is no .js that gets generated, the .js file is built when you build the main module. What are the flags you are using when you build the main module?
I'm sort of lost here, I can register glfwSetCharCallback and other callbacks work fine,
all callback functions are declared exactly the same way, and yet that 'throw' code is being generated specifically for the glfwSetCursorPosCallback.
This happens when building a side module:
I tried the following flags:
-sSIDE_MODULE=1
-sUSE_GLFW=3
-sEXPORT_ALL
-sLINKABLE
The callbacks and the glfw functions are in a library which is linked to the side module,
the code loads the side module at runtime.
The text was updated successfully, but these errors were encountered: