From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] base.bbclass: Use bb.plain to print the build header
Date: Thu, 24 Nov 2011 08:03:56 -0800 [thread overview]
Message-ID: <4ECE6AEC.8060108@linux.intel.com> (raw)
In-Reply-To: <1322146645.10818.0.camel@ted>
On 11/24/2011 06:57 AM, Richard Purdie wrote:
> If we just use print, the bitbake logging functions don't see the message
> and it can get lost if bitbake is for example logging messages to disk.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Acked-by: Darren Hart <dvhart@linux.intel.com>
> ---
> diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> index ba1f230..72196d6 100644
> --- a/meta/classes/base.bbclass
> +++ b/meta/classes/base.bbclass
> @@ -232,7 +232,7 @@ python base_eventhandler() {
>
> statuslines += layers_branch_rev
> statusmsg = "\nOE Build Configuration:\n%s\n" % '\n'.join(statuslines)
> - print statusmsg
> + bb.plain(statusmsg)
>
> needed_vars = [ "TARGET_ARCH", "TARGET_OS" ]
> pesteruser = []
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
prev parent reply other threads:[~2011-11-24 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 14:57 [PATCH] base.bbclass: Use bb.plain to print the build header Richard Purdie
2011-11-24 16:03 ` Darren Hart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ECE6AEC.8060108@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.