From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Kang Kai <kai.kang@windriver.com>
Cc: bitbake-devel@lists.openembedded.org, Zhenfeng.Zhao@windriver.com
Subject: Re: [PATCH 1/1] hob2: add elf to hcc supported image types
Date: Tue, 17 Jul 2012 10:52:57 +0100 [thread overview]
Message-ID: <1342518777.10484.2.camel@ted> (raw)
In-Reply-To: <97edd3e3b004e658241e3b3fc759837686deff74.1342495796.git.kai.kang@windriver.com>
On Tue, 2012-07-17 at 14:58 +0800, Kang Kai wrote:
> [Yocto #2709]
>
> OE Core Commit c9b01af84b64edba056f959c349895e0698324e6 add elf image
> type. This will cause hob build image failed.
> Add elf to hcc supoorted image types to fix this issue.
>
> Signed-off-by: Kang Kai <kai.kang@windriver.com>
> ---
> bitbake/lib/bb/ui/crumbs/hobwidget.py | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/bitbake/lib/bb/ui/crumbs/hobwidget.py b/bitbake/lib/bb/ui/crumbs/hobwidget.py
> index dba278c..d10c56b 100644
> --- a/bitbake/lib/bb/ui/crumbs/hobwidget.py
> +++ b/bitbake/lib/bb/ui/crumbs/hobwidget.py
> @@ -89,6 +89,7 @@ class hcc:
> "cpio.xz" : ["cpio.xz"],
> "vmdk" : ["vmdk"],
> "cpio.lzma" : ["cpio.lzma"],
> + "elf" : ["elf"],
> }
>
> class HobViewTable (gtk.VBox):
Why do we have a hardcoded list here and why do new image types cause
builds to fail?
We need to rewrite this code so this does not happen and the user at
least gets a sensible error message. Hardcoded lists are bad...
I've merged the patch but I'd like to see a bug opened about this.
Cheers,
Richard
next prev parent reply other threads:[~2012-07-17 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 6:58 [PATCH 0/1] hob2: add elf to image types Kang Kai
2012-07-17 6:58 ` [PATCH 1/1] hob2: add elf to hcc supported " Kang Kai
2012-07-17 9:52 ` Richard Purdie [this message]
2012-07-18 3:13 ` Kang Kai
2012-07-18 13:15 ` Richard Purdie
2012-07-19 3:16 ` Kang Kai
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=1342518777.10484.2.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Zhenfeng.Zhao@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=kai.kang@windriver.com \
/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.