On Saturday 18 March 2006 09:26, Stephan Kulow wrote: > No, that's not the goal. The goal is to have a collecting message at the > end of the configure run > > Greetings, Stephan
i.e. the way we have it now, each application has its own configure.in.in, which gets recursively combined into one configure script for the entire module. To avoid the problem that we want to inform the user about some event, but can't because the next application's configure script is scrolling information on the screen, we have configure.in.bot, which goes after all of the configure.in.in's in the module configure script. That way we can put any information that the user needs to read all in one section right at the end, where it is easy to scroll up to catch anything they've missed. Regards, - Michael Pyne
pgpRHTOtIsb0U.pgp
Description: PGP signature
_______________________________________________ Kde-buildsystem mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-buildsystem
