Re: On managing debug and production builds

["tomzy" <tomasz.zyjewski@3mdeb.com>]

[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]

> 
> Thanks Tomasz. I will check kas.

No problem

> 
> Yes, for selecting some of the packages I have created prod and debug
> image
> recipes.But this did not work for the kernel as the kernel recipe is
> picked
> as part of PROVIDERin machine conf.

What are the difference there? You want to use different config on prod and debug images?
Maybe add it as config fragments? Then you would need to add some global variable to
distinguish when use given .cfg file.

[1] https://docs.yoctoproject.org/singleindex.html#creating-configuration-fragments

> 
> SoI had to use 2 conf to have the
> IMAGE_FEATURES (orany other var)set differently for prod and debug. This
> is for
> building the kernelrecipie differently for prodand debug. Setting the
> IMAGE_FEATURES in the image recipe (and not inconf) causes2 problems. One
> is
> that kernel and other bootloaders recipes arepicked early via PROVIDER in
> conf
> and not as packages included in image recipe.

Is that a problem?

> 
> Secondly,setting the var in the
> image recipe breaks this command for e.g.
> "bitbake base-image-prod.bbbase-image-debug.bb".

Didn't you want to distinguish this to builds to be able to run `bitbake base-image-prod` or
`bitbake base-image-debug`?

> 
> Since the command parses the recipes only once for both image creation.

Nevertheless I would greatly recommend you to use kas. In simple .yml file you
could prepare different `local.conf` per configuration prod/debug.

[2] https://kas.readthedocs.io/en/latest/userguide.html#project-configuration

Regards,
Tomasz Żyjewski
Embedded Systems Engineer
GPG: 5C495EA3EBEECA59
https://3mdeb.com | @3mdeb_com

[-- Attachment #2: Type: text/html, Size: 2377 bytes --]