>I'm currently testing CMake (http://www.cmake.org) for possible use in
>personal projects.
>CMake manages the build process in an operating system and compiler
>independent manner.
>
>I read some complaints about autotools on this list and i wonder if there is
>some interest to replace autotools with cmake for transcode.
While it does look like an interesting alternative, I'm not
particularly excited about a GUI-based configuration system (even assuming
any required Makefiles would be generated ahead of time for distribution
packages. Looking at e.g. http://www.cmake.org/HTML/RunningCMake.html:
Using CMake to build a project in non-interactive mode is a simple
process if the project does not have many options. For larger projects
like VTK, using ccmake, cmake -i, or CMakeSetup is recommended. This
is because as you change options in the CMakeCache.txt file, cmake may
add new entries to that file. It can be difficult to know when to stop
the run cmake, edit the cache file cycle without the aid of an
interface.
From reading this, it seems to me that cmake is primarily intended for
use via GUI, and command-line use is considered deprecated. In any case, I
would be nervous about using a tool that rewrites user-edited files like
this; as complex as the autotools suite is, it does follow the standard
input-file-to-output-file process, so it's easy to track the effects of
changes.
--Andrew Church
[EMAIL PROTECTED]
http://achurch.org/
