Passing a filename as --em-config or in EM_CONFIG will continue to work yes. Thats the plan.
By the way if you use `emsdk --embedded` these days it should just work to call emcc without `--em-config`. enscripten now knows to look for it config relative to itself (firstly its own directory and then it looks two levels up for the emsdk embedded config). Regarding parsing `~/.emscripten` in order to find emscripten, I really want to stop people from trying to do this. I'd much rather the PATH was way one finds emscripten. e.g. `which emcc`. Failing that an environment variable. But other tools assuming the location and format of the `.emscripten` config file is not a good idea IMHO. I know some tools do this already but hopefully we can teach them other ways. cheers, sam On Wed, May 20, 2020 at 12:28 PM Floh <[email protected]> wrote: > PS: I'm depending on the --em-config option (because I'm installing the > emsdk with --embedded), > but I'm passing in a regular string, not some sort of python expression). > > Are you going to remove the entire --em-config option, or just that it is > evaluated as a python string? > > I'm fine with both, as long as locally installed SDKs installed with > '--embedded' continue > to work :) > > On Wednesday, 20 May 2020 21:24:16 UTC+2, Floh wrote: >> >> Good riddance ;) >> >> That reminds me that the .emscripten file is also a python script which >> must be evaluated with a python interpreter to make any sense of the >> content >> >> For instance: >> >> import os >> emsdk_path = os.path.dirname(os.environ.get('EM_CONFIG')).replace('\\', >> '/') >> ... >> >> Are there any plans on changing that to a plain text file? Might simplify >> things >> for build tools which try to figure out where the emscripten SDK is >> actually located. >> >> I also remember that there was some obscure voodoo happening with the >> "emcc --em-config=..." option, if I remember right, the passed string was >> assigned >> to an environment variable EM_CONFIG (or even python variable?) in order >> to make followup tools work, and somehow this might also have been related >> to the .emscripten file... >> >> At least that's my hazy memory from long ago when I tried to make sense >> of >> how "embedded SDKs" work, and what's up with .emscripten being a >> python file. Any simplifications in that area are definitely welcome ;) >> >> Cheers, >> -Floh. >> >> On Tuesday, 19 May 2020 20:46:25 UTC+2, Sam Clegg wrote: >>> >>> emscripten has a feature where you can avoid using a config file >>> completely and instead pass a python literal in the EM_CONFIG >>> environment variable or `--em-config` command line. >>> >>> e.g. `emcc --em-config="<python code>` >>> >>> As part of routine cleanup I'm hoping to be able to remove this >>> feature and allow the code to depend on the existence of a config >>> file on disk. >>> >>> I'm not imagining there are any users of this feature, and we can >>> make it into warning a few releases to confirm this. >>> >>> Does anyone know of any users of this feature? >>> >>> cheers, >>> sam >>> >> -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/emscripten-discuss/e48aea72-28ad-4121-bc8c-d3414dccf1b1%40googlegroups.com > <https://groups.google.com/d/msgid/emscripten-discuss/e48aea72-28ad-4121-bc8c-d3414dccf1b1%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAL_va28_Ge605-tN8RpP7ObANvxCvekrp3yNyc0p0XMh6y19Dg%40mail.gmail.com.
