From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Randy MacLeod <randy.macleod@windriver.com>,
Harish Sadineni <Harish.Sadineni@windriver.com>,
bruce.ashfield@gmail.com
Cc: Sundeep.Kokkonda@windriver.com, yoann.congal@smile.fr,
elmehdi.younes@smile.fr,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2 03/15] rust: install Rust library sources for 'make rustavailable' support
Date: Wed, 07 Jan 2026 19:03:56 +0000 [thread overview]
Message-ID: <1441d3bab7f90779a57c82e940369a8a6dd53786.camel@linuxfoundation.org> (raw)
In-Reply-To: <980e869b-15e4-4b6a-a2ac-3e13ecb43b00@windriver.com>
On Wed, 2026-01-07 at 13:21 -0500, Randy MacLeod wrote:
>
> On 2026-01-07 11:34 a.m., Harish Sadineni wrote:
>
> > On 1/7/2026 12:29 AM, Randy MacLeod wrote:On 2026-01-05 11:24 a.m.,
> > Harish Sadineni wrote:
> > > We don't want the rust recipe to change based on a kernel config
> > > unless we *really* have to
> > > since that essentially doubles the testing that should be done
> > > or leaves a gap in testing of the
> > > rust builds. If you do that for the kernel first, then another
> > > recipe later, soon you have a maintenance mess.
> > >
> > > Also if the kernel needs these files, then it's likely that
> > > other software will need it as well.
> > > You should analyze why the kernel needs these files and why
> > > other recipes do not. Perhaps any
> > > kernel-like image will have the same requirement. Is there a
> > > baremetal image using rust anywhere
> > > that you can use to check on that? I looked but all I found was:
> > > https://github.com/ahcbb6/baremetal-helloqemu-rust
> > > Anyway, let's focus on the linux kernel's requirements for now.
> > >
> > >
> > > So, how many files are needed and how much FS space do they use?
> > The file size of the library directory is around 50MB.
> > I've been around since the 1990s, 50 MB doesn't seem small to me
> > but
> let's see what other people think.
>
>
> Also, how may files is that?
>
> What's the content? ls -lR if the list isn't too long.
>
> Does the kernel build need each and every file ? How did you check?
> Can we automate the generation of the list of required files by
> scraping the data from the kernel perhaps?
>
In the scheme of things, 50MB is not great but probably ok. It will be
compressed down for sstate and so on.
It does however need to be in a separate target package, that is
important.
The win here is that if you change DISTRO_FEATURES, rust/rust-native
shouldn't be rebuilding, which is worth a bit of disk usage, IMO at
least.
Cheers,
Richard
>
next prev parent reply other threads:[~2026-01-07 19:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-30 14:15 [PATCH v2 00/15] Enable rust support for linux kernel Harish.Sadineni
2025-12-30 14:15 ` [PATCH v2 01/15] bindgen-cli: extend BBCLASSEXTEND to include nativesdk Harish.Sadineni
2026-01-12 0:10 ` [OE-core] " Alistair Francis
2025-12-30 14:15 ` [PATCH v2 02/15] linux-yocto: conditionally add clang/rust/bindgen-cli-native to DEPENDS Harish.Sadineni
2026-01-12 0:12 ` [OE-core] " Alistair Francis
2025-12-30 14:15 ` [PATCH v2 03/15] rust: install Rust library sources for 'make rustavailable' support Harish.Sadineni
2025-12-30 15:58 ` [OE-core] " Richard Purdie
2026-01-05 16:24 ` Harish Sadineni
2026-01-06 18:59 ` Randy MacLeod
2026-01-07 16:34 ` Harish Sadineni
2026-01-07 18:21 ` Randy MacLeod
2026-01-07 19:03 ` Richard Purdie [this message]
2026-01-12 0:42 ` Alistair Francis
2026-01-13 12:14 ` Harish Sadineni
2025-12-30 14:15 ` [PATCH v2 04/15] bitbake.conf: Include "rust-kernel" in native/nativesdk feature filters Harish.Sadineni
2025-12-30 14:15 ` [PATCH v2 05/15] kernel-yocto: enable Rust kernel support via rustavailable and staged rustlib sources Harish.Sadineni
2025-12-30 14:15 ` [PATCH v2 06/15] linux-yocto: enable Rust support in kernel configuration Harish.Sadineni
2025-12-30 14:15 ` [PATCH v2 07/15] kernel-yocto: Fix for buildpaths errors when rust is enabled for kernel Harish.Sadineni
2025-12-30 14:15 ` [PATCH v2 08/15] kernel-yocto.bbclass: Disable ccache when rust-kernel is enabled Harish.Sadineni
2026-01-14 15:41 ` alban.moizan
2025-12-30 14:15 ` [PATCH v2 09/15] kernel-devsrc: copying rust-kernel source to $kerneldir/build Harish.Sadineni
2025-12-30 14:15 ` [PATCH v2 10/15] selftest/cases/runtime_test: Add test for Linux Rust sample Harish.Sadineni
2026-01-05 9:32 ` [OE-core] " Mathieu Dubois-Briand
2026-01-08 9:39 ` Yoann Congal
2025-12-30 14:15 ` [PATCH v2 11/15] kernel.bbclass: Copy include/config/auto.conf in STAGING_KERNEL_BUILDDIR Harish.Sadineni
2025-12-30 14:15 ` [PATCH v2 12/15] kernel.bbclass: Export artifacts needed for out-of-tree Rust compilation Harish.Sadineni
2025-12-30 14:15 ` [PATCH v2 13/15] module.bbclass: Prepare out-of-tree rust module compilation Harish.Sadineni
2025-12-30 14:15 ` [PATCH v2 14/15] meta-skeleton: Add rust-out-of-tree-module recipe Harish.Sadineni
2025-12-30 14:15 ` [PATCH v2 15/15] runtime_test: Add rust-out-of-tree selftest Harish.Sadineni
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=1441d3bab7f90779a57c82e940369a8a6dd53786.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Harish.Sadineni@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=bruce.ashfield@gmail.com \
--cc=elmehdi.younes@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.com \
--cc=yoann.congal@smile.fr \
/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