About
wind&oil, Weblog
Syndicate:
Subscribe to a syndicated feed of my weblog,
brought to you by the wonders of RSS.
Projects:
www.behrmann.name
www.oyranos.org
ColourWiki
CinePaint
Others Bogs:
Color hacks
mulebakken.net
Linux Photography
home :: docs :: cmake_2007.12.13.html
CMake hassle
CMake is wrong in claiming it generates unix makefiles. It generates lots of
dependend files, which must be read to understand the whole process. Nothing
selfcontained. All is spread over many files and various dependencies. Cmake
feels much like a PHP hack. If CMake could render it true to generate native
build files, I mean selfcontained unix Makefiles and projects files for other
build environments, CMake would be a great tool and probably help reducing
complexity. Currently it is more close to autotools laboriousness.
Changing the paradigm from
automated configure scripts to a full interactive only configuration process
moves the new build environment clearly to Windows. In the same way CMake looses
a clear Unix feeling.
To make it clear, I dont like to use libtool with its timeconsuming complexity.
But what makes Cmake substancially better? As I often try to compile many
different projects, my benchmark is, how quickly can I overcome a unexpected
problem during the build process?
The following questions arise quickly [with CMake answeres]:
Do I need to learn a new syntax? [yes]
Are all tools and dependencies in one place, making needed adaptions easy and straight forward? [no]
Does I get a project relevant help message by default to change options or set variables? [no]
Can I easily trace wrong parameters to its source, without the need to go
through various files and possible learn theire syntax? [no]
Can I use the tool in existing automated envioronments? [not obvious]
If you search for a elegant and simple buildenvironment, chances are high
you dont find it with a current version of this tool.
/docs | 1 comment | permanent link |