(oops! sorry for going off-list)
On 12/09/14 05:50, Paul Eggleton wrote: > On Monday 08 December 2014 22:30:31 Trevor Woerner wrote: >> This is really awesome stuff. I'm still playing around with it. >> >> My current HEAD is: >> >> commit 6ea5f5368a88317ace198f44a47cf043bc9fb6e6 >> Author: Paul Eggleton <paul.eggle...@linux.intel.com> >> Date: Fri Dec 5 11:30:25 2014 +0000 >> >> devtool: use event filtering to disable events if available >> >> on your contrib/paule/devtool branch. >> >> If I do a "devtool add" without a "devtool create-workspace" it succeeds >> but I get: >> >> $ devtool add xannounce ~/devel/code/xannounce >> INFO: Creating workspace layer in >> INFO: Recipe recipes/xannounce/xannounce.bb has been automatically >> created; further editing may be required to make it fully functional >> >> and find the changes have been made in the current directory. If I do >> the "devtool create-workspace" first, I get a "workspace" directory and >> all the stuff put in there, which is nicer. >> >> If it doesn't fail due to a user running "devtool add" before "devtool >> create-workspace" then I think it would be nice if the two results were >> the same. > Ah, oops - I've found the cause and fixed it on the branch. Thanks! Awesome... *very* nice. It works great now. > >> Would it be possible to make the output of devtool be nice and colourful >> like the output of bitbake? > Good idea, this is now done on the branch as well. "devtool build" doesn't > support colour in the bitbake output, but that's because colour support in > bitbake is switched by whether the output is going to a TTY and stdout is > being redirected in this case. (I guess we could add a command line option > for > that as I have with devtool/recipetool.) > If it's not too much trouble I would like to ask that colour/curses be possible/enabled by default. Trying to find the error in all that output is a "needle in a haystack"-like operation :-) I wonder if all the NOTE: Running setscene task 31 of 33 (/home/trevor/devel/yocto/build/poky/meta-poky/meta/recipes-devtools/gcc/gcc-runtime_4.9.bb, do_populate_sysroot_setscene) NOTE: recipe gcc-runtime-4.9.1-r0: task do_populate_sysroot_setscene: Started NOTE: recipe gcc-runtime-4.9.1-r0: task do_populate_sysroot_setscene: Succeeded NOTE: Running setscene task 33 of 33 (/home/trevor/devel/yocto/build/poky/meta-poky/meta/recipes-devtools/gcc/gcc-cross_4.9.bb, do_populate_sysroot_setscene) NOTE: recipe gcc-cross-i586-4.9.1-r0: task do_populate_sysroot_setscene: Started NOTE: recipe gcc-cross-i586-4.9.1-r0: task do_populate_sysroot_setscene: Succeeded Could be (should be) done as part of the "devtool create-workspace"/"devtool add" operation? -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core