Re: Changing external kernel module results in rebuild of whole kernel

[Mike Looijmans <mike.looijmans@topic.nl>]

Just tried that. Change the SRCREV of the module, and ran
bitbake-whatchanged kernel-module-dyplo

Then it claims nothing changed:
$ bitbake-whatchanged kernel-module-dyplo
Figuring out the STAMPS_DIR ...
Generating the new stamps ... (need several minutes)

=== Summary: (0 changed, 0 unchanged)
Newly added: 0
PV changed: 0
PR changed: 0
Dependencies changed: 0


But if I run bitbake -n kernel-module-dyplo, it really wants to rebuild the 
kernel and module.

I'm merged oe-core master last monday, so it's pretty recent.


On 06-05-15 12:35, Burton, Ross wrote:
>
> On 6 May 2015 at 07:35, Mike Looijmans <mike.looijmans@topic.nl
> <mailto:mike.looijmans@topic.nl>> wrote:
>
>     If I change a recipe for a kernel module (a bb recipe that does "inherit
>     module") this will trigger a rebuild of the whole kernel.
>
>
> You can start to debug this by using bitbake-whatchanged. Build the kernel and
> modules, make a minor change to the module recipe, and then run
> "bitbake-whatchanged virtual/kernel" or some relevant target.
>
> Ross



Kind regards,

Mike Looijmans
System Expert

TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
Telefax: +31 (0) 499 33 69 70
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com

Please consider the environment before printing this e-mail