All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 18 Jul 2012 14:15:14 +0100	[thread overview]
Message-ID: <1342617314.30680.29.camel@ted> (raw)
In-Reply-To: <500629E5.5000202@windriver.com>

On Wed, 2012-07-18 at 11:13 +0800, Kang Kai wrote:
> On 2012年07月17日 17:52, Richard Purdie wrote:
> > 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):
> 
> Hi Richard,
> 
> Thanks.
> 
> > Why do we have a hardcoded list here and why do new image types cause
> > builds to fail?
> After build the image, Hob trys to get list of created images. It needs 
> a map from image type to real image file's extend name, such as "live" 
> --> "hddimg" and "iso".
> then search the image output dir to get the list.
> >
> > 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...
> 
> For the current, only image type 'live' need this map. So I can remove 
> the list and check the image type is whether 'live' or not.
> But for the future, if a new image type added and need this kind of map, 
> new check for the single type is needed. I think for this scenario the 
> list is better.

Well, I *hate* the concept that if you add a new image type, the UI has
to be changed.

Ideally, we need to add something to the metadata that explains this
mapping to the UI. I want to see the hardcoded list removed from the UI,
one way or another.

Cheers,

Richard




  reply	other threads:[~2012-07-18 13:26 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
2012-07-18  3:13     ` Kang Kai
2012-07-18 13:15       ` Richard Purdie [this message]
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=1342617314.30680.29.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Kai.Kang@windriver.com \
    --cc=Zhenfeng.Zhao@windriver.com \
    --cc=bitbake-devel@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.