Re: [docs] [PATCH] dev-manual: add command to force a recipe re-compile
"Robert P. J. Day" <[email protected]>
| Newsgroups | org.yoctoproject.lists.docs |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 10 Jun 2026, Alexander Kanavin wrote: > On Tue, 9 Jun 2026 at 21:20, Robert P. J. Day via > lists.yoctoproject.org <[email protected]> > wrote: > > --- a/documentation/dev-manual/temporary-source-code.rst > > +++ b/documentation/dev-manual/temporary-source-code.rst > > @@ -65,3 +65,11 @@ build system uses to build the package would be as follows:: > > > > project/build/tmp/work/qemux86-poky-linux/foo/1.3.0 > > > > +Finally, if you make some changes to a recipe's unpacked source code, > > +you can force a re-compile of that recipe with the command:: > > + > > + $ bitbake -c compile -f recipe-name > > + > > +The ``-f`` option in the above forces that task to be re-run > > +(invalidating any existing stamp file). > > + > > While explaining where to find the unpacked source is okay, taking it > further and providing a way to force-build it is not a good advice. If > someone needs to modify and build source like this, they should be > using 'devtool modify'. i actually thought about adding a link to devtool, along the lines of "while this technique works, devtool modify is now the recommended way" or something like that, at least as a historical reference for people who have been doing it the bitbake way all this time to let them know there's a better way. rday