emsdk activate doesn't write to home directory

[vadi2]

I can't get emsdk activate to write to ~/.emscripten, it keeps writing to the sdk directory. What can I do?

vadi@gooseberry:~/Programs/emsdk$ ./emsdk activate latest
Writing .emscripten configuration file to user home directory /home/vadi/Programs/emsdk
The Emscripten configuration file /home/vadi/Programs/emsdk/.emscripten has been rewritten with the following contents:

import os
emsdk_path=os.path.dirname(os.environ.get('EM_CONFIG')).replace('\\', '/')
LLVM_ROOT = '' + emsdk_path + '/fastcomp/fastcomp/bin'
BINARYEN_ROOT = '' + emsdk_path + '/fastcomp'
EMSCRIPTEN_ROOT = '' + emsdk_path + '/fastcomp/emscripten'
EMSCRIPTEN_NATIVE_OPTIMIZER = '' + emsdk_path + '/fastcomp/bin/optimizer'
NODE_JS = '' + emsdk_path + '/node/12.9.1_64bit/bin/node'
TEMP_DIR = '' + emsdk_path + '/tmp'
COMPILER_ENGINE = NODE_JS
JS_ENGINES = [NODE_JS]

To conveniently access the selected set of tools from the command line, consider adding the following directories to PATH, or call 'source ./emsdk_env.sh' to do this for you.

   /home/vadi/Programs/emsdk:/home/vadi/Programs/emsdk/fastcomp/emscripten:/home/vadi/Programs/emsdk/node/12.9.1_64bit/bin

Set the following tools as active:
   releases-fastcomp-d57bfdd6d43181501bbd3fab502d57c9073ceb49-64bit
   node-12.9.1-64bit

vadi@gooseberry:~/Programs/emsdk$ ./emsdk activate --embedded latest
Writing .emscripten configuration file to Emscripten SDK directory /home/vadi/Programs/emsdk
Backing up old Emscripten configuration file in /home/vadi/Programs/emsdk/.emscripten.old
The Emscripten configuration file /home/vadi/Programs/emsdk/.emscripten has been rewritten with the following contents:

import os
emsdk_path=os.path.dirname(os.environ.get('EM_CONFIG')).replace('\\', '/')
LLVM_ROOT = '' + emsdk_path + '/fastcomp/fastcomp/bin'
BINARYEN_ROOT = '' + emsdk_path + '/fastcomp'
EMSCRIPTEN_ROOT = '' + emsdk_path + '/fastcomp/emscripten'
EMSCRIPTEN_NATIVE_OPTIMIZER = '' + emsdk_path + '/fastcomp/bin/optimizer'
NODE_JS = '' + emsdk_path + '/node/12.9.1_64bit/bin/node'
TEMP_DIR = '' + emsdk_path + '/tmp'
COMPILER_ENGINE = NODE_JS
JS_ENGINES = [NODE_JS]

To conveniently access the selected set of tools from the command line, consider adding the following directories to PATH, or call 'source ./emsdk_env.sh' to do this for you.

   /home/vadi/Programs/emsdk:/home/vadi/Programs/emsdk/fastcomp/emscripten:/home/vadi/Programs/emsdk/node/12.9.1_64bit/bin

Set the following tools as active:
   releases-fastcomp-d57bfdd6d43181501bbd3fab502d57c9073ceb49-64bit
   node-12.9.1-64bit

vadi@gooseberry:~/Programs/emsdk$ 

Using the latest e047fe4 commit.

[sbc100]

I believe that once you pass the --embedded flag to emsdk it creates the config file in the emsdk directory, and the it continues to use the presence of that file that you want to be in the embedded mode. This might or might not be a bug.

So removing the .emscripten file from the emsdk directory should fix if.

[sbc100]

BTW, I'm hoping to make emsdk always work in embedded mode at some point in the future. Can I ask, do you have a reason why you would want it to explicitly not work in embedded mode?

[vadi2]

Ah, thanks, that worked.

As for needing not-embedded: Qt Creator 4.11 beta came out a few days ago and it right now only looks for ~/.emscripten by the sounds of it; see comments: https://www.qt.io/blog/qt-creator-4.11-beta-released

[sbc100]

Interesting, thank you. Presumably its doing that so that it can find the emscripten root?

[sbc100]

See #9543 for the long term plan to remove the config from $HOME.

[vadi2]

Sure. While I'm just a user, I've shared it with them: https://bugreports.qt.io/browse/QTCREATORBUG-23126