0

I've installed emsdk, following the steps described in the following document: https://emscripten.org/docs/getting_started/downloads.html#sdk-download-and-install

Now, when I launch a Terminal under macOS, I have these lines inserted at the beginning:

Setting up EMSDK environment (suppress these messages with EMSDK_QUIET=1)
Adding directories to PATH:
PATH += [private]/emscripten/emsdk
PATH += [private]/emscripten/emsdk/upstream/emscripten
PATH += [private]/emscripten/emsdk/node/14.18.2_64bit/bin

Setting environment variables:
PATH = [private]/emscripten/emsdk:[private]/emscripten/emsdk/upstream/emscripten:[private]/emscripten/emsdk/node/14.18.2_64bit/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Little Snitch.app/Contents/Components:/usr/local/share/dotnet:/opt/X11/bin:~/.dotnet/tools:/Library/Apple/usr/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands
EMSDK = [private]/emscripten/emsdk
EM_CONFIG = [private]/emscripten/emsdk/.emscripten
EMSDK_NODE = [private]/emscripten/emsdk/node/14.18.2_64bit/bin/node
EMSDK_PYTHON = [private]/emscripten/emsdk/python/3.9.2_64bit/bin/python3
SSL_CERT_FILE = [private]/emscripten/emsdk/python/3.9.2_64bit/lib/python3.9/site-packages/certifi/cacert.pem

I can't find from where this is launched. emsdk doesn't appear in .bash_profile, nor in .profile or .bashrc.

Where do I have to set EMSDK_QUIET=1 to avoid these lines?

Benoît Lahoz
  • 1,270
  • 1
  • 18
  • 43
  • Pretty sure you just export it as an envar in your .bashrc if using bash or .zshrc if using zsh – Jared Smith Oct 04 '22 at 17:15
  • Oh ! Thank you, I forgot I passed to zsh while upgrading to macOS Monterey. I, actually have this line in .zprofile: source "[private]/emscripten/emsdk/emsdk_env.sh" But no .zshrc file... – Benoît Lahoz Oct 04 '22 at 17:28
  • 1
    You might echo something to make sure your zprofile is getting sourced when you start the terminal – Jared Smith Oct 04 '22 at 17:58
  • If it is then you should be able to export the envar there – Jared Smith Oct 04 '22 at 17:58
  • I echo EMSDK_QUIET=1 but it still happens on other (newly opened) terminal windows and after reboot. – Benoît Lahoz Oct 05 '22 at 09:01
  • Not "echo" but "export". – Benoît Lahoz Oct 05 '22 at 09:11
  • Did you echo something to make sure that file is getting sourced when you start your shell? And did you set it prior to sourcing the emsdk_env script? – Jared Smith Oct 05 '22 at 12:10
  • @JaredSmith You should post this as an answer: exporting EMSDK_QUIET=1 before the line added by emsdk on install did the trick. The problem was that I didn't have any .zprofile before installing emsdk (I upgraded macOS to Monterey a few days ago), so I never thought of searching for this file. Thank you! – Benoît Lahoz Oct 06 '22 at 08:09

2 Answers2

1

A lot of times when you install a program that needs to alter the environment like compiler toolchains the install script will modify the file it expects to be sourced by your shell based on the default shell for the current user or sometimes by scanning $HOME. On MacOS you might see it add a line to (or create if it can't find):

  • $HOME/.bashrc or $HOME/.bash_profile for bash
  • $HOME/.zshrc or $HOME/.zprofile for zsh
  • $HOME/.config/fish/config.fish for fish

Note that recent versions of MacOS have changed the default shell from bash to zsh. Due to licensing issues they have to ship an archaic version of bash (3.2 vs 5.x current) so it was probably a good move but it means you may need to check the zsh files instead of the usual bash ones.

When you need to set an envar for a toolchain like EMSDK_QUIET=1 just look for the line where the environment is sourced, and export that envar above it.

Jared Smith
  • 19,721
  • 5
  • 45
  • 83
0

According to official documentation of recommended installing Emscripten using emsdk (Emscripten SDK), the last move in the procedure is:
#Activate PATH and other environment variables in the current terminal
source ./emsdk_env.sh"
So this script is at the core of generating said message, exposed at the beginning of every new shell session. Logic dictates that the suppressor of this event (EMSDK_QUIET=1) should be placed in it, because emsdk_env.sh is defined as source, right?
One possible location of "export EMSDK_QUIET=1" could be at the bottom section of the script (# Force emsdk to use bash syntax...) before the line "eval EMSDK_BASH=1 "$DIR/emsdk" construct_env".

cyberslot
  • 1