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
Then I indeed did a yarn build, pushed the new index.js that got generated, and tried to install the fork.
Upon trying to use it, I get greeted by the following error:
index.js:1 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'prototype')
at D.initClass (index.js:1:935979)
at index.js:1:936495
at Set.forEach (<anonymous>)
at index.js:1:936476
initClass @ index.js:1
(anonymous) @ index.js:1
(anonymous) @ index.js:1
Promise.then (async)
(anonymous) @ HSWFC.js:36
I suspected that it was because of the following piece of code at the end of eigen.mjs that adds the GC to the classes, since it still has the QuadProgSolver in there:
After removing "QuadProgSolver" it indeed started working. I'm not savvy enough in web build tools to come up with a nicer solution for this, but maybe it is good to put a disclaimer/warning in the readme for now about it, so people can still perform a functioning yarn build without OSQP in there.
The text was updated successfully, but these errors were encountered:
Hey there, I tried forking this repo and building without OSQP as instructed in the readme using the latest version of emscripten:
emcc -D NO_OSQP -I lib/eigen -Isrc -s DISABLE_EXCEPTION_CATCHING=0 -s ASSERTIONS=0 -O3 -s ALLOW_MEMORY_GROWTH=1 -s MODULARIZE=1 --bind -o build/eigen_gen.js src/cpp/embind.cc
Then I indeed did a
yarn build
, pushed the newindex.js
that got generated, and tried to install the fork.Upon trying to use it, I get greeted by the following error:
I suspected that it was because of the following piece of code at the end of
eigen.mjs
that adds the GC to the classes, since it still has theQuadProgSolver
in there:After removing
"QuadProgSolver"
it indeed started working. I'm not savvy enough in web build tools to come up with a nicer solution for this, but maybe it is good to put a disclaimer/warning in the readme for now about it, so people can still perform a functioningyarn build
without OSQP in there.The text was updated successfully, but these errors were encountered: