From: Scott Garman <scott.a.garman@intel.com>
To: yocto@yoctoproject.org
Subject: Re: understanding recipes
Date: Thu, 26 Jan 2012 10:55:48 -0800 [thread overview]
Message-ID: <4F21A1B4.60305@intel.com> (raw)
In-Reply-To: <4F2182E2.2030101@gmail.com>
On 01/26/2012 08:44 AM, jfabernathy wrote:
> 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?
Hi Jim,
The best way to do this is to create your own layer, and keep all of
your customizations there.
You'd put this in a directory, say meta-jfa with something like the
following:
meta-jfa/
meta-jfa/conf/layer.conf
meta-jfa/recipes-jfa/helloworld/helloworld.bb
where your layer.conf file would look like:
# We have a conf and classes directory, add to BBPATH
BBPATH := "${BBPATH}:${LAYERDIR}"
# We have a packages directory, add to BBFILES
BBFILES := "${BBFILES} ${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
BBFILE_COLLECTIONS += "jfa"
BBFILE_PATTERN_jfa := "^${LAYERDIR}/"
BBFILE_PRIORITY_jfa = "5"
Then point your build's bblayers.conf file to include the path to your
meta-jfa/ directory.
>
> 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?
Those examples are defined in the bitbake classes you have in your base
layers.
> And what does the following line do or require me to do:
>
> LIC_FILES_CHKSUM = "file://COPYING;md5=751419260aa954499f7abaabaa882bbe"
This was answered in another post.
> 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?
You'd also need to add the helloworld package to your image file. The
simplest way to do this is to add EXTRA_IMAGE_FEATURES += "helloworld"
in your build's local.conf file.
I think the above should be accurate enough w/o testing it myself.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-01-26 18:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 16:44 understanding recipes jfabernathy
2012-01-26 16:48 ` Jack Mitchell
2012-01-26 18:55 ` Scott Garman [this message]
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=4F21A1B4.60305@intel.com \
--to=scott.a.garman@intel.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.