From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <deepesh.varatharajan@windriver.com>,
<openembedded-core@lists.openembedded.org>
Cc: <Deepesh.Varatharajan@windriver.com>
Subject: Re: [OE-core] [PATCH v2 2/3] rust: refactor source handling into a shared work-shared recipe
Date: Thu, 23 Jul 2026 07:33:22 +0200 [thread overview]
Message-ID: <DK5PEQXXJ9YA.34F0OF7DED7VM@bootlin.com> (raw)
In-Reply-To: <20260722061757.109411-2-Deepesh.Varatharajan@windriver.com>
On Wed Jul 22, 2026 at 8:17 AM CEST, Deepesh via lists.openembedded.org Varatharajan wrote:
> From: Deepesh Varatharajan <Deepesh.Varatharajan@windriver.com>
>
> [YOCTO #15808]
>
> Consolidate Rust source management across all Rust recipes (rust, cargo,
> libstd-rs and their native/nativesdk variants) into a single shared
> source tree using the work-shared pattern.
>
> Disk savings: a world build with multilibs enabled, together with
> nativesdk-rust and nativesdk-cargo, now shares a single ~4.2 GB rustc-src
> tree instead of maintaining up to 11 independent copies (~46.2 GB total).
>
Hi Deepesh,
> --- /dev/null
> +++ b/meta/recipes-devtools/rust/rust-source.bb
> @@ -0,0 +1,56 @@
> +# rust-source.bb - Shared source recipe for the Rust toolchain
> +#
> +# This recipe fetches, unpacks, and patches the rustc source tree into a
> +# work-shared location so that rust, cargo, libstd-rs, and their native/nativesdk
> +# variants all share a single copy of the source. This eliminates duplication
> +# (up to 11 copies of the ~4.2 GB source tree in multilib + nativesdk builds)
> +# and significantly reduces disk usage (~46.2 GB -> ~4.2 GB for rustc-src).
> +#
> +# Only do_fetch, do_unpack, and do_patch are meaningful here. All other
> +# tasks are disabled since this recipe exists solely to provide sources.
> +
> +SUMMARY = "Rust compiler and runtime libaries"
> +HOMEPAGE = "http://www.rust-lang.org"
> +SECTION = "devel"
> +LICENSE = "(MIT | Apache-2.0) & Unicode-3.0"
Please use the new LICENSE syntax here...
> --- a/meta/recipes-devtools/rust/rust_1.96.1.bb
> +++ b/meta/recipes-devtools/rust/rust_git.bb
> @@ -4,6 +4,10 @@ SECTION = "devel"
> LICENSE = "(MIT | Apache-2.0) & Unicode-3.0"
... and here.
Parsing recipes...WARNING: /srv/pokybuild/yocto-worker/beaglebone/build/layers/openembedded-core/meta/recipes-devtools/rust/rust-source.bb: rust-source-1.96.1: LICENSE is using an old syntax and should be upgraded to: "Unicode-3.0 AND (Apache-2.0 OR MIT)"
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-07-23 5:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 6:17 [PATCH v2 1/3] rust: Fix reproducibility with shared source trees Deepesh.Varatharajan
2026-07-22 6:17 ` [PATCH v2 2/3] rust: refactor source handling into a shared work-shared recipe Deepesh.Varatharajan
2026-07-23 5:33 ` Mathieu Dubois-Briand [this message]
2026-07-22 6:17 ` [PATCH v2 3/3] rust: Move do_update_snapshot to rust-source Deepesh.Varatharajan
2026-07-22 13:33 ` [OE-core] [PATCH v2 1/3] rust: Fix reproducibility with shared source trees Mathieu Dubois-Briand
2026-07-22 14:46 ` Varatharajan, Deepesh
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=DK5PEQXXJ9YA.34F0OF7DED7VM@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=deepesh.varatharajan@windriver.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