Thanks for input. In meantime certain time ago, I guess there were different types of bitbake-layers output (I has short opportunity to analyze) which comment several number of packages/recipes by "re

#bitbake

Hi, From all variables which qualify to be set/modified in conf/local.conf, among others those documented in conf/local.conf template, are any to be set /modified only in conf/local.conf? There is one

I wonder what are all possible criteria for Bitbake to decide to skip recipe (please compare to reports delivered by bitbake-layers). Recipe overlay, recipe version, others? Which knowledge source to

#bitbake

As for project here Poky operates on headless server. Developers use SSH to interact with Poky, to handle its input data, and to access build results. Must gtk3 be installed locally to Poky or will ta

#bitbake

If yes, me wonders how to force Bitbake to build that recipe, if for target system gtk is not built, there is actually no target depending on gtk. Hence, I add such recipe Bitbake might ignore it as t

#bitbake

Myself wonders if the answer is just to enable a recipe building native package gtk of version 3.0.

#bitbake

Hi, Myself had to ask web search engine for usage of Task Dependency Explorer taskexp as I didn't succeed on search in Yocto materials. Hence, the way I try to use taskexp might be not right. In the f

#bitbake

I wonder if all the artifacts described in YP Development Manual, current release, ch. 3.32* yet only those describing software composition (for purposes of compliance with copyleft software) will cha

Regarding package feed packages index I learned one difference between rpm and ipk. For ipk plain-text files named Packages are generated and placed to architecture-subdirectories in tmp/deploy/ipk tr

Thanks for hint. Which qualities might current implementation output still miss? I tried to ask in meantime three Yocto books for help but no clear help got. My search went toward distribution-level m

1. Where to learn more about above command options (file path the file referred to to be found; file path usage in command option,....)? 2. Set/modify variable in bitbake command line, e.g. BBPATH="xy

Thanks for input from you. Does this mean shown differences in directory tree is result, a mix of these all listed parameters? I am aware of these are two different distributions. I am aware of these

Thanks for helpful input. This matches my own observation. Tool-chain used in project requires additionally license.manifest file on its input. For some reason it also takes a look into files named Pa

One more question: plain-text files named 'Packages' and placed during distribution build in subtrees tmp/deploy/rpm, .../ipk, ... are these artifacts supported YP releases can still build?

Two projects are given. They use different YP release each. Projects use also different target platform each. I wonder if differences in structuring metadata- and recipes- directory tree between these

How are the odds for this question to get more audience on stackoverflow? In meantime I tried to search release notes of all YP releases starting the oldest used here for related entries. Unsure if it

Hello, This is about two projects Projects A and B. Both use Yocto to build embedded-Linux distribution. However different Yocto release each. Also different target platform each. One puts Linux softw

Sorry for be that late. Just for fellows who in future look answers to above question (like me today). I really like Philips feedback, thanks for that: https://lists.openembedded.org/g/openembedded-ar