All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Barros Pena, Belen" <belen.barros.pena@intel.com>
To: Allen Curtis <allen.curtis@curtisembedded.com>,
	yocto <yocto@yoctoproject.org>
Subject: Re: packagegroup not appearing in HOB
Date: Mon, 12 Oct 2015 14:01:09 +0000	[thread overview]
Message-ID: <D24179D4.677F2%belen.barros.pena@intel.com> (raw)
In-Reply-To: <591A7BB6-5C46-4D67-B8BC-9F6E57442A40@curtisembedded.com>



On 07/10/2015 18:36, "yocto-bounces@yoctoproject.org on behalf of Allen
Curtis" <yocto-bounces@yoctoproject.org on behalf of
allen.curtis@curtisembedded.com> wrote:

>Hello,
>
>I created a packagegroup file as per the instructions called
>packagegroup-foo.bb
>
>Within that file I define 2 package groups as such.
>
>PACKAGES = "\
> packagegroup-foo-apps \
> packagegroup-foo-tools \
>"
>
>RDEPENDS_packagegroup-foo-apps = "Š"
>
>RDEPENDS_packagegroup-foo-tools = "Š"
>
>However, when I run HOB and inspect the list of packages it shows
>packagegroup-foo but it does not list packagegroup-foo-apps or
>packagegroup-foo-tools.
>
>Is this correct?
>
>How do I verify the groups are created correctly so I can complete
>implementation using the new group definitions?

Hi Allen,

Hob development has been on hold for quite a while, so I am not sure how
reliable the list of packages currently is.

If you would like to know if your package group is set up correctly, and
you want to do it with a graphical tool, you can use Toaster, which is the
replacement for Hob. There is a manual here

www.yoctoproject.org/docs/1.8/toaster-manual/toaster-manual.html

And a quick video tutorial here

https://www.youtube.com/watch?v=f3gDg75FwFo

Assuming you are building with 1.8 fido, you can set up Toaster
dependencies as explained here

http://www.yoctoproject.org/docs/1.8/toaster-manual/toaster-manual.html#toa
ster-manual-start

And then run Toaster locally as explained here

http://www.yoctoproject.org/docs/1.8/toaster-manual/toaster-manual.html#set
ting-up-locally-and-running-in-build-mode

You would then need to import your custom layer (the one providing your
package group) and build packagegroup-foo

Once the build finishes, you can select it, view the list of packages
built, search for packagegroup-foo, and look at its dependencies. If the
package group is working as intended, the dependencies should list
packagegroup-foo-apps and packagegroup-foo-tools, and in turn the
dependencies for each of those should list the RDEPENDS you specified.

I know this all sounds quite convoluted, but it's actually not too bad :)
This is how the RDEPENDS for a package group look like in Toaster

http://imgur.com/E7OCp08


If you have any questions, let me know.

Cheers

Belén


>
>TIA
>
>-- 
>_______________________________________________
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto



      reply	other threads:[~2015-10-12 14:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-07 17:36 packagegroup not appearing in HOB Allen Curtis
2015-10-12 14:01 ` Barros Pena, Belen [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=D24179D4.677F2%belen.barros.pena@intel.com \
    --to=belen.barros.pena@intel.com \
    --cc=allen.curtis@curtisembedded.com \
    --cc=yocto@yoctoproject.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.