From 3805a1837a8f02b42ca815244c1146cdf583b980 Mon Sep 17 00:00:00 2001 From: Ciro Santilli Date: Thu, 13 Sep 2018 21:10:18 +0100 Subject: [PATCH] why you need to request rebuild explicitly --- README.adoc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.adoc b/README.adoc index a7b36ad..7dea07c 100644 --- a/README.adoc +++ b/README.adoc @@ -234,6 +234,8 @@ Congratulations, you are now officially a kernel module hacker! We use `./build-buildroot` here because kernel modules go into the root filesystem, and it is Buildroot that generates our root filesystem. The kernel modules are inside a Buildroot package. +`--kernel-modules` is required even if files were modified as explained at: <>. + The reboot after rebuild is annoying. We don't have a perfect solution for it yet, but there are some ideas cooking at: <>. Not satisfied with kernel modules? OK then, let's hack up the <> Linux kernel itself. @@ -9082,6 +9084,12 @@ Since rebuilding this package is such a common case, we have a shortcut for it: ./build-buildroot --kernel-modules .... +The rebuild must be requested explicitly, otherwise the package does not rebuild, even if its files were modified. + +This is because Buildroot builds dozens of packages, and just reading there Makefiles and checking the stamps generates too much overhead + +So you must tell Buildroot yourself about the rebuild. + === Custom Buildroot configs We provide the following mechanisms: