cdrkit without cmake

Posted May 24, 2009 4:59 UTC (Sun) by solardiz (guest, #35993)
In reply to: cdrkit: Debian's fork of cdrtools by aleXXX
Parent article: cdrkit: Debian's fork of cdrtools

We wanted to introduce cdrkit into Openwall GNU/*/Linux (Owl), a small distro for servers, and we finally did, but we found the build-time dependency on cmake very unfortunate. So we got rid of that dependency in our package, but this cost us time. For more info, see my posting to the Distributions list and our cdrkit package files, including README-cmakeless.

We find cdrkit's use of cmake unreasonable. cdrkit is relatively small (e.g., compared to cmake!) and it does not require "portability" to native development environments on non-Unix platforms (where the use of cmake could be an advantage). cdrkit is simply bloated by its use of cmake. :-(

cdrkit without cmake

Posted May 29, 2009 20:16 UTC (Fri) by aleXXX (subscriber, #2742) [Link] (1 responses)

You can consider cmake a tool like make and the compiler, i.e. something
which should already be existing on the system.
On most systems this is now already the case.

On basically all desktop distros this is the case now, and more and more
other programs are converting to cmake. So maybe cdrkit is the first
program you are encountering now which uses cmake for your distro, but
there will be more in the future.

If you want to avoid the build time, you can also use the binary cmake
release which you can download here:
http://www.cmake.org/cmake/resources/software.html
It works on all Linux distributions (at least we don't know of any where
it doesn't).
This still adds size, but you can save the build time for cmake.

Alex

cdrkit without cmake

Posted Jun 2, 2009 12:58 UTC (Tue) by nix (subscriber, #2304) [Link]

The build time for cmake is about five minutes :)

I suspect what's annoying people is that the syntax for cmake is quite
different from configure scripts, and it takes a good bit of manual
reading to figure out how to get a list of per-package compilation options
et al (cmake --help doesn't work for that as far as I can tell: you can
get lists of *all* properties or commands, but not only of those added byt
the thing you're trying to build. I have to resort to reading the
cmakefiles, which is not ideal!)