Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: twoerner@gmail.com, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] sdk: fold SDK_TOOLCHAIN_LANGS into SDK_FEATURES
Date: Thu, 06 Aug 2026 13:30:15 +0100	[thread overview]
Message-ID: <a5f9084c7e6427dfd1ac0765836ab3a44612f01a.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260805070136.3499233-3-twoerner@gmail.com>

On Wed, 2026-08-05 at 03:01 -0400, Trevor Woerner via lists.openembedded.org wrote:
> Selecting the toolchain languages for an SDK is the same kind of choice
> as selecting any other optional SDK content, so it does not need a list
> of its own.
> 
> Make "go" and "rust" values of SDK_FEATURES and mark SDK_TOOLCHAIN_LANGS
> as renamed so existing settings are reported rather than silently
> ignored.

Thanks Trevor, this is going in the right direction.

> diff --git a/meta/conf/fragments/yocto-autobuilder/autobuilder.conf b/meta/conf/fragments/yocto-autobuilder/autobuilder.conf
> index a9ae99a451e6..601cf269ab04 100644
> --- a/meta/conf/fragments/yocto-autobuilder/autobuilder.conf
> +++ b/meta/conf/fragments/yocto-autobuilder/autobuilder.conf
> @@ -9,6 +9,6 @@ IMAGE_CLASSES += 'testimage'
>  SDK_EXT_TYPE = 'minimal'
>  SDK_INCLUDE_TOOLCHAIN = '1'
>  ESDK_LOCALCONF_REMOVE:append = 'BB_HASHSERVE'
> -SDK_TOOLCHAIN_LANGS += 'go rust'
> +SDK_FEATURES:append = ' go rust'
>  PTEST_EXPECT_FAILURE = '1'

Can we not just stick with += rather than append?

Cheers,

Richard


      reply	other threads:[~2026-08-06 12:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05  7:01 [PATCH 0/2] add an SDK_FEATURES lever Trevor Woerner
2026-08-05  7:01 ` [PATCH 1/2] bitbake.conf: " Trevor Woerner
2026-08-05  7:01 ` [PATCH 2/2] sdk: fold SDK_TOOLCHAIN_LANGS into SDK_FEATURES Trevor Woerner
2026-08-06 12:30   ` Richard Purdie [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=a5f9084c7e6427dfd1ac0765836ab3a44612f01a.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=twoerner@gmail.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