Emscripten: 'em++' is not recognized

About Monkey 2 Forums Monkey 2 Programming Help Emscripten: 'em++' is not recognized

This topic contains 57 replies, has 7 voices, and was last updated by  Richard Betson 1 year, 5 months ago.

Viewing 15 posts - 1 through 15 (of 58 total)
  • Author
    Posts
  • #10532

    Hezkore
    Participant

    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:

    So it’s obviously found…
    Are the errors at the end important to Monkey 2? (Java)

    #10533

    Hezkore
    Participant

    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.

    #10534

    CopperCircle
    Participant

    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.

    #10535

    Hezkore
    Participant

    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.

    #10536

    CopperCircle
    Participant

    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.

    #10538

    Hezkore
    Participant

    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)

    #10539

    CopperCircle
    Participant

    I dont get those warnings so maybe the Emsdk install is not happy, this my result:

    em++ -v
    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)
    Target: x86_64-pc-windows-msvc
    Thread model: posix
    InstalledDir: C:\emsdk-portable\clang\e1.37.9_64bit
    INFO:root:(Emscripten: Running sanity checks)

    #10540

    Hezkore
    Participant

    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.

    #10541

    CopperCircle
    Participant

    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.1

    #10542

    Hezkore
    Participant

    Hmm..
    “emsdk update” then “emsdk install latest” gets me emscripten-1.37.1

    #10543

    Mark Sibly
    Keymaster

    Have you tried a *clean* install of the v1.1.07 package?

    Are you using very latest ted2go?

    #10547

    Jesse
    Participant

    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 version

    #10548

    Mark Sibly
    Keymaster

    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.

    #10549

    Hezkore
    Participant

    I’m giving it a go now Mark
    Will report back soon

    #10550

    Mark Sibly
    Keymaster

    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.

Viewing 15 posts - 1 through 15 (of 58 total)

You must be logged in to reply to this topic.