On 6/3/11 1:10 AM, Darren Hart wrote: > > > On 05/31/2011 03:26 PM, Scott Garman wrote:
... > o In general I find the default UI to be exceedingly noisy. It feels > very much like what I would write for something I was actively > developing - ie, something I expect to break a lot! I don't think > that's the sort of impression we want users to have while building a > release (for example). I have heard similar comments from others as well. > I'd prefer if what we currently get today was the output of -D. The > current output could instead be something a lot more in the vein of > what we see with recipe parsing. Perhaps one line per > BB_NUMBER_TREADS (N), maybe something like: > > Task 2300/4600 [#################### ] > 0: linux-yocto: do_compile > 1: matchbox: do_fetch > ... > N: dbus: do_configure > > It would of course update the current lines and not scroll. Most of > the time, this would be plenty information. Upon failure we stop > updating the "UI" and print something like: Even if it did scroll, somehow limiting the messages being printed would be beneficial. It's been suggested to me simply one (or two) messages per step MAX. Running linux-yocto do_compile Running matchbox do_fetch ... I believe currently we have around 3-5 messages per step, and it's still too noisy -- unless you need to debug something. > ERROR: An unhandled exception occured while processing > linux-yocto: do_fetch > > Exception: No such file or directory. > > Run with -D for a more detailed error report or consult the > appropriate log file: > > $(pwd)/tmp/work/$machine/linux-yocto-$HASH-$HASH \ > /temp/log.do_fetch.$PID > > Or something along those lines. > > Thanks for collecting these Scott, great idea! > _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
