I ended up completely overriding EXTRA_OECONF in my .bbappend with the configure flags that I wanted. I guess I don't understand the order of evaluation in yocto's .bbappend and .bb files. Based on

Hello Josef, Let me redefine the question? May I? What is the difference while building an IMAGE="core-image-minimal" using DISTRO="poky-tiny" versus building an IMAGE="core-image-minimal" using

--- scripts/lib/wic/ksparser.py | 1 + scripts/lib/wic/partition.py | 1 + scripts/lib/wic/plugins/source/rootfs.py | 7 ++++--- 3 files changed, 6 insertions(+), 3

I currently have an image with six different partitions. See the following partition configuration: My problem is now that if I use the wic -e option to specify an image name as rootfs-dir I can

Hello All, I am creating custom meta-layer for my project work, but some of my third package is not able to fine the dependent library and package previously in yocto daisy1.6 all the dependent

core-image-minimal is a IMAGE poky-tiny is a DISTRO Its just different things. ——————————————— Josef Holzmayr Software Developer Embedded Systems Tel: +49 8444

<martyn.welch@...> wrote: If not in insane.bbclass, a new image-insane.bbclass. I dislike it being defined in multiple places. -- Otavio Salvador O.S.

Create symlinks in bindir to jar and javah. If a recpie needs jar to create a jar file or javah for a JNI package, jar and javah needs to be in bindir. ---

I don't know. The logic for IMAGE_QA_COMMAND is in image.bbclass, as far as I can see the package QA tests are in package.bbclass, so image.bbclass seemed like a reasonable place to put the image QA

That's what I initially thought... ... print "Hello" ... Hello

This was already discussed - the test should be on the image rather than package level: http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144335.html Alex

The best way to fix this is to modify the original recipe so that all three options become PACKAGECONFIG-configurable, and submit the patch to whoever maintains the recipe. Alex

> DISTRO = "poky-tiny" and i get the following What is the difference between core-image-minimal and poky-tiny? Thank you, Zoran

hi i am trying to compile the yocto-tiny for raspberry pi by adding the distro to my local.conf DISTRO = "poky-tiny" and i get the following ERROR: nothing provides 'virtual/kernel' ERROR:

isn't it this class meta/classes/insane.bbclass for this type of checks? Martyn Welch <martyn.welch@...> wrote:

I would like to filter out two configure flags from EXTRA_OECONF in a .bbappend. When I filter out only one everything works, when I do the same thing twice it doesn't. Here is the .bbappend that

That is EXACTLY what I am looking for. Thanks! A "nice to have" would be a check to see if any AUTOREVs has snuck in since last srcrev.conf generation. I'd like to validate/ensure this with a build

<martyn.welch@...> wrote: for p in path.split(':'): if not p.startswith('/'): so you can drop the if path != "". An empty list won't go inside the for. Each item

Paul Knopf <pauldotknopf@...> wrote: would this tool be useful for your needs? I do not fully grasp what you want to do. ---- You can use the buildhistory-collect-srcrevs command with the -a

Add documentation for the IMAGE_QA_PROHIBITED_PATHS variable and associated prohibited-path QA test Signed-off-by: Martyn Welch <martyn.welch@...> --- Changes since v1: - Correcting