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/9a102f90-d5cb-4125-a329-0fd5d34745a1%40googlegroups.com.
