Re: [bitbake-devel] [PATCH] bitbake-setup: pass install-buildtools options from config and CLI

Hi Alex,

Any downstream distro that builds its own extended buildtools tarball under a non-Poky distro name hits a FileNotFoundError because install-buildtools
hardcodes pokysdk when looking for environment-setup-<arch>-pokysdk-linux. The --sdk-name option fixes that hardcoded assumption.

The archive itself contains the same tools as upstream extended buildtools — it can't be provided via recipes because buildtools exist specifically to
bootstrap the host environment before BitBake can run.

The --url and --filename options are needed for projects that host their buildtools on an internal server rather than yoctoproject.org, and want to pin a
specific version across the team without requiring manual arguments on every invocation.

The workaround today is to pass arguments manually or modify wrapper scripts, which is probably why this hasn't surfaced as a bug report before.

The --sdk-name option itself is introduced in a companion patch to oe-scripts/install-buildtools in openembedded-core:
https://lists.openembedded.org/g/openembedded-core/topic/patch_install_buildtools/119814299

Thanks,
Jaipaul Cheernam


From: Alexander Kanavin <[email protected]>
Date: Monday, 15 June 2026 at 15:32
To: Jaipaul Cheernam <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: [bitbake-devel] [PATCH] bitbake-setup: pass install-buildtools options from config and CLI

On Mon, 15 Jun 2026 at 14:19, Jaipaul Cheernam via
lists.openembedded.org
<[email protected]> wrote:
> Allow distro-specific buildtools to be configured with a custom URL,
> filename, and SDK name via an install-buildtools section in
> config-upstream.json. Expose the same options as CLI arguments: --url,
> --filename, --sdk-name, --no-check. CLI arguments take precedence over
> config values.
>
> This requires the --sdk-name option to be available in
> oe-scripts/install-buildtools from openembedded-core.

Can you please describe the use case? Presumably this is useful in
your environment, I'd like to understand the specifics of what you put
in the custom buildtools archive and why it has to be there and not
built via recipes.

Alex