From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: Creating a new recipe based on another recipe
Date: Mon, 28 Sep 2015 09:46:09 -0600 [thread overview]
Message-ID: <560960C1.2070806@mlbassoc.com> (raw)
In-Reply-To: <2DCC166D4F5C8443941662E1E67FD5C17871C6C5@LEICESTER.internal.datapath.co.uk>
On 2015-09-28 09:30, Stuart Weaver wrote:
> Hi all,
>
> I have a recipe for a package which builds well. I now need to add a patch into certain builds. What is the best way to do this?
>
> 1.Is there a variable I can append the image name to (similar to:/SRC_URI_image-name/)?//
>
> 2.Is there a way of creating a new ‘recipe 2’ that obtains the details from ‘recipe 1’ and applies a patch? This way I can then simply add the new recipe into any builds I want and
> includes any future changes I make to ‘recipe 1’. This solution also means not having to continuously reconfigure/recompile the original recipe!
>
> 3.Do I have to do it the hard way and copy the whole .bb file into a new one and make sure everything is in sync when future updates are applied?
If it's just a patch, the simplest way is to use something like this:
SRC_URI_append_XYZ = "file://XYZ.patch"
where XYZ is something which can identify the override. One example
might be where XYZ is the name of a target board (${MACHINE})
There are many examples of this usage in the Poky/Yocto tree(s)
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2015-09-28 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 15:30 Creating a new recipe based on another recipe Stuart Weaver
2015-09-28 15:46 ` Gary Thomas [this message]
2015-09-28 17:59 ` Daniel.
2015-09-28 18:22 ` 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=560960C1.2070806@mlbassoc.com \
--to=gary@mlbassoc.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.