From: Joshua Lock <josh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: Re: [OE-core] Feedback on HOB (new image creator GUI)
Date: Fri, 30 Sep 2011 17:38:12 -0700 [thread overview]
Message-ID: <1317429497.11645.33.camel@scimitar> (raw)
In-Reply-To: <33AB447FBD802F4E932063B962385B3512DAF448FC@shsmsx501.ccr.corp.intel.com>
On Sat, 2011-10-01 at 08:30 +0800, Yu, Ke wrote:
> > -----Original Message-----
> > From: Koen Kooi [mailto:koen@dominion.thruhere.net]
> > Sent: Saturday, October 01, 2011 12:33 AM
> > To: Patches and discussions about the oe-core layer
> > Cc: Yu, Ke; bitbake-devel@lists.openembedded.org; openembedded-core
> > Subject: Re: [OE-core] Feedback on HOB (new image creator GUI)
> >
> >
> >
> > Op 30 sep. 2011 om 10:49 heeft Joshua Lock <josh@linux.intel.com> het
> > volgende geschreven:
> >
> > > On Fri, 2011-09-30 at 08:36 -0600, Yu, Ke wrote:
> > >> Hi,
> > >>
> > >> As you may already know, a new GUI has been added to bitbake
> > >> recently, i.e. HOB (Human Oriented Builder).
> > >
> > > It's not an acronym, it's just a name - Hob.
> > >
> > >> It is a graphical image creator that allows user to freely choose
> > >> which packages to be built in the image.
> > >> The wiki https://wiki.yoctoproject.org/wiki/BitBake/GUI/Hob has more
> > >> detail.
> > >
> > > I'll be changing this page and adding more user-centric info in the
> > > coming weeks.
> > >
> > >> This email is to collect your feedback on the HOB. Current HOB is our
> > >> first version, and it surely has many place to improve. We has the
> > >> plan to enhance it in Yocto 1.2. So we really hope that you can use
> > >> it and provide your valuable feedback . We do think user's
> > >> feedback/requirement is the right way to go. Looking forward your valuable
> > input.
> > >>
> > >> Best Regards
> > >> Ke
> > >>
> > >> Ps. The simple way to run hob is:
> > >> # touch conf/hob-pre.conf conf/hob-post.conf # bitbake -u hob -r
> > >> conf/hob-pre.conf -R conf/hob-post.conf
> > >
> > > In oe-core (and therefore Poky) we have a wrapper script so from an
> > > oe-init-build-env'd build directory you can just call hob.
> > >
> > > The script will create the required configuration files with some
> > > required values.
> >
> > Can we have it use local.conf by default please? I hate having to put the same
> > info in multiple places
>
> Yes, this is valid. We should be able to use local.conf as pre and post
> conf file, if they are not specified by user. Thanks for the input. I
> will add it to my plan.
I'm not sure we should promise that - the plan, per bug #1441 (and as
alluded to earlier) is to have the configuration be independent of
BitBake and persistent to the UI (i.e. hob configuration is the same
even if I launch it from a clean build dir).
This isn't a mandate but we should certainly weigh up the pro's and
con's of either side before we propose which one to implement.
http://bugzilla.pokylinux.org/show_bug.cgi?id=1441
Cheers,
Joshua
--
Joshua Lock
Yocto Project "Johannes factotum"
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-10-01 0:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 14:36 Feedback on HOB (new image creator GUI) Yu Ke
2011-09-30 15:16 ` Joshua Lock
2011-09-30 15:36 ` Joshua Lock
2011-09-30 15:49 ` Joshua Lock
2011-09-30 16:32 ` [OE-core] " Koen Kooi
2011-09-30 17:16 ` Joshua Lock
2011-09-30 18:43 ` Koen Kooi
2011-10-01 0:30 ` Yu, Ke
2011-10-01 0:38 ` Joshua Lock [this message]
2011-09-30 16:20 ` McClintock Matthew-B29882
2011-09-30 17:23 ` Joshua Lock
2011-09-30 17:32 ` McClintock Matthew-B29882
2011-09-30 17:34 ` Joshua Lock
2011-09-30 21:55 ` [OE-core] " Gary Thomas
2011-10-01 0:23 ` Yu, Ke
2011-10-01 17:46 ` Otavio Salvador
2011-10-01 17:51 ` Koen Kooi
2011-10-03 22:13 ` Joshua Lock
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=1317429497.11645.33.camel@scimitar \
--to=josh@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox