Ned Deily added the comment:
Thanks for your suggestion but changing build systems is a *huge* undertaking
for cPython thanks to the many different platforms that we have added support
to over the years and the many, many customizations that have been made. cmake
would certainly be one opti
TheUltimatePineapple added the comment:
For me CPython has caused a lot of pain without having CMake.
I have to manually compile CPython on each OS I want to support, having to fix
the quirks on each build system and I have keep the built linkable blobs in my
project which increases the repo
Chris Jerdonek added the comment:
This was discussed a bit last December 2019 here ("Is there prior discussion
around the build system of CPython itself?"):
https://discuss.python.org/t/is-there-prior-discussion-around-the-build-system-of-cpython-itself/2813
--
nosy: +chris.jerdonek
Christian Heimes added the comment:
How about you start with a PEP that compares our current build system with
CMake and explores if CMake is a viable option? Is CMake supported on platforms
like Solaris, HP-UX, VxWorks? Or are there better options for a new build
system for CPython, for exa
Rémi Lapeyre added the comment:
Can you point to specific issues with the current build system?
It seems to me that for 1. it will only make it easier for projects that use
CMake, 2. the build system is not the only part needed to support a new OS and
for 3. I've not found Python to be partic
pmp-p added the comment:
Hi, I'm always curious about others experiences : why would you need
cross-platform building for any of the officially supported platforms ?
Also on some random unsupported platforms that require cross-compilation like
maybe android, wasm or other uncommon posix, cma
New submission from TheUltimatePineapple :
The current CPython build system is antiquated and makes cross-platform builds
difficult (in my experience). There have been unofficial CMake implementations
but they are either outdated, abandoned or just unusable.
Adopting CMake has many benefits,
