-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
add wasm builds; requires emsdk path #1928
base: develop
Are you sure you want to change the base?
Conversation
c128d79
to
586fad9
Compare
586fad9
to
6849d64
Compare
It's probably a better UX if the user can navigate to the SDK path directly. So this needs some tweaking for the emsdkPathValue input. |
@@ -39,7 +40,8 @@ class ExporterSettingsPanel : public Component | |||
"C++ Code", | |||
"Electro-Smith Daisy", | |||
"DPF Audio Plugin", | |||
"Pd External" | |||
"Pd External", | |||
"JS / WebAssembly" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or should we just call it WebAssembly
?
(it looks a bit off like this)
@@ -100,6 +103,7 @@ class ExporterSettingsPanel final : public Component | |||
state.appendChild(views[1]->getState(), nullptr); | |||
state.appendChild(views[2]->getState(), nullptr); | |||
state.appendChild(views[3]->getState(), nullptr); | |||
state.appendChild(views[4]->getState(), nullptr); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see now there is a conflict with OWL feature.
We can merge that one first and then adjust accordingly.
Work in progress, but already works on my machine ;)
Also it should have a check that fails early when the user didn't enter any emsdk path.
I wonder if for Windows we can just use the
emsdk_env.sh
since we run everything in a bash shell, so definitely needs some testing on all platforms.