On 2015-09-29 03:38, Stuart Weaver wrote:
Many thanks for your answers Gary/Daniel,
Gary- I've tried:
SRC_URI_append_image-name2 = "file://XYZ.patch"
But no luck, when building the image it seems to skip over it with no
patching occurring. I can't use the ${MACHINE} variable as the two images will
be for the same ${MACHINE}
Sorry, I didn't see this because of the [misleading] subject :-( Next time,
either reply to the [single] message directly, or at least modify the subject
line to match the current thread.
You're command is incorrect - there is a big difference between "_"
and "-" when it comes to bitbake parsing. Try this:
SRC_URI_append_image_name2 = "file://XYZ.patch"
^
Notice this uses underscore (_) not hyphen (-)
Daniel- with a .bbappend, to my knowledge I wouldn't be able to include it to
just one image.
My "perfect" solution would be to find a variable out there that will
copy/refer to a current recipe and add the details into the new recipe with it's own ${S}
etc... Of course I could just copy one to another, but then there's the problem of
updating files later on. Therefore, unless there is another option that I haven't
considered, I might look at refactoring everything into a .inc file and have two
different recipe names of which I can then include seperately in the respective images.
Many Thanks,
Stuart Weaver
On 2015-09-28 11:59, Daniel. wrote:
I think you're searching for .bbappend don't?
Shouldn't be any need for that - it's his recipe, so he can modify it as he
wishes.
One uses .bbappend to made changes/additions to a recipe where you don't
want (or
can't) modify the original.
http://www.yoctoproject.org/docs/current/dev-manual/dev-
manual.html#us
ing-bbappend-files
Or, maybe, put all the common things in a .inc file, create the recipes,
include the files in recipes. There is also a lot of examples of this:
http://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-bsp/hosta
p/
Cheers,
- dhs
2015-09-28 12:46 GMT-03:00 Gary Thomas <[email protected]
<mailto:[email protected]>>:
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
------------------------------------------------------------
--
_______________________________________________
yocto mailing list
[email protected] <mailto:[email protected]>
https://lists.yoctoproject.org/listinfo/yocto
--
/"Do or do not. There is no try"/
///*Yoda Master*/
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
Regards,
Stuart Weaver
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
