<div dir="ltr">Hi,<br><br>I am using bitbake to build images for a Gumstix.<br><br>Their setup has a .conf file that sets preferred versions for things like the kernel; I used this to choose a different version than standard, and this worked. Later, I wanted to switch back to the original version, but although the right version built, it was still pulling in modules from the other version.<br>
<br>Based on info on the web, etc, I tried forcing a rebuild of various tasks and the main image, to no avail, e.g.<br><br> bitbake -f -c clean task-base-gumstix <br> bitbake -f -c clean gumstix-basic-image<br><br> bitbake -f -c rebuild task-base-gumstix <br>
bitbake -f -c rebuild gumstix-basic-image<br><br>I ended up just using the sledgehammer and deleting the tmp directory... :(<br><br>My question is this: what is the correct principle to apply when rebuilding parts of an image?<br>
It seems that rebuilding at the top level won't necessarily rebuild stuff that has changed.<br>How can I know what to rebuild? Is there a way to rebuild everything above the toolchain (kernel, userspace, image)?<br>I don't have a good understanding of how this works so my solutions so far have been ad-hoc and trial and error.<br>
If someone could help me get the right model in mind, that would be great!<br><br>BTW, openembedded is a really nice system.. a bit of a learning curve though :)<br><br>Lewis<br></div>