On Thu, 10 Oct 2024 at 05:45, Guo, Yanmei via Lists.Yoctoproject.Org
<yanmei.guo=boeing....@lists.yoctoproject.org> wrote:
> Can you explain a bit more on separate build configurations?
>
> We are using multi-config to separate the build configuration. However the 
> `local.conf` and `bblayers.conf` are shared across.
> unless you are suggesting complete new build (new local.conf and bblayers) 
> not sharing anything in common.

Yes, I'm suggesting exactly that. There are standard mechanisms
(configuration templates) that allow you to save and maintain these
files directly inside the layers, and initialize the build/ directory
using them.

> In addition, is there a recommended way to manage debug/release build in 
> which case they share common configurations but also varies in lots of areas.

First, you should carefully consider if you need separate
debug/release builds at all. What would differ between them? Can you
achieve the same thing in a single build by having different image
recipes with their own set of packages and image tweaks? Can you
configure your software to make those decisions at runtime when it
starts (e.g. decide to run 'debug' or 'release' mode depending on what
is written into a target configuration file)?

If you do need two different builds (which will double the load on
your CI), then you should make two different distributions. They need
not be entirely separate: they can share almost everything in a common
.inc, and only a few tweaks in the top level distro.conf file. Then
local.conf only needs to set DISTRO to choose one or the other.

Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#64003): https://lists.yoctoproject.org/g/yocto/message/64003
Mute This Topic: https://lists.yoctoproject.org/mt/108661552/21656
Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to