Details
-
Bug
-
Resolution: Done
-
P2: Important
-
Qt Creator 4.11.1, Qt Creator 4.12.0-beta2
-
Qt 5.14.1
macOS
emsdk from git repo, sdk-fastcomp-1.38.27-64bit installed
macOS python 2.7.17
-
-
b057ea1ab81cbb74b05e763afa61974920886810 (qt-creator/qt-creator/master)
Description
Related to QTCREATORBUG-23126
The Webassembly kit fails to autodetect a 'standard' emscripten install. It also disables the "Choose" button and doesn't allow editing the compiler path, making the compiler (and thus kit) unusable.
Activating the emsdk (./emsdk activate) on a toolchain creates the .emscripten file in the emsdk install directory, but auto-detect checks the ~/. location. To work around this, after activation the .emscripten file can be copied to ~/. where it will be found by auto-detect.
Unfortunately the file is parsed incorrectly. While the individual defines are recognized, the emsdk_path string substitution doesn't occur, so the compiler location is prepended with "+ emsdk_path + " instead of the actual location.
Manually editing each of the defines in ~/.emscripten with the emsdk path (LLVM_ROOT = '/Users/tec/emsdk/fastcomp-clang/e1.38.27_64bit/binaryen', etc) will result in the compiler detecting properly, and in turn it can now be selected as the compiler to get the kit working.
Attachments
Issue Links
- depends on
-
QTCREATORBUG-24811 WebAssembly: Add an options page for manual Emscripten configuration
- Closed
- relates to
-
QTCREATORBUG-23126 Don't depend on $HOME for emscripten configuration
- Closed
For Gerrit Dashboard: QTCREATORBUG-23741 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
320094,41 | WebAssembly: Revamp Emscripten SDK registration and toolchain handling | master | qt-creator/qt-creator | Status: MERGED | +2 | 0 |
321797,1 | WebAssembly: Revamp Emscripten SDK registration and toolchain handling | master | qt-creator/qt-creator | Status: ABANDONED | 0 | 0 |