Details
-
Bug
-
Resolution: Done
-
Not Evaluated
-
Qt Creator 4.15.1
-
None
-
Windows, Emsdk 1.39.20
-
Windows
-
2bc7f6603c93f9754b5dfe7a86ea0b42ae17f35f (qt-creator/qt-creator/4.15)
Description
The current emsdk version does not add the python interpreter to the path (which it ships on Windows) but sets the EMSDK_PYTHON environment variable:
Adding directories to PATH: C:\Users\alportal\dev\emsdk\node\14.15.5_64bit\bin C:\Users\alportal\dev\emsdk\upstream\emscripten C:\Users\alportal\dev\emsdk Setting environment variables: EM_CACHE=C:/Users/alportal/dev/emsdk/upstream/emscripten\cache EM_CONFIG=C:\Users\alportal\dev\emsdk\.emscripten EMSDK=C:/Users/alportal/dev/emsdk EMSDK_NODE=C:\Users\alportal\dev\emsdk\node\14.15.5_64bit\bin\node.exe EMSDK_PYTHON=C:\Users\alportal\dev\emsdk\python\3.9.2-1_64bit\python.exe JAVA_HOME=C:\Users\alportal\dev\emsdk\java\8.152_64bit
"Launch with emrun" currently just searches in the path and might fail to find a suitable Python interpreter. It should instead look at EMSDK_PYTHON first and if absent fall back to searching in the path.
The resulting error message looks like this:
10:32:33: Checking available ports... 10:32:33: Found 1001 free ports. 10:32:33: Starting C:/Users/alportal/dev/emsdk/upstream/emscripten/emrun.py --browser firefox --port 30000 --no_emrun_detect --serve_after_close C:/Users/alportal/dev/qtcreator-bug-snippets/QTCREATORBUG-25030/build-qtquickcontrols2-qmake-Qt_5_15_4_WebAssembly-Debug/qtquickcontrols2-qmake.html... 10:32:33: No executable specified.