[issue40743] [CMake] It's 2020, where is CMake?

[TheUltimatePineapple]

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, here are few:

1. Simplifies cross-platform builds and inclusion of CPython in other projects 
as subdirectory/subproject.

2. Automatically generated builds for any CMake supported OS'es, no need to 
maintain an unique build system for each OS, only the CMake script.

3. Faster. Just the configuration process in current build system for Unix is 
super slow, making testing changes slow and painful.

--
components: Build
messages: 369724
nosy: TheUltimatePineapple
priority: normal
severity: normal
status: open
title: [CMake] It's 2020, where is CMake?
type: enhancement
versions: Python 3.10

___
Python tracker 
<https://bugs.python.org/issue40743>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue40743] [CMake] It's 2020, where is CMake?

[TheUltimatePineapple]

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 size.

It seems though the people here are so old-fashioned they don't see the point 
in CMake ¯\_(ツ)_/¯

I don't think I can keep CPython adopted in my engine if it keeps being this 
way, I'll have to look into alternate scripting languages which don't rely on 
antiquated build systems.

--

___
Python tracker 
<https://bugs.python.org/issue40743>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com