By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement . We’ll occasionally send you account related emails.

C:\emsdk-main>emsdk activate latest
Resolving SDK alias 'latest' to '2.0.24'
Resolving SDK version '2.0.24' to 'sdk-releases-upstream-6ab7fc5622a67e6111d07c4ba61c8d3c8fc33ed2-64bit'
Setting the following tools as active:
node-14.15.5-64bit
python-3.9.2-1-64bit
java-8.152-64bit
releases-upstream-6ab7fc5622a67e6111d07c4ba61c8d3c8fc33ed2-64bit

Adding directories to PATH:
PATH += C:\emsdk-main
PATH += C:\emsdk-main\node\14.15.5_64bit\bin
PATH += C:\emsdk-main\upstream\emscripten

Setting environment variables:
PATH = C:\emsdk-main;C:\emsdk-main\node\14.15.5_64bit\bin;C:\emsdk-main\upstream\emscripten;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Users\SonMiguel\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Bandizip
EMSDK = C:/emsdk-main
EM_CONFIG = C:\emsdk-main.emscripten
EMSDK_NODE = C:\emsdk-main\node\14.15.5_64bit\bin\node.exe
EMSDK_PYTHON = C:\emsdk-main\python\3.9.2-1_64bit\python.exe
JAVA_HOME = C:\emsdk-main\java\8.152_64bit
Clearing existing environment variable: EMSDK_PY
The changes made to environment variables only apply to the currently running shell instance. Use the 'emsdk_env.bat' to re-enter this environment later, or if you'd like to permanently register this environment permanently, rerun this command with the option --permanent.

C:\emsdk-main>emsdk_env.bat
Setting environment variables:
PATH = C:\emsdk-main;C:\emsdk-main\upstream\emscripten;C:\emsdk-main\node\14.15.5_64bit\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Windows\System32\OpenSSH;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\NVIDIA NvDLISR;C:\Users\SonMiguel\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Bandizip
Clearing existing environment variable: EMSDK_PY

C:\emsdk-main>emcc -v
Traceback (most recent call last):
File "C:\emsdk-main\upstream\emscripten\emcc.py", line 23, in
from tools.toolchain_profiler import ToolchainProfiler
ModuleNotFoundError: No module named 'tools'

cheking the enscripten folder I can found toolchain_profiler.py (C:\emsdk-main\upstream\emscripten\tools\toolchain_profiler.py)
but emcc returned error.
how can I resolve this?

Will that is very odd.. can you try running emsdk.py via python directly:

> C:\emsdk-main\python\3.9.2-1_64bit\python.exe C:\emsdk-main\upstream\emscripten\emcc.py

Can you verify that C:\emsdk-main\upstream\emscripten\tools\__init__.py exists?

I can't imagine why python wouldn't be able to find the tools module alongside emcc.py . Do you any anything else in your environment that could effect python in some way?

I've got same error from python direct execute
> C:\emsdk-main\python\3.9.2-1_64bit\python.exe C:\emsdk-main\upstream\emscripten\emcc.py

and C:\emsdk-main\upstream\emscripten\tools\__init__.py file is exist.
I have format my computer recently, so another environment cannot effect python...

This is very odd indeed. Its seems python cannot load module that exist alongside the script itself.

Can you try something even simpler. Can you change directory to C:\emsdk-main\upstream\emscripten and then run C:\emsdk-main\python\3.9.2-1_64bit\python.exe -c "import tools" . That should work, but I'm guess its doesn't on your machine for some reason.

Can you maybe dump the contents of your environment and post it here? I think on windows you can just do set to get this list.

reinstall seems ok

# Get the emsdk repo
git clone https://github.com/emscripten-core/emsdk.git $HOME/OneDrive/Code/apps/emsdk
# Enter that directory
cd $HOME/OneDrive/Code/apps/emsdk
# Fetch the latest version of the emsdk (not needed the first time you clone)
git pull
# Download and install the latest SDK tools.
$HOME/OneDrive/Code/apps/emsdk/emsdk install latest
# Make the "latest" SDK "active" for the current user. (writes .emscripten file)
$HOME/OneDrive/Code/apps/emsdk/emsdk activate latest
# Activate PATH and other environment variables in the current terminal
source $HOME/OneDrive/Code/apps/emsdk/emsdk_env.sh