From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Brandon Maier" <brandon.maier@collins.com>
Cc: "Michaelis,
Adam J Collins via buildroot" <buildroot@buildroot.org>,
"Michaelis, Adam J Collins" <adam.michaelis@collins.com>,
"Buchmeyer, Neal Collins" <Neal.Buchmeyer@collins.com>,
"Julien Olivain" <ju.o@free.fr>,
"Romain Naour" <romain.naour@smile.fr>
Subject: Re: [Buildroot] [PATCH v2 1/1] linux: Install artifacts to staging for kmod build
Date: Tue, 22 Oct 2024 22:23:09 +0200 [thread overview]
Message-ID: <20241022222309.06d64ebe@windsurf> (raw)
In-Reply-To: <D52LZL79C2WS.1LHI702Z0GTIY@collins.com>
On Tue, 22 Oct 2024 20:14:54 +0000
"Brandon Maier" <brandon.maier@collins.com> wrote:
> > I am actually wondering whether this should be an option. We don't have
> > any similar option for any other package.
>
> I think the main advantage to being an option is to keep the size of the
> SDK down. This installs a large amount of the kernel source code which
> appears to be hundreds of MBs.
Then probably there is too much stuff getting copied. I think "all"
what's needed are the configured headers + some bits of the build
system.
> I looked around a bit in the kernel and couldn't find anything.
>
> I checked a few distro packages and they all seem to be variants of
> this. See the following
>
> Arch: https://gitlab.archlinux.org/archlinux/packaging/packages/linux/-/blob/main/PKGBUILD?ref_type=heads#L133
> Fedora: https://src.fedoraproject.org/rpms/kernel/blob/rawhide/f/kernel.spec#_3507
> Yocto: https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-kernel/linux/kernel-devsrc.bb#L37
Wargh, I just looked at the Yocto one, and it's awful.
What's your use case for wanting to build out of tree modules with the
SDK ? :-)
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-22 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 16:06 [Buildroot] [PATCH v2 1/1] linux: Install artifacts to staging for kmod build Michaelis, Adam J Collins via buildroot
2024-10-22 19:24 ` Thomas Petazzoni via buildroot
2024-10-22 20:14 ` Brandon Maier via buildroot
2024-10-22 20:23 ` Thomas Petazzoni via buildroot [this message]
2024-10-22 21:08 ` [Buildroot] [External] " Michaelis, Adam J Collins via buildroot
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=20241022222309.06d64ebe@windsurf \
--to=buildroot@buildroot.org \
--cc=Neal.Buchmeyer@collins.com \
--cc=adam.michaelis@collins.com \
--cc=brandon.maier@collins.com \
--cc=ju.o@free.fr \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
/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