Mat,
I'm fairly new to OpenEmbedded (4 months now and I still feel like a noobi but
I'm trying to give back while the pain is still fresh in my mind)
For something like u-boot it kind of depends on what your changing. If you need
to change the u-boot code and the changes are small then typically you'd create
a patch f for your changes and then make them part of a .bbappend in your layer
for the recipe. There are examples on the net for how to create a .bbappend and
reference the patch file.
Generally your .bbappend can be as simple as:
FILESEXTRAPATHS_prepend = ":${THISDIR}/files"
SRC_URI += "files://xyzzy.patch"
Where your patches are in subdirectory of your recipe directory.
Remember that generally recipes are about how to obtain the code, build it and
package it for distribution, you can do recipes that deal with a pre-built
binary but that is generally not the case.
Hope this helps,
Matt S.
From: [email protected] [mailto:[email protected]] On
Behalf Of [email protected]
Sent: Thursday, December 04, 2014 1:49 AM
To: [email protected]
Subject: Re: [yocto] u-boot precompiled ?
Even if this is a stupid question a little advise would be nice ... like "don't
ask so stupid questions, go read this and that" or something... no time ?
Should I rather unsubscribe from this list until I'm an expert?
Von: Heise, Matthias
Gesendet: Mittwoch, 3. Dezember 2014 15:15
An: '[email protected]'
Betreff: u-boot precompiled ?
Hi all,
I'm still trying to find out basic things about getting a system up and
running. This question is about U-Boot, is it right that for example for my
wandboard a pre-compiled *.imx is just downloaded ?
So if I want to make settings to U-Boot I make them directly in the source,
compile it and re-direct in a recipe to take that new file as bootloader ? Or
can I make the settings within a recipe and I just didn't find the spot ?
Thanks for your time,
Regards
Mat
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
