Changes between Version 3 and Version 4 of Ticket #5020

03/23/2017 02:30:22 PM (3 years ago)

Added last part, the one making the script compatible with Windows. It makes the process of retrieving Emscripten configuration somewhat more robust by reading .emscripten configuration file directly instead of relying on stable emsdk output. In the process I found out that Emscripten on Windows isn't exactly a well-supported solution:

  • Node.JS path will be misconfigured. The issue has been fixed months ago but didn't make it into the download package yet. So you will have to edit emsdk_manifest.json of your installation manually.
  • In theory, both Visual Studio 2013 and Visual Studio 2015 are supported (Express Edition and probably the full one as well). However, emsdk will default to the former and you need to use the undocumented --vs2015 command line flag if you want to use Visual Studio 2015. Build directories are different which is why you have to add this flag to any emsdk command - not merely install but activate as well. This is even true when activating tools that weren't compiled at all, simply because it won't recognize compiled tools as active and remove them from configuration.
  • Even with the provisions above I couldn't make Emscripten activate correctly - the path to the native optimizer was always wrong, pointing to the missing Visual Studio 2013 version. I had to edit the configuration file manually to fix that.
  • #pragma once support requires help from the file system, so you shouldn't compile on a VirtualBox shared folder. If you do clang will get confused because it treats compiled\filter\..\String.h and compiled\String.h as different files.


  • Ticket #5020 – Review URL(s)

    v3 v4