From: Jacob Kroon <jacob.kroon@gmail.com>
To: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: How to skip building kernel modules
Date: Mon, 16 Mar 2020 10:05:49 +0100 [thread overview]
Message-ID: <74a48760-cfec-a2ff-e50b-ebd5d70ae8d8@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
Hi,
I'm using the linux-yocto kernel recipes together with additional kernel
config fragments that I append in our custom distro layer. All required
functionality is built into the kernel, so we don't install any kernel
modules on target.
What would be the correct way to save compilation time and skip
building/packaging the kernel modules ? Do I need to provide a custom
defconfig that explicitly disables all modules ?
I can monkey-patch oe-core with the attached patch in order to achieve
that goal, but I'm guessing something like this wouldn't be suitable for
upstreaming ?
Cheers,
Jacob
[-- Attachment #2: 0001-Handle-KERNEL_MODULES.patch --]
[-- Type: text/x-patch, Size: 1285 bytes --]
From: Jacob Kroon <jacob.kroon@gmail.com>
Date: Mon, 16 Mar 2020 09:47:58 +0100
Subject: [PATCH] Handle KERNEL_MODULES
---
meta/classes/kernel.bbclass | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index a724645466..538e769f89 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -329,7 +329,12 @@ kernel_do_compile() {
fi
}
+KERNEL_MODULES ?= "1"
+
do_compile_kernelmodules() {
+ if [ "${KERNEL_MODULES}" = "0" ]; then
+ exit 0
+ fi
unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS MACHINE
if (grep -q -i -e '^CONFIG_MODULES=y$' ${B}/.config); then
cc_extra=$(get_cc_option)
@@ -353,7 +358,7 @@ kernel_do_install() {
# First install the modules
#
unset CFLAGS CPPFLAGS CXXFLAGS LDFLAGS MACHINE
- if (grep -q -i -e '^CONFIG_MODULES=y$' .config); then
+ if [ "${KERNEL_MODULES}" = "1" ] && (grep -q -i -e '^CONFIG_MODULES=y$' .config); then
oe_runmake DEPMOD=echo MODLIB=${D}${nonarch_base_libdir}/modules/${KERNEL_VERSION} INSTALL_FW_PATH=${D}${nonarch_base_libdir}/firmware modules_install
rm "${D}${nonarch_base_libdir}/modules/${KERNEL_VERSION}/build"
rm "${D}${nonarch_base_libdir}/modules/${KERNEL_VERSION}/source"
next reply other threads:[~2020-03-16 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 9:05 Jacob Kroon [this message]
2020-03-16 9:12 ` How to skip building kernel modules Alexander Kanavin
2020-03-16 9:22 ` Jacob Kroon
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=74a48760-cfec-a2ff-e50b-ebd5d70ae8d8@gmail.com \
--to=jacob.kroon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox