Open vault-thirteen opened 7 months ago
The idea is the running emsdk active latest
and then emsdk_env.bat/emsdk_env.sh will set EMSDK_PYTHON
which and add emscripten to your PATH. python.exe
is not added to that PATH since we don't want to interfere with any existing python installation.
The idea is the running emsdk active latest and then emsdk_env.bat/emsdk_env.sh
I thought that if I use the --permanent
argument, then I do not need to run the emsdk_env
script.
Usage of this --permanent
argument should be documented.
The idea is the running emsdk active latest and then emsdk_env.bat/emsdk_env.sh
I thought that if I use the
--permanent
argument, then I do not need to run theemsdk_env
script. Usage of this--permanent
argument should be documented.
Yes, if you use --permanent
you don't need to use emsdk_env
. emsdk_env
is way to inject the settings in the current shell.
However, under no circumstances do we ever add python.exe to the user's PATH.
I think this should be documented. Because I see the python folder and consider that it should be automatically used but it turns out that I should use an external python.
Windows Install Python 3.6 or newer (older versions may not work due to a GitHub change with SSL).
It would be great to mention there that an external python should be installed before installation of the Emscripten tool and that the Emscripten tool comes with a bundled python which is for internal usage only so that it should not be used anyhow by a user.
The bundled Python is not found by
emcmake
!It's folder was added manually into the
PATH
variable but it is still "not found". How is it possible ?