Yeah, if you're comfortable using the Unix command line, using non-interactive CMake this way is almost always an easier path to joy than using the GUI or Curses interactive application.
It's why the Slicer people spent considerable time putting together a suite of TCL scripts to do their builds, rather than ask users to configure and build many different packages. I've taken the Slicer scripts and tailored them to the BRAINS suite of applications, and have spent some time fine tuning them to the point where on supported platforms, there's no configuration necessary at all for a full development build, and there's some support for generating installable packages as well. On Tue, Mar 3, 2009 at 10:19 AM, Jed Brown <j...@59a2.org> wrote: > On Tue 2009-03-03 09:20, kent williams wrote: >> Lather, Rinse, Repeat. After 2 or 3 go-arounds, CCMake is happy and >> lets you generate your build files. > > This and the fact that most modules aren't written to handle multiple > passes (for instance, if the wrong version is found on the first pass, > the cache becomes corrupt) means that I frequently configure cmake > packages by repeatedly running > > $ rm -rf * && cmake .. -DVAR1=foo -DVAR2=bar > > and adding options based on the output. _______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
