public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Alejandro Hernandez <alhe@linux.microsoft.com>
To: richard.purdie@linuxfoundation.org,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/5] bitbake.conf: Add SDKMACHINE to BUILDCFG_VARS, drop TARGET_FPU
Date: Mon, 16 Mar 2026 10:37:38 -0600	[thread overview]
Message-ID: <fdc3ba7d-e193-4c58-885a-2f269eaf7159@linux.microsoft.com> (raw)
In-Reply-To: <20260314094758.3929192-2-richard.purdie@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 1956 bytes --]

Hello,

What are your thoughts on including TCLIBC in BUILCFG_VARS?.

I often find myself missing this key information, but I may be biased due to my particular usecase,
hence I would like other folks opinion on how useful this may be for the general public, sometimes
we get similar information from TARGET_OS / LIBCEXTENSION, but that isn't always the case.

Thanks

Alejandro

On 3/14/2026 3:47 AM, Richard Purdie via lists.openembedded.org wrote:
> Tweak the default build header to add SDKMACHINE and drop TARGET_FPU since
> that data is more likely to be of use to the general user.
>
> Signed-off-by: Richard Purdie<richard.purdie@linuxfoundation.org>
> ---
>   meta/conf/bitbake.conf | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 5f632d9f8e7..6b3443695a0 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -761,7 +761,7 @@ PREFERRED_PROVIDER_virtual/fakeroot-native ?= "pseudo-native"
>   
>   # Pre-build configuration output
>   BUILDCFG_HEADER = "Build Configuration${@" (mc:${BB_CURRENT_MC})" if d.getVar("BBMULTICONFIG") else ""}:"
> -BUILDCFG_VARS = "BB_VERSION BUILD_SYS NATIVELSBSTRING TARGET_SYS MACHINE DISTRO DISTRO_VERSION TUNE_FEATURES TARGET_FPU"
> +BUILDCFG_VARS = "BB_VERSION BUILD_SYS NATIVELSBSTRING TARGET_SYS MACHINE SDKMACHINE DISTRO DISTRO_VERSION TUNE_FEATURES"
>   BUILDCFG_VARS[type] = "list"
>   BUILDCFG_NEEDEDVARS = "TARGET_ARCH TARGET_OS"
>   BUILDCFG_NEEDEDVARS[type] = "list"
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#233077):https://lists.openembedded.org/g/openembedded-core/message/233077
> Mute This Topic:https://lists.openembedded.org/mt/118311455/4354175
> Group Owner:openembedded-core+owner@lists.openembedded.org
> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub [alhe@linux.microsoft.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

[-- Attachment #2: Type: text/html, Size: 3017 bytes --]

  reply	other threads:[~2026-03-16 16:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-14  9:47 [PATCH 1/5] sstate: Drop unneeded SSTATE_MANMACH variable Richard Purdie
2026-03-14  9:47 ` [PATCH 2/5] bitbake.conf: Add SDKMACHINE to BUILDCFG_VARS, drop TARGET_FPU Richard Purdie
2026-03-16 16:37   ` Alejandro Hernandez [this message]
2026-03-16 21:01     ` [OE-core] " Richard Purdie
2026-03-14  9:47 ` [PATCH 3/5] allarch/lib: Convert core of allarch code into a function Richard Purdie
2026-03-14  9:47 ` [PATCH 4/5] meta/dummy-sdk-package: Improve SDK dummy package handling Richard Purdie
2026-03-15 14:08   ` [OE-core] " Mathieu Dubois-Briand
2026-03-14  9:47 ` [PATCH 5/5] sstate: Tweak SDK sstate package architecture Richard Purdie
     [not found] ` <189CAC32AB5A06DA.1508127@lists.openembedded.org>
2026-03-14 10:00   ` [OE-core] [PATCH 4/5] meta/dummy-sdk-package: Improve SDK dummy package handling Richard Purdie
2026-03-14 14:40     ` Bruce Ashfield
     [not found]   ` <189CACDC59FF3062.2629287@lists.openembedded.org>
2026-03-14 10:28     ` Richard Purdie
2026-03-16 16:37       ` Randy MacLeod

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=fdc3ba7d-e193-4c58-885a-2f269eaf7159@linux.microsoft.com \
    --to=alhe@linux.microsoft.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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