| Summary: | Kernel not recreated with rootfs when bzImage missing | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Dave Stewart <david.c.stewart> |
| Component: | meta-yocto | Assignee: | Paul Eggleton <bluelightning> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | Medium | CC: | jessica.zhang, jiajun.xu, lianhao.lu, liping.ke, poky.bs.watcher, poky.watcher, sgw |
| Version: | 1.0 | ||
| Target Milestone: | 1.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | RFC patch posted to OE-core ml (17 Aug) | ||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 1346 | ||
|
Description
Dave Stewart
2011-08-02 14:31:48 UTC
This will happen regardless of how you initiate a build, not just with hob. This is expected behavior. Bitbake will only redeploy something if that thing has changed. You can't randomly delete things and have bitbake figure out what you deleted and what it needs to do to get it back... It did change... it was deleted. It's not unreasonable to expect that a user will delete files in this directory. In this case, if I want to rebuild the end product of the build, I would expect that I could just delete these end products and expect the build system to regenerate them. This is how "make" works, for example. How else would I force the the rootfs and kernel to be remade? If you remove random files from your windows system directory do you expect it still to work? The correct way to tell bitbake to rebuild something is to clean it (e.g. "bitbake virtual/kernel -c clean"). This is the one correct way to rebuild anything. The problem is we don't track the "output" of each task as whilst make and git can do this for projects of a certain size, we're talking about giagbytes of build data and we simply can't track that number of files and still respond to user requests in a timely fashion (have you seem how long a delete of a build takes? :( ). We could start special casing tasks but this then teaches the user that deleting files is ok. We'll then get the bug report that file X was changed of deleted and we didn't manage to detect that. I don't want give users the impression this is ok and instead I want to ensure we have consistency in the behavior. OK - Richard and I talked - this is definitely an area for potential confusion, but it sounds like it's hard to fix effectively in bitbake. So we agreed to two actions: 1. Let's put a file in the tmp/deploy/images directory when we create it which is named something like: "README - DO NOT DELETE FILES IN THIS DIRECTORY" and which contains instructions on what to do properly. 2. Add to the Quick Start Guide a warning similar to this when you describe the tmp/deploy/images content. Reclassifying this a medium priority and assigning to Paul. Feature has now been added in commit http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=333d571b360e112d7ade0b4ae3bacbda9c8b228d |