[bitbake-devel] Lifecycle issues in Bitbake
clarson at kergoth.com
Thu Jan 22 16:39:15 UTC 2015
On Thu, Jan 22, 2015 at 7:57 AM, Richard Purdie <
richard.purdie at linuxfoundation.org> wrote:
> Looking at and thinking about:
> We have several issues. Firstly, DATE and TIME are locked in stone when
> the base configuration is parsed. This may cause images to overwrite
> previous versions for example if DATE and TIME are not re-evaluated. We
> could fix this by specifically setting DATE and TIME in bitbake at
Seems quite reasonable to me.
Secondly, there is one cooker log file opened for the duration of the
> cooker lifecycle. This is a cooker log, not a log of each build so that
> is perhaps not surprising (and is the core problem in the above bug).
> There is no overwriting of the log file, it just keeps growing with each
> We could trigger knotty to write out build specific log files based on
> the BuildStart/Finish events?
This doesn't seem unreasonable, though a build isn't necessarily bound to a
particular UI, is it? Should that go into the server or perhaps the ui
helper at least? Hmm.
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bitbake-devel