Date 1 - 2 of 2
Scope of the build parameters #systemd
toggle quoted message Show quoted text
its Yocto chant #1: "Recipe data is local, configuration data is global."
Means: whatever happens in a recipe, other recipes can't see it. Whatever happens in a configuration file (local, machine, distro), it is visible everywhere. An image is just a recipe, in the end - so whatever you do there, it cannot affect the distribution. In a nutshell: you can't set DISTRO_FEATURES in an image.
On Thu, Nov 3, 2022 at 8:54 PM Martin Leduc via lists.yoctoproject.org <martin.leduc=luminator.com@...> wrote:
Martin Leduc <martin.leduc@...>
I'm wondering how to figure out the scope of a set of parameters. Example. I have an Image (my-core-image-minimal.bb) recipe containing the following parameters
SystemD isn't deployed in my image as the init_manager. Now, I put the parameters into local.conf
I'm confused because my comprehension is when I run bitbake my-core-image-minimal , the parameters defined in this image are defined at the top level of the bitbake configuration parameters no?
Seriously, I have a lots of difficulties understanding the scope of a parameter, where to put it. At the limit, my comprehension is that I can have two recipes:
What does I miss?
Thank you all :)
|1 - 2 of 2|