[Python-Dev] Evaluated cmake as an autoconf replacement

[Alexander Neundorf]

On Mon, Mar 30, 2009 at 8:49 PM, Christian Heimes <lists at cheimes.de> wrote:
> David Cournapeau wrote:
>> On Tue, Mar 31, 2009 at 3:16 AM, Alexander Neundorf
>> <alex.neundorf at kitware.com> wrote:
>>> Can you please explain ? What is "those" ?
>>
>> Everything in Lib. On windows, I believe this is done through project
>> files, but on linux at least, and I guess on most other OS, those are
>> handled by distutils. I guess the lack of autoconf on windows is one
>> reason for this difference ?
>
> All modules under Modules/ and PC/ are build inside the VS project. Some
> dependencies like gzip, bzip2, openssl etc. are build inside the
> project, too. Other dependencies are using shell scripts and nmake.

AFAIK we also have cmake-based builds for gzip, bzip2 and other
dependencies KDE needs somewhere.

> On Unix the builtin modules are compiled with a custom build system
> (Modules/Setup.* and friends). The shared libraries are build by a
> distutils script (setup.py) in the root folder of the Python distribution.

With CMake I was also building the Modules directly with CMake, i.e.
not using distutils, so these were already taken care of.

In Lib/ there are only python files, and they should be compiled to
pyc files, right ? I didn't do this back then.
We are right now getting better support for this in KDE, which would
probably help here:
http://lists.kde.org/?l=kde-buildsystem&m=123795136609498&w=2

Alex