From: Darren Hart <dvhart@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bitbake.conf: Change build output message to list BUILD_SYS, TARGET_SYS and NATIVELSBSTRING
Date: Mon, 26 Nov 2012 10:42:12 -0800 [thread overview]
Message-ID: <50B3B804.70003@linux.intel.com> (raw)
In-Reply-To: <1353941677.21863.59.camel@ted>
On 11/26/2012 06:54 AM, Richard Purdie wrote:
> The build summary is meant to reflect key configuration variables. Information
> about the build system we're running on is important but currently missing
> from the information displayed.
>
> Printing TARGET_SYS removes the need to print TARGET_OS and TARGET_ARCH
> and we add BUILD_SYS and NATIVELSBSTRING to show information about the
> build system.
>
> [YOCTO #3456]
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Tested-by: Darren Hart <dvhart@linux.intel.com>
Fedora 17 amd64 host:
Build Configuration:
BB_VERSION = "1.17.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Fedora-17"
TARGET_SYS = "i586-poky-linux"
MACHINE = "qemux86"
DISTRO = "poky"
DISTRO_VERSION = "1.3+snapshot-20121126"
TUNE_FEATURES = "m32 i586"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp
meta-yocto
meta-yocto-bsp
meta = "master:7eb5d130ad451c105f4349bd94164cff58e88040"
Looks good to me.
Thanks,
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel
prev parent reply other threads:[~2012-11-26 18:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 14:54 [PATCH] bitbake.conf: Change build output message to list BUILD_SYS, TARGET_SYS and NATIVELSBSTRING Richard Purdie
2012-11-26 18:42 ` 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=50B3B804.70003@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox