Calling "emsdk activate --global latest" hangs when setting environment variables.

[timhutton]

Platform: Windows 10, Python 2.7.13

Without the --global option the command runs very quickly and succeeds. With --global it hangs here:

...
Setting environment variables:
EMSDK = c:/emscripten

WORKAROUND: emsdk activate latest

(From this commit it looks like this acts globally anyway.)

[sbryfcz]

I have the same issue. Platform Windows 10. Python 3.6.3.

[juj]

With --global the Windows UAC elevation prompt should appear to ask for permission to permanently add the PATHs and environment variables to registry. If that does not happen and you're getting a hang before that line, I wonder if running Windows Command Prompt in Administrator mode might help avoid the issue?

[sbryfcz]

The UAC prompt never appeared for me. And I tried in Adminstrator mode but nothing happened except it hanging.

[Slluxx]

+1

[d07RiV]

Same issue. It worked fine on my other machine, but here no matter what I do, it hangs before setting LLVM_ROOT, and none of the variables it claims to have set appear in global environment. Tried both cmd and powershell in administrator mode.

[aplumly]

anyone find a fix for this?... apart from setting all the env variables by hand?

[roman-petrov]

Today I spent a hour trying to investigate this issue on my machine. As I see the hang caused by win32api.SendMessage(win32con.HWND_BROADCAST, win32con.WM_SETTINGCHANGE, 0, 'Environment')
call in emsdk Python script.

Found some on StackOverflow https://stackoverflow.com/questions/1951658/sendmessagehwnd-broadcast-hangs

Still not sure if there is a simple workaround, but maybe removing this system call should work. Or we can use SendMessageTimeout in this call as they suggested on StackOverflow.

I am new with emsdk so I am not sure what is the right solution, need help...

[roman-petrov]

Right solution might be to use PostMessage vs SendMessage in https://github.com/emscripten-core/emsdk/blob/master/emsdk#L263

Can anybody give an advice?...