mchung's profile - activity

overview network karma followed questions activity

2019-01-18 02:39:16 -0600	received badge	● Editor (source)
2019-01-18 02:39:16 -0600	edited question	How can I compile OpenCV.js so that it does not require defining the "onRuntimeInitialized" field? How can I compile OpenCV.js so that it does not require defining the "onRuntimeInitialized" field? I'm trying to expose
2019-01-18 02:37:24 -0600	marked best answer	How can I compile OpenCV.js so that it does not require defining the "onRuntimeInitialized" field? I'm trying to expose more opencv modules to the existing opencv.js javascript module. Following the official opencv instructions https://docs.opencv.org/3.4.5/d4/da1/..., I was able to build a wasm version of opencv.js (see here for more details), but it behaves differently than the one provided in the npm pkg - https//www.npmjs.com/package/opencv.js Specifically, the opencv.js I built require me to define the "onRuntimeInitialized" field in the imported module (as reported by others, see here) where the one provided in npm pkg does not (see here, their module does not have "onRuntimeInitialized" and "wasmMaxTableSize", "wasmMemory", ... that are existing in the opencv.js I built). I believe I can build opencv like the person who built the opencv.js like changing some emscripten flags for, but can't figure out what those flags are. Here are some places where the build script provided by opencv is setting emscripten flags: * https://github.com/mjyc/opencv/blob/j... * https://github.com/mjyc/opencv/blob/j... How can I can build an wasm so it does not require me to define "onRuntimeInitialized" but loads all required modules at the import time?
2019-01-18 02:37:24 -0600	received badge	● Scholar (source)
2019-01-18 02:17:08 -0600	asked a question	How can I compile OpenCV.js so that it does not require defining the "onRuntimeInitialized" field? How can I compile OpenCV.js so that it does not require defining the "onRuntimeInitialized" field? I'm trying to expose