On Sat Jul 25, 2026 at 5:51 AM CEST, Deepesh via lists.openembedded.org 
Varatharajan wrote:
> From: Deepesh Varatharajan <[email protected]>
>

Hi Deepesh,

> [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).
>
> Performance (clean core-image-sato build, qemux86-64):
>
> --- /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 sources"
> +HOMEPAGE = "http://www.rust-lang.org";
> +SECTION = "devel"
> +LICENSE = "(Unicode-3.0 AND (Apache-2.0 OR MIT)"

We are missing a closing parentheses here. I believe you can remove the
opening one.

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#242087): 
https://lists.openembedded.org/g/openembedded-core/message/242087
Mute This Topic: https://lists.openembedded.org/mt/120436471/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to