From: "tomzy" <tomasz.zyjewski@3mdeb.com>
To: yocto@lists.yoctoproject.org
Subject: Re: On managing debug and production builds
Date: Mon, 28 Feb 2022 23:04:31 -0800 [thread overview]
Message-ID: <19024.1646118271331133648@lists.yoctoproject.org> (raw)
In-Reply-To: <CAH9dsRiArf_9GgQS4hCg5=J_Jk6cd3eiGaOiQd788+iSLTuU+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
Hi Vinayak
I believe that the best way to prepare debug and prod images is to create
include file (.inc) with base set of packages and features and then add two
.bb recipes, one for prod and one for debug - every of this recipes will need
to include the `.inc` file. You could name them `base-image-prod.bb` and
`base-image-debug.bb`. This way you could run either prod or debug builds
by running `bitbake base-image-debug` or `bitbake base-image-prod`.
As for the machine, this would need to be set in local.conf every time you want
to switch the machine. To simplify this process, for the management of the
configuration of the entire build (including the selection of debug / prod image
or machine configuration), I recommend the kas[1] project with the very helpful
kas-container tool.
[1] https://github.com/siemens/kas
Regards,
Tomasz Żyjewski
Embedded Systems Engineer
GPG: 5C495EA3EBEECA59
https://3mdeb.com | @3mdeb_com
[-- Attachment #2: Type: text/html, Size: 1536 bytes --]
next prev parent reply other threads:[~2022-03-01 7:04 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 [this message]
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
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=19024.1646118271331133648@lists.yoctoproject.org \
--to=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).