-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with emcc v3.1.31 in combination with -sMODULARIZE -sEXPORT_ES6
#3238
Comments
Thanks. Hopefully this will be fixed when we make the next release. If not we can build it with an earlier version that still works. |
I was able to compile it with When this is not released yet for the next verovio release I can create a small PR: https://github.com/WolfgangDrescher/verovio/tree/fix-3238 Or we can implement something like this:
It looks like older version had the same problem but I only noticed it now because a dependency is more strict with strict mode (either Rollup.js oder Vite, but I'm not sure about this yet). |
@WolfgangDrescher any update on this? |
Verovio var createVerovioModule = (() => {
var _scriptDir = import.meta.url;
return (
async function(createVerovioModule = {}) {
var Module=... This looks good now, but I did not test it again. I will close this issue and reopen if I run into this problem again. |
Great! Many thanks for keeping an eye on this. It is all very helpful. |
Currently
buildToolkit
is not compatible withemcc
v3.1.31 when running with-s MODULARIZE=1 -s EXPORT_ES6=1
.The JS build will contain
"use strict";
inside the async return function ofcreateVerovioModule()
:This will run into:
I will check if we need additional flags such as
-sSTRICT
or-sSTRICT_JS
or if we need to wait for the nextemcc
release.There seems to be already a merged pull request related to this: emscripten-core/emscripten#18614. As well as related issues: emscripten-core/emscripten#18610, emscripten-core/emscripten#18620.
The text was updated successfully, but these errors were encountered: