We get below host contamination warnings of license files for
each recipe, when we try to create a separate ${PN}-lic package (which
contains license files), by setting LICENSE_CREATE_PACKAGE equal to "1"
in local.conf.
-- snip --
WARNING: QA Issue: libcgroup:
/libcgroup-lic/usr/share/licenses/li
Hooking up a serial console is a "developer mode", the chances are pretty good
developers are interested in watching the kernel boot log on the console so
they can spot any problems or diagnose any failed boots (e.g. can't find root
fs).
Signed-off-by: Trevor Woerner
---
scripts/contrib/mkefidis
Regardless of which image is built using which layers, try to ensure the image
on the SD device being prepared is the one that is booted automatically when
the board is powered.
Signed-off-by: Trevor Woerner
---
scripts/contrib/mkefidisk.sh | 3 +++
1 file changed, 3 insertions(+)
diff --git a/
I was poking at the layer index and ran across this:
http://layers.openembedded.org/layerindex/branch/master/recipes/?q=devmem
The recipe appears in 4 layers.
Should we just move it to openembedded-core? I wonder how easy it would
be to have the layer index report duplicate recipes?
Philip
--
