On Saturday 14 June 2008 01:19:32 you wrote: ... > I still don't understand why all the scons, cmakes and jams out there > don't even try to provide the *standard* user interface everyone is used > to on a unix system. For cmake: CMake has a cache, where the values of variables are stored, e.g. if an option is enabled or not, or where a library has been found (e.g. JPEG_LIBRARY=/usr/local/lib/libjpeg.so). The way to influence the behaviour of cmake is to change the value of these variables, this can be done either via a GUI (curses based or with cmake 2.6 also a graphical one), or via the command line: $ cmake -D<name_of_variable>=<new_value> ...more options There is no simple automatic mapping from the variables to enabling features. Anyway, it is on the TODO for cmake to add some kind of support for project-configurable command line options, so that configure-compatible options could be provided. > > Lots of packages need special tools or other software installed to > > build them; this is no different. > > autotools need only a shell and make Yes, and requiring a shell is a lot, in the case you want to port also to Windows. Alex -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
