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

[erlendaasland (Erlend E. Aasland)]

@jcfr

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.

Thanks, that’s good to know

Based on earlier discussions, we are deliberately doing this in very small steps. The first step is to try and get a picture of what a “perfect” CPython build system would look like:

What do you want to see in tomorrow’s CPython build system?

Hypothetically, if we had to recreate the build process from just the available code today, which qualities and features would we want to see in tomorrow’s new build system? Let’s do an informal brainstorm: post your wishes about what a perfect (or very good) CPython build system should look like. Post one item per message, if someone has already posted something you want, “vote” for it using the “heart” mechanism.

We could of course have started with the slightly related question “what’s the problem with the current build system?”^[1].

---

1. We’ll get to that later ↩︎