Hi All, Had a question about kernel-fitimage.bbclass. I am enabling the fitimage using KERNEL_CLASSES += "kernel-fitimage" and KERNEL_IMAGETYPE = "fitImage". It works and I see fitimage in my deploy

Hi Probably you're inheriting from some more complex image class that pulls in the undesired packages. Have you already checked bitbake -e to see how the variables get expanded? Greetz -- Josef

Hi, I tried that but it does pull other packages even if I set in my image: IMAGE_FEATURES = "" IMAGE_LINGUAS = "" PACKAGE_INSTALL = "my-layout-recipe" Regards -- Ayoub Zaki Embedded Systems

Hi Should be possible if your image installs only your specific recipes that populate those directories. Means: no packagegroup-core-boot, no base-passwd, no.... -> then nothing should bring along

Hi, you can add to local.conf or distro.conf : include conf/machine/${MACHINE}-extra.conf then create in your meta layer or bsp layer

When publishing a layer, send an email notification to all of that layer's maintainers. Fixes [YOCTO #11208] Signed-off-by: Amanda Brindle <amanda.r.brindle@...> --- layerindex/views.py

The following changes since commit ad1aac4ea5d4f2b327f7bd9611aed13f7c31ff7e: Show note if layer branch hasn't been indexed (2017-10-04 13:49:00 +1300) are available in the git repository at:

That would be one way. You could also over-ride from any other global config file, e.g. local.conf or the distro config file (if you have one). Right, the variable is not used by the image recipe, so

Hi, I would like to generate an image that contains a custom directories layout for expl: foo/ ├── bar1 │   └── bar2 │       ├── config │       └──

Or better yet use http://www.yoctoproject.org/docs/2.3.2/mega-manual/mega-manual.html#ref-classes-image-buildinfo to get: ----------------------- Build Configuration:

Hi Richard (and all), @Richard: Thanks for the input regarding the topic and apologies for not replying until now, I was a bit buried under workload and simultaneously completing my Masters studies.

bitbake-layers supports at least some of this functionality: $ bitbake-layers -h NOTE: Starting bitbake server... usage: bitbake-layers [-d] [-q] [-F] [--color COLOR] [-h] <subcommand> ... BitBake

I think bitbake -e could be of some help with these two things. It's not particularly compact, but it tells you the full story. Alex

Hello, I am not sure if you've found the OpenEmbedded Layer Index [0] yet, but that's a good resource and an example of what can be done. I believe the source code is available [1] and I've toyed

Suppose I have the following bugfix patch for a 3rd party machine conf file I am using: diff --git a/conf/machine/colibri-vf.conf b/conf/machine/colibri-vf.conf index 3ddef79..ba47488 100644 ---

I am a new user for a few weeks now, trying to make a customized image for a toradex colibri-vf module, so far I have succeeded in the following disciplines: * adding the 3rd party layers that I

Hi, That's easy to do : do_install_append () {     for layer in ${BBLAYERS}; do         cd $layer         echo -n "$(basename $layer) = "  >>

I've noticed that bitbake prints the git commit versions of the layers when the build starts. meta-python = "HEAD:b40116cf457b88a2db14b86fda9627fb34d56ae6" meta-mender-core =

Hi Fabien, Good to know that it helps here. Submitted the patch to oe-core mailing list today: http://lists.openembedded.org/pipermail/openembedded-core/2017-October/143288.html Thanks and

I found a bug in the GNU assembler that makes it produce corrupted listings, reported it on sourceware bugzilla, and it has been fixed. Now I'd like to take those small patches and apply them to the