User: Password:
|
|
Subscribe / Log in / New account

Why the KDE project switched to CMake -- and how (continued)

Why the KDE project switched to CMake -- and how (continued)

Posted Jul 6, 2006 1:44 UTC (Thu) by zlynx (subscriber, #2285)
In reply to: Why the KDE project switched to CMake -- and how (continued) by emptty
Parent article: Why the KDE project switched to CMake -- and how (continued)

For a project like KDE, the amount of changes needed in the KDE code itself to port to a platform like AIX dwarfs the amount of code changes needed to make CMake run on that platform. So if it makes work easier on the common platforms, it is a better deal, and ports can still be done by porting CMake first.

As for autotools I have never seen them be that useful in porting. Sure, autotools may run on all sorts of systems but nothing out there tells you what autotools tests and variables your code needs to be checking for portability.

For example, assuming select() returns the remaining time from a timeout. If you develop on Linux and rely on that feature, then port to another Unix, autotools may have a test to detect that for you but you have to try the port and find the problem first before you even know you need it.


(Log in to post comments)


Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds