Revisiting the case for CMake as a primary, cross-major-plats, build config

[jcfr (Jean Christophe Fillion Robin)]

It is great to see momentum to move forward and streamline how CPython can be built, cross-compiled and embedded.

As a the maintainer of python-cmake-buildsystem, we created the project ~ 10 years ago by consolidating prior work ^[1] from other developers with similar interest and goals.

I would be happy to answer questions and discuss implementing changes that would help facilitate the adoption of the system.

@gpshead

That python-cmake-buildsystem repository , nice that it exists. Kudos to them. It seems very old (3.6 and earlier). Have they ever reached out to the cpython project itself ever or at least recently?

Back in 2014, while attending SciPy, we put together a poster^[2]

@thewtex and I briefly brought this up with @ncoghlan. But since then did not have a chance to resume conversation.

That said, we will be happy to resume conversation.

Poster

• https://github.com/jcfr/scipy_2014_python-cmake-buildsystem_poster

cc: @henryiii

---

1. Transfer ownership to "python-cmake-buildsystem" organization · Issue #63 · python-cmake-buildsystem/python-cmake-buildsystem · GitHub ↩︎

2. GitHub - jcfr/scipy_2014_python-cmake-buildsystem_poster: SciPy 2014 Poster - Python cross-compilation and platform builds for HPC and scientific computing ↩︎