From: jfabernathy <jfabernathy@gmail.com>
To: yocto@yoctoproject.org
Subject: understanding recipes
Date: Thu, 26 Jan 2012 11:44:18 -0500 [thread overview]
Message-ID: <4F2182E2.2030101@gmail.com> (raw)
I'm trying to understand the concept of creating a recipe and having it
included in the build I do.
For example, suppose I want to create the meta-intel/meta-cedartrail BSP
with the core-image-minimal image, but I wanted to include hello world
as shown in 3.1.2 Autotooled Package section of the Poky reference Manual.
Where do I put the recipe file? I'm guessing a recipe-jfa directory at
the same level as the meta-cedartrail recipe-core, recipe-kernel,
recipe-graphic, recipe-bsp?
I'm also assuming that helloworld.bb file would contain:
DESCRIPTION = "GNU Helloworld application"
SECTION = "examples"
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
PR = "r0"
SRC_URI = "${GNU_MIRROR}/hello/hello-${PV}.tar.gz"
inherit autotools gettext
So where do the values of ${GNU_MIRROR|, and ${PV} get set correctly?
And what does the following line do or require me to do:
LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
Is this all that is needed to get helloworld put into /usr/bin so it can
be executed at the command line when the image is booted?
Jim A
next reply other threads:[~2012-01-26 16:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 16:44 jfabernathy [this message]
2012-01-26 16:48 ` understanding recipes Jack Mitchell
2012-01-26 18:55 ` Scott Garman
2012-01-26 21:29 ` jfabernathy
2012-01-26 21:32 ` jfabernathy
2012-01-26 21:38 ` Scott Garman
2012-01-26 21:42 ` jfabernathy
2012-01-26 22:04 ` jfabernathy
2012-01-26 22:11 ` Scott Garman
2012-01-26 22:36 ` jfabernathy
2012-01-26 22:37 ` Gary Thomas
2012-01-26 23:44 ` jfabernathy
2012-01-26 23:52 ` Gary Thomas
2012-01-27 1:12 ` jfabernathy
2012-01-27 1:20 ` Saul Wold
2012-01-27 3:14 ` Scott Garman
2012-01-27 18:43 ` Joshua Lock
2012-01-28 1:42 ` McClintock Matthew-B29882
2012-01-28 10:13 ` Gary Thomas
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=4F2182E2.2030101@gmail.com \
--to=jfabernathy@gmail.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.