public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alejandro Hernandez <alhe@linux.microsoft.com>,
	 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 21:01:53 +0000	[thread overview]
Message-ID: <001cd479982cd530afb67cda3051f71876e9dc32.camel@linuxfoundation.org> (raw)
In-Reply-To: <fdc3ba7d-e193-4c58-885a-2f269eaf7159@linux.microsoft.com>

On Mon, 2026-03-16 at 10:37 -0600, Alejandro Hernandez wrote:
> 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.

We need to try and keep the information concise and not have too much
there. I'd have thought TARGET_SYS should already have the libc
information as part of the target triplet?

Also, you can customise this locally if that helps.

Cheers,

Richard


  reply	other threads:[~2026-03-16 21:02 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   ` [OE-core] " Alejandro Hernandez
2026-03-16 21:01     ` Richard Purdie [this message]
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=001cd479982cd530afb67cda3051f71876e9dc32.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alhe@linux.microsoft.com \
    --cc=openembedded-core@lists.openembedded.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