From: Vinayak Menon <menon.vinayak@gmail.com>
To: tomzy <tomasz.zyjewski@3mdeb.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] On managing debug and production builds
Date: Wed, 2 Mar 2022 11:59:33 +0530 [thread overview]
Message-ID: <CAH9dsRgUsFarc+fvjcAo7ocekB7__eDWvWks8ej23A9EzPk--w@mail.gmail.com> (raw)
In-Reply-To: <CAH9dsRgmBt-Y-P0P+1o1u6RC2WqFXH03nURMnaDpZJjNH_nE0Q@mail.gmail.com>
Add list. missed earlier.
On Wed, Mar 2, 2022 at 8:11 AM Vinayak Menon <menon.vinayak@gmail.com> wrote:
>
> On Tue, Mar 1, 2022 at 2:56 PM tomzy <tomasz.zyjewski@3mdeb.com> wrote:
> >
> > 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.
>
> Ya, and I am using exisitng IMAGE_FEATURE instead of the global var. I
> can use global var too.
> The only thing is that I am setting the global var from a conf and not
> image recipe.
>
> >
> > [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 are picked early via PROVIDER in conf
> > and not as packages included in image recipe.
> >
> > Is that a problem?
>
> Ya you are right, that is not a problem as such. But I have seen in the yocto
> documentation that IMAGE_FEATURES are recommended to be set from conf.
> Is there any reason for such a recommendation ?
>
> >
> > 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`?
>
> Yes I want to distinguish, and as a developer I can give separate
> bitbake commands. But the
> thought was that later the user can issue commands the way they want.
> And if they use it in
> combined manner described above, expecting 2 images with different
> kernels, it does not work.
>
>
> >
> > 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.
>
> Sure, I will explore this.
>
>
> >
> > [2] https://kas.readthedocs.io/en/latest/userguide.html#project-configuration
> >
> > Regards,
> > Tomasz Żyjewski
> > Embedded Systems Engineer
> > GPG: 5C495EA3EBEECA59
> > https://3mdeb.com | @3mdeb_com
> >
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#56335): https://lists.yoctoproject.org/g/yocto/message/56335
> > Mute This Topic: https://lists.yoctoproject.org/mt/89469781/6783826
> > Group Owner: yocto+owner@lists.yoctoproject.org
> > Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [menon.vinayak@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
>
>
> --
> vinayak
--
vinayak
prev parent reply other threads:[~2022-03-02 6:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 5:06 On managing debug and production builds Vinayak Menon
2022-03-01 7:04 ` tomzy
2022-03-01 8:52 ` [yocto] " Vinayak Menon
2022-03-01 8:58 ` Alexander Kanavin
2022-03-01 9:26 ` tomzy
2022-03-02 3:22 ` [yocto] " Karthik Poduval
2022-03-02 6:50 ` Josef Holzmayr
[not found] ` <CAH9dsRgmBt-Y-P0P+1o1u6RC2WqFXH03nURMnaDpZJjNH_nE0Q@mail.gmail.com>
2022-03-02 6:29 ` Vinayak Menon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAH9dsRgUsFarc+fvjcAo7ocekB7__eDWvWks8ej23A9EzPk--w@mail.gmail.com \
--to=menon.vinayak@gmail.com \
--cc=tomasz.zyjewski@3mdeb.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).