[CMake] "Empty" ./CMakeFiles/Makefile2 - how to proceed?

[Eric Noulard]

2011/10/20 Alastair McKinstry <mckinstry at debian.org>:
>
> I'm building a debian package, CDAT. The latest version 6.0.alpha uses CMAKE
> to build, rather than configure. The trouble is that CMake doesn't build. It
> doesn't even fail.
>
> $ mkdir build
> $ cd build
> $ cmake ..
> ()-- Configuring done
> -- Generating done
> -- Build files have been written to: /home/amckinstry/deb-packages
> /cdat/cdat-6.0.alpha/build
> $ make
> $
>
> The problem is, 'make' does nothing. A Makefile is generated by CMake, which
> calls cmake which calls make again on ./CMakeFiles/Makefile2 ... which does
> nothing useful. Apparently the CMake is supposed to put useful stuff in
> there, but doesn't. What puts stuff into Makefile2, and where should I pick
> up the bugs trail?

CMake is not a "build" tool like make is, it is a build tool **generator**.
Thus, CMake generates the Makefile files (including ./CMakeFiles/Makefile2)
during the

$ cmake ..

step.

The inputs of CMake are files named CMakeLists.txt, those files are
the "equivalent"
of Makefile files for make with a more declarative syntax.

However if this CDAT package does not build correctly out-of-the-box
you'd better
ask to the package provider first. They must but the authors of their
CMake usage.
If they have trouble with CMake, then they can ask question here.

-- 
Erk
Membre de l'April - « promouvoir et défendre le logiciel libre » -
http://www.april.org