September 16, 2017 at 2:49 pm #10532
I’m trying to compile all modules to Emscripten, but I keep getting:
“’em++’ is not recognized as an internal or external command, operable program or batch file.”
However “em++” is in PATH, and trying to access it manually I get:MS DOS123456789G:\>em++ -vemcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 1.37.1clang version 3.9.0 (emscripten 1.37.1 : 1.37.1)Target: x86_64-pc-windows-msvcThread model: posixInstalledDir: G:\tools\monkey2-develop\devtools\emscripten\clang\e1.37.1_64bitINFO:root:(Emscripten: Running sanity checks)WARNING:root:java does not seem to exist, required for closure compiler, which is optional (define JAVA in C:\Users\Vital.NODE\.emscripten if you want it)WARNING:root:closure compiler will not be available
So it’s obviously found…
Are the errors at the end important to Monkey 2? (Java)September 16, 2017 at 4:51 pm #10533
Alright, I’ve managed to get it going.
But now I’m getting:
“***** Fatal mx2cc error *****
Invalid value for ‘apptype’ option: ‘wasm’ – must be ‘gui’ or ‘console'”
I’ve selected Emscripten Release in Ted2Go.
No matter what I set ‘Application Type’ to, Wasm, wasm+asmjs, asmjs, I always get a similar error.September 16, 2017 at 5:13 pm #10534
I just installed Emscripten on Windows10, I had to run Command Prompt as Administrator to run ’emsdk activate –global latest’ which setup all the env stuff.
Then rebuild all the modules with Emscripten enabled.September 16, 2017 at 5:15 pm #10535
Yeah I’ve managed to get the Emscripten modules compiled.
But selecting Emscripten as my target and trying to build an app, I get the error I mentioned above.September 16, 2017 at 5:44 pm #10536
I had that error until I ran “emsdk activate –global latest” from admin command prompt from within the emsdk-portable folder. Then I added mserver-v86c to the monkey2 devtools folder.September 16, 2017 at 6:28 pm #10538
That step was part of the Emsdk “setup” so I’ve already tried that CopperCircle :/
(Tried again, rebuild modules – worked, tried building app – same error)September 16, 2017 at 6:45 pm #10539
I dont get those warnings so maybe the Emsdk install is not happy, this my result:
emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 1.37.9
clang version 4.0.0 (emscripten 1.37.9 : 1.37.9)
Thread model: posix
INFO:root:(Emscripten: Running sanity checks)September 16, 2017 at 6:56 pm #10540
Hmm okay yeah, that might be something…
It’s true, I don’t have Java installed, should I really need that?
Also, are you running the newest Monkey 2 from dev branch, along with Ted2Go from dev branch?
I think the newer M2 versions did something with emscripted.September 16, 2017 at 7:02 pm #10541
I doubt you need Java and I am running the latest itch.io M2 release v1.1.07, I also have the latest Emsdk with emscripten 1.37.9, I see yours is 1.37.1September 16, 2017 at 7:04 pm #10542
“emsdk update” then “emsdk install latest” gets me emscripten-1.37.1September 16, 2017 at 8:22 pm #10543
Have you tried a *clean* install of the v1.1.07 package?
Are you using very latest ted2go?September 16, 2017 at 9:56 pm #10547
I get the same error as Hezcore with the latest develop from the repository and emscripten 1.37.9 and I do have the latest java installed.
2013 MacBook Air with the latest OS X.
I haven’t tried the itch.io versionSeptember 16, 2017 at 10:15 pm #10548
I haven’t tried the itch.io version
Could you please try this?
I know people have a lot of ‘custom’ versions of monkey2 going so I need to be able to rule potential problems there out.September 16, 2017 at 10:15 pm #10549
I’m giving it a go now Mark
Will report back soonSeptember 16, 2017 at 10:27 pm #10550
Alas, macos has majorly broken PATH and environment vars over the years – processes no longer inherit env vars so you need to make sure env_macos.txt is correct instead of relying on system PATH.
And please make sure you have at least v1.37.9 of emscripten installed if you want to use wasm. Otherwise, stick with asmjs output.
Also, you might want to delete any emscripten folders in blah.products dirs (or just whole blah.products dir). Older versions of these could be causing problems too.
The first time you run an emscripten app now, you should get a product setting prompt asking of wasm, wasm+asmjs or asmjs apptype.
You must be logged in to reply to this topic.