search

emscripten-core / emsdk

Emscripten SDK
http://emscripten.org
Other
2.96k stars 676 forks source link

`emsdk activate latest --permenant` does not add user's environment variables (PATH, ...) #1312

Open vault-thirteen opened 8 months ago

vault-thirteen commented 8 months ago

D:\Temp\1\emsdk>emsdk activate latest --permenant

Resolving SDK alias 'latest' to '3.1.50'
Resolving SDK version '3.1.50' to 'sdk-releases-2ce4170cef5ce46f337f9fd907b614a8db772c7d-64bit'
Setting the following tools as active:
   node-16.20.0-64bit
   python-3.9.2-nuget-64bit
   java-8.152-64bit
   releases-2ce4170cef5ce46f337f9fd907b614a8db772c7d-64bit

Adding directories to PATH:
PATH += D:\Temp\1\emsdk
PATH += D:\Temp\1\emsdk\upstream\emscripten

Setting environment variables:
PATH = D:\Temp\1\emsdk;D:\Temp\1\emsdk\upstream\emscripten;[...]
EMSDK = D:/Temp/1/emsdk
EMSDK_NODE = D:\Temp\1\emsdk\node\16.20.0_64bit\bin\node.exe
EMSDK_PYTHON = D:\Temp\1\emsdk\python\3.9.2-nuget_64bit\python.exe
JAVA_HOME = D:\Temp\1\emsdk\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 register this environment permanently, rerun this command with the option --permanent.

After closing this window and opening a new Command Prompt I see that no environment variables are saved. Windows' tools also tell me that none of that variables were saved.

sbc100 commented 8 months ago

Sorry, there was a typo in the original version of #1308. --permanent was spelt wrong in the message.