Bug 5556 - A way to force all the recipes rebuild
Summary: A way to force all the recipes rebuild
Status: RESOLVED WONTFIX
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.6
Hardware: x86 Multiple
: Undecided enhancement
Target Milestone: 1.6 M4
Assignee: Robert Yang
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-11-19 07:30 UTC by Robert Yang
Modified: 2013-11-21 15:43 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Yes (doc changes required)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Yang 2013-11-19 07:30:27 UTC
We usually meet that the recipe is failed when rebuild it, we can figure out a way to rebuild all the recipes once to check such failures, for example:

bitbake world -crebuild

Then all the world recipes will be rebuilt.

Or we can edit some config files, env, and so on, it should be an official UI/API.
Comment 1 Robert Yang 2013-11-19 08:28:12 UTC
We need be able to rebuild only one or all, for example:

bitbake zlib -crebuild

will only rebuild zlib, it is useful when we modified the source in ${S} and build it for development/testing, and:

bitbake zlib -crebuild_all

will rebuild all the dependencies recipes, including the native ones.
Comment 2 Paul Eggleton 2013-11-20 12:13:58 UTC
Surely this is already easily accomplished by deleting TMPDIR and SSTATE_DIR or moving them out of the way before building world?
Comment 3 Richard Purdie 2013-11-21 15:43:44 UTC
We have the clean* targets and the -C and -f options as well as --no-setscene so I don't believe adding in extra duplicate API is a good thing.