| Summary: | Need dependencies from tasks on postprocessing variables | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Paul Eggleton <bluelightning> |
| Component: | core | Assignee: | Magnus Olsson <magnus> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | minor | ||
| Priority: | Medium | CC: | magnus, meta.mr.watcher, meta.watcher, richard.purdie |
| Version: | 1.6 | ||
| Target Milestone: | 1.8 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Paul Eggleton
2014-12-03 14:57:09 UTC
If you look at _depends_list() in lib/oe/rootfs.py, you'll see that at least some of these do have dependencies. We therefore need to figure out which ones are missing. Right, I'd completely missed that, and most of the variables I've listed (if not all, I haven't gone through and checked every one) seem to be covered by that mechanism, which suggests it may not be working according to the reports I have received. I've encountered issues where changes to IMAGE_PREPROCESS_COMMAND-functions does not trigger a rebuild.
IMAGE_PREPROCESS_COMMAND += "test; "
test() {
install -m 0755 ${DEPLOY_DIR_IMAGE}/${DTB_FILENAME} ${IMAGE_ROOTFS}
}
If test() is changed, Bitbake does not re-trigger build unless I explicitly taint the sstate-cache (-f).
After some digging, I can confirm that we do have code not only to add these variables (all of them) as dependencies of do_rootfs but also we get the functions as dependencies for the variables, so I think we do have the mechanism already as Richard pointed out. Magnus, I've tried the exact example you gave on both master and dizzy and haven't been able to reproduce the issue - changing the contents of the function causes do_rootfs to re-execute the next time I build the image. Is there something else going on in your setup that I'm not replicating? |