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

[Alastair McKinstry]

I'm building a debian package, CDAT <http://bugs.debian.org/584637>. 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?

-- 
Alastair McKinstry  ,<alastair at sceal.ie>  ,<mckinstry at debian.org>     http://blog.sceal.ie

Anyone who believes exponential growth can go on forever in a finite world
is either a madman or an economist - Kenneth Boulter, Economist.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.cmake.org/pipermail/cmake/attachments/20111020/af24a29c/attachment.htm>