[OE-core] [PATCH 0/9] Show progress during build and eSDK install

[Christopher Larson]

On Mon, Jun 13, 2016 at 8:47 AM, Randle, William C <
william.c.randle at intel.com> wrote:

> On Mon, 2016-06-13 at 15:13 +1200, Paul Eggleton wrote:
> >
> > I have contemplated and even prototyped going a step further and using
> the
> > count of lines in the output to track progress for *all* long-running
> tasks,
> > which does work reasonably well - the caveat is you actually need the
> > expected line count ahead of time for each task, so you have to be able
> to
> > get that from somewhere. I  haven't worked out a practical means of
> > delivering that, suggestions would be very much welcome - my prototype
> stuff
> > is on poky-contrib paule/progress-wip and relies on someone profiling a
> > build containing all the tasks beforehand and that information somehow
> being
> > made available to everyone else.
>
> Could this be done somewhat analagous to the way the sstate stuff works,
> in the
> sense you could specify a local or remote line count mirror, or use a local
> directory. The first time a unique task is run, the line count from the
> output
> is saved in the line count db. On subsequent runs, it would detect there's
> already an entry in the db and would be able to provide the progress
> report.
>
> Similar to the way an autobuilder can create a shared sstate mirror, when
> a task
> is run on an autobuilder, it could save the line count and make it
> available to
> other consumers, so on first run you would get a progress report, rather
> than
> having to bootstrap the line counts first.


I think if you want to do this, then we should do it in a generic way, to
store info of that sort from a build and use it as input to another build,
i.e. another sqlite3 db or something, as this isn't the only case where
build output could be used as hints for another build.
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20160613/b59ff74e/attachment-0002.html>