emcc -- command not found

[briefy]

i referenced the tutorial http://webassembly.org/getting-started/developers-guide/
and found a similar issue #5696

however i cannnot figure out how can this be done?
i really wanna use emcc to test wasm

[kripken]

More information could let us help you better: what OS are you on? How did you install the emsdk? Did you get any errors while doing so? What is the full error you get when trying to run emcc?

[briefy]

@kripken .
i am using a macOS x, and i am sure other requirements are met
there are no errors, it only says emcc: command not found at last
i checked the emsdk directory, i didnt find any file name emcc

the steps are, exactly the same by the tutorial

git clone https://github.com/juj/emsdk.git
cd emsdk
./emsdk install latest
./emsdk activate latest

[kripken]

On linux at least, you need to do source ./emsdk_env.sh after those commands after first installation (as it may in the path next time you open a shell, but in the current shell, it hasn't been done yet). That's mentioned after the activate step on http://kripken.github.io/emscripten-site/docs/getting_started/downloads.html

I'm not sure how MacOS handles that kind of thing. But maybe it's the same?

[bnjm]

I ran into this problem on MacOS too even after running through the thread: #5696

In my case I hadn't run the activate step after installing:
./emsdk activate --global --build=Release sdk-incoming-64bit binaryen-master-64bit

[kmturley]

I solved by adding this line to my .bash_profile file:

# Web Assembly paths
source "/Users/${USER}/Sites/emsdk/emsdk_env.sh"

[stale]

This issue has been automatically marked as stale because there has been no activity in the past year. It will be closed automatically if no further activity occurs in the next 7 days. Feel free to re-open at any time if this issue is still relevant.

[sebastienmascha]

More accurate is:
source path/to/emsdk/emsdk_env.sh

If you do not want to run this command each time you reload your terminal, you should put it on .bash_profile (as suggest @kmturley) or .zprofile if you're using ZSH.