Hi Paul, On Fri, Jul 10, 2015 at 6:56 AM, Paul Eggleton <paul.eggle...@linux.intel.com> wrote: > I'm finally sending out the patches to support the output of bbwarn, > bberror etc. actually going to the console. This is the OE-Core side > of the changes to implement it (changes are also required to BitBake, > the patch for which has been sent to the bitbake-devel list).
Now when I start a devshell and run "../temp/run.do_compile" warnings etc which previously went to the devshell console now end up in file "../temp/fido.XXX". Would it be possible to fall back to the old behaviour if bitbake isn't listening at the other end of the fifo? > The following changes since commit 18cc6d2ec4dc289bb0333dddc96df5a645ea53d0: > > wic: Set default set of bitbake variables (2015-07-10 13:34:50 +0100) > > are available in the git repository at: > > git://git.openembedded.org/openembedded-core-contrib > paule/oecore-shell-logging > > http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/oecore-shell-logging > > Paul Eggleton (1): > classes/logging: make shell message functions output to the console > > meta/classes/logging.bbclass | 32 ++++++++++++-------------------- > 1 file changed, 12 insertions(+), 20 deletions(-) > > -- > 2.1.0 > > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core