Beuc <b...@beuc.net> added the comment:
I've been maintaining a Python Emscripten build for the Ren'Py (game engine) web port: https://github.com/python-emscripten/python https://renpy.beuc.net/ I recently tackled Python3 with a minimal/embeddable approach and checking the other ports already pointed in the discussion: https://github.com/python-emscripten/python/tree/trunk/3.8/ (2 patches, and a short pyconfig.h fix-up) There is also a Cython module to use the Emscripten C API. Here's a demo at: https://www.beuc.net/python-emscripten/demo/3/ (hello-world size: 3MB, with a few common modules: 4MB) I can provide a pull request with a first few core changes. Should this be done on github? - cross-compilation handling appears to follow an incorrect logic, in particular by querying 'dpkg' or parsing compiler output to detect include paths -- it is the (cross-)compiler's responsibility to provide the system paths, and detecting them manually causes conflicts. I had to patch setup.py. Let me know if I missed something. Usually cross-compiling is triggered by non-matching build-type/host-type. Here cross-compilation logic is apparently triggered when exporting _PYTHON_HOST_PLATFORM=xxx manually (it's in the Makefile but not exported, and breaks normal build when exported). Is this the way it's meant to be used? ---------- nosy: +Beuc _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40280> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
