public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <ch@denx.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 0/2] Integrate compatibiliy systems
Date: Thu, 17 Aug 2023 17:00:18 +0200	[thread overview]
Message-ID: <85470f6c-10d5-4ac2-8b49-019cef6549c2@denx.de> (raw)
In-Reply-To: <ZN4zSy18TGUfEqgP@ilbers.de>

Hi Baurzhan

On 2023-08-17 16:48, Baurzhan Ismagulov wrote:
> Thanks Claudius for the patches,
> 
> On 2023-08-17 15:57, Claudius Heine wrote:
>> this patchset add MACHINEOVERRIDES, DISTROOVERRIDES as well as
>> COMPATIBLE_MACHINE features from OE.
> 
> Just out of curiosity, for which use case did you need this?

This is needed for the COMPATIBLE_MACHINE feature as well as writing one 
recipe that can be reused for different machines/distros with slightly 
different configurations.

Here are some examples:
  - Creating a custom debian based distribution by patching debian 
certain packages, but still being compatible to the debian distribution 
and reusing their `:debian-bookworm`, etc overrides, where applicable.
  - Creating BSP package layers that support multiple different boards 
with the same or a different soc, where some packages/recipes are soc 
specific, some are board specific.

All of that is possible with other means, but using the *OVERRIDES and 
COMPATIBLE_* variables is the most straight forward and accustomed way 
for developers coming from OE.

In my case, I am integrating a couple of boards based on different tegra 
variants in one BSP.

regards,
Claudius

> 
> With kind regards,
> Baurzhan
> 

-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

  reply	other threads:[~2023-08-17 15:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-17 13:57 Claudius Heine
2023-08-17 13:57 ` [PATCH 1/2] meta/bitbake.conf: add MACHINEOVERRIDES and DISTROOVERRIDES Claudius Heine
2023-08-17 13:57 ` [PATCH 2/2] meta/base.bbclass: integrate COMPATIBLE_MACHINE feature Claudius Heine
2023-08-17 14:06   ` Anton Mikanovich
2023-08-17 14:45     ` Claudius Heine
2023-08-17 14:49       ` Anton Mikanovich
2023-08-23  7:53         ` Uladzimir Bely
2023-08-17 14:09 ` [PATCH 0/2] Integrate compatibiliy systems Anton Mikanovich
2023-08-17 14:48 ` Baurzhan Ismagulov
2023-08-17 15:00   ` Claudius Heine [this message]
2023-08-17 15:05     ` Baurzhan Ismagulov
2023-08-24 15:15 ` Uladzimir Bely

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=85470f6c-10d5-4ac2-8b49-019cef6549c2@denx.de \
    --to=ch@denx.de \
    --cc=isar-users@googlegroups.com \
    /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