From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alex Kiernan <alex.kiernan@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-Core][PATCH v2 09/10] packagegroup-core-sdk: Add SDK toolchain language selection support
Date: Wed, 21 Dec 2022 16:39:40 +0000 [thread overview]
Message-ID: <abe8931d3e41dae57f13ab07a8e016c2ded2827f.camel@linuxfoundation.org> (raw)
In-Reply-To: <20221221125306.13779-10-alex.kiernan@gmail.com>
On Wed, 2022-12-21 at 12:53 +0000, Alex Kiernan wrote:
> Use SDK_TOOLCHAIN_LANGS to allow different language support to be
> selected within SDKs. Initially supported options are rust and go.
>
> Signed-off-by: Alex Kiernan <alex.kiernan@gmail.com>
> ---
>
> (no changes since v1)
>
> .../packagegroups/packagegroup-core-sdk.bb | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/packagegroups/packagegroup-core-sdk.bb b/meta/recipes-core/packagegroups/packagegroup-core-sdk.bb
> index d70aff22c725..0e480e6ac756 100644
> --- a/meta/recipes-core/packagegroups/packagegroup-core-sdk.bb
> +++ b/meta/recipes-core/packagegroups/packagegroup-core-sdk.bb
> @@ -11,6 +11,11 @@ inherit packagegroup
>
> #PACKAGEFUNCS =+ 'generate_sdk_pkgs'
>
> +SDK_TOOLCHAIN_LANGS ??= ""
> +SDK_TOOLCHAIN_LANGS:remove:sdkmingw32 = "rust"
> +# libstd-rs doesn't build for mips n32 with compiler constraint errors
> +SDK_TOOLCHAIN_LANGS:remove:mipsarchn32 = "rust"
> +
> RDEPENDS:packagegroup-core-sdk = "\
> packagegroup-core-buildessential \
> coreutils \
> @@ -23,7 +28,10 @@ RDEPENDS:packagegroup-core-sdk = "\
> less \
> ldd \
> file \
> - tcl"
> + tcl \
> + ${@bb.utils.contains('SDK_TOOLCHAIN_LANGS', 'go', 'packagegroup-go-sdk-target', '', d)} \
> + ${@bb.utils.contains('SDK_TOOLCHAIN_LANGS', 'rust', 'packagegroup-rust-sdk-target', '', d)} \
> +"
I'm a little torn on this. I created SDK_TOOLCHAIN_LANGS as a control
for the SDKs from populate_sdk. Whether the target SDK images should
follow that as well, I'm less sure.
It is probably fine and I nearly didn't send a comment but I just
wanted to see what others think.
We could perhaps do something like:
TARGET_TOOLCHAIN_LANGS ??= "${SDK_TOOLCHAIN_LANGS}"
in the recipe to cover the ability to separate the two if we wanted...
Cheers,
Richard
next prev parent reply other threads:[~2022-12-21 16:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 12:52 [OE-Core][PATCH v2 00/10] Add rust runtime tests Alex Kiernan
2022-12-21 12:52 ` [OE-Core][PATCH v2 01/10] oeqa/runtime/rust: Add basic compile/run test Alex Kiernan
2022-12-21 12:52 ` [OE-Core][PATCH v2 02/10] libstd-rs: Merge .inc into .bb Alex Kiernan
2022-12-21 12:52 ` [OE-Core][PATCH v2 03/10] libstd-rs: Move source directory to library/test Alex Kiernan
2022-12-21 12:52 ` [OE-Core][PATCH v2 04/10] rust-llvm: Merge .inc into .bb Alex Kiernan
2022-12-21 12:53 ` [OE-Core][PATCH v2 05/10] rust-llvm: Update LLVM_VERSION to match embedded version Alex Kiernan
2022-12-21 12:53 ` [OE-Core][PATCH v2 06/10] cargo: Merge .inc into .bb Alex Kiernan
2022-12-21 12:53 ` [OE-Core][PATCH v2 07/10] cargo: Extend DEBUG_PREFIX_MAP to cover vendor Alex Kiernan
2022-12-21 12:53 ` [OE-Core][PATCH v2 08/10] packagegroup-rust-sdk-target: Add Rust SDK target packagegroup Alex Kiernan
2022-12-21 12:53 ` [OE-Core][PATCH v2 09/10] packagegroup-core-sdk: Add SDK toolchain language selection support Alex Kiernan
2022-12-21 16:39 ` Richard Purdie [this message]
2022-12-21 16:42 ` Alex Kiernan
2022-12-21 18:54 ` Khem Raj
2022-12-21 12:53 ` [OE-Core][PATCH v2 10/10] oeqa/runtime/rust: Add cargo test Alex Kiernan
2022-12-21 21:20 ` [OE-Core][PATCH v2 00/10] Add rust runtime tests Alexandre Belloni
2022-12-21 22:34 ` Alex Kiernan
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=abe8931d3e41dae57f13ab07a8e016c2ded2827f.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kiernan@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.