Wed, 19 Oct 2011
Dear Lazyweb,
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?
Posted by Jordi Gutiérrez Hermoso at Thu Oct 20 07:11:06 2011
Posted by Debian User at Fri Oct 21 12:22:17 2011
Posted by rjc at Fri Oct 21 13:04:39 2011
I'm working from the git repository for this, as listed in the project website.
It turns out I was over-zealous in blocking External downloads (it downloads "External third-party packages", patches and builds them (including python, R, tcl-tk, GL, Qt, pkg-config, sci-py, matlplotlib ...). But it includes itself as an "external package".
So, with a bit of work to download into the orig tarball the full CDAT source, and another supplementary tarball for the sample data to downloads separately, I now have a build that works.
The 16-month delay was because I was packaging all the external packages into Debian (and applying patches as necessary). The software
is now at "6.0.beta" upstream.
Thanks for volunteering, sorry about that.
A.
Posted by amckinstry at Wed Oct 26 19:18:59 2011
like you post: to my @iiofkifu twitter
Posted by IndinueCrence at Fri Nov 4 17:52:24 2011