[CMake] converting everything

Eric Noulard eric.noulard at gmail.com
Fri Sep 21 08:56:25 EDT 2007


2007/9/21, Christian Buhtz <exsudat at gmx.de>:
> I ask me why there are so much make-implementations. It is to hard for
> all of us. I know that there couldn't be the one super-make...

There is it is called CMake :=) [just kidding].

> Can CMake read a foreign-makefile (e.g. MinGW-make or nmake) and
> generate its own cmake-makefile of it (what is the word for the
> cmake-makefile-format?)?

If you want to do this you'll need to implements AS MANY
"parser" AS MANY make flavor, including "project" files which are
not make-based like Visual Studio project file,  Code:Blocks, Eclipse etc...

CMake make the choice to specify its own "CMakeLists" format
from which you GENERATE the target make-like format.

I think it is a wiser choice because it should be easier to write
a "valid makefile" which may well only use a subset of the
full makefile syntax, than trying to parse it.

If you "parse" foreign makefile you should be able to give
message about syntax error which would be
such a pain to support if you want to support a variety of format.

> Or can CMake read a CodeBlocks project and generate its cmake-makefile
> so that I can generate every supported makefile-format from it?

Nope.
CMake (CVS version) is able to generate CodeBlocks project from
its OWN CMakeLists.txt.

May be you can ask CodeBlocks people to write
a CMake export feature?

As a side note since CMake is a generator it is more powerful
than a build system like makefile unless the build system can call
itself like re-entrant makefile feature (I did use that with gmake).


-- 
Erk


More information about the CMake mailing list