On Monday 06 Nov 2006 10:44, Chris Cannam wrote:
> [...] building continues.

Well, it built.

I have to say I'm still only half keen.

Pros:

 * CMakeList syntax looks straightforward enough.

 * Extension through modules in cmake_admin looks comprehensible.

 * Good feedback during compiling, nice progress indicator.

 * There is a generally solid feel about the cmake program.

   You get the impression it's been pretty heavily tested.  It didn't
   seem to do anything I didn't expect.

 * Easy to obtain cmake.

   This is really only a mitigating factor for the problem that it has
   to be obtained at all.

 * Appears to do the right thing for cross-Makefile dependencies.

I had mentioned "produces makefiles" as a pro; I'm not mentioning it this 
time, because it turns out the makefiles are far too complicated to be used 
or tweaked independently of CMake.

Cons:

 * Requires a tool users won't necessarily have.

 * Generates a staggering amount of supporting cruft.

   I counted a total of 96 files generated by the configure and build
   process (not counting directories or the usual object files).

 * No way to remove the supporting cruft (no "make distclean").

   The docs suggest that this doesn't matter because you should be
   building to a separate build directory.  I would accept that if the
   default was to build to a separate build directory, but it isn't.

   What's particularly odd is that most of the generated and object
   files _do_ get written to special directories (the CMakeFiles
   directories) -- just not quite all of them.

 * Some of the output is so verbose and/or weird as to be offputting.
   The stuff you get when you type "make" and there's no work to be
   done, for example, is just excessive.

I would much rather have only a single makefile (or at most two, one in the 
top-level directory and one in src/).  16 generated files is still a lot, but 
it's much better than 96, and it would cut down on the verbiage as well as 
there would be, and should be, no need to change directories.  If the 
makefile was too large and unwieldy with all the file names in it, it could 
perhaps include lists of files from the individual directories.  Or I'd 
probably rather it wildcarded the list of source files itself.


Chris

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel

Reply via email to