On Tuesday 17 June 2008 15:46:36 Enrico Weigelt wrote: > * Alexander Neundorf <neundorf@xxxxxxxxxxxxx> schrieb: > > On Monday 16 June 2008 17:15:37 Enrico Weigelt wrote: > > > * Alexander Neundorf <neundorf@xxxxxxxxxxxxx> schrieb: > > > > 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 > > > > > > Are these variables strictly specified or is all left to individual > > > author's decision ? > > > > Authors decision. > > Then you've got the same problem as w/ autoconf's config.status: > You have to tweak it for each individual package separately :( Well, these are all more or less scripting languages, so people can create whichever variables they like, no way to enforce something. Still one can suggest standards which should be followed. 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
