On Thu, Jun 12, 2014 at 12:00 PM, Burton, Ross <ross.bur...@intel.com> wrote:
> On 12 June 2014 19:53, Patrick Doyle <wpds...@gmail.com> wrote: > > As you know, when we bitbake a recipe, we see lots of messages about > > individual tasks that are run as they are being run (do_fetch, > > do_configure, etc…), and then a final summary message that reads > > something like: > > > > NOTE: Tasks Summary: Attempted 690 tasks of which 677 didn't need to > > be rerun and all succeeded. > > > > I'm curious: > > 1) What were the 13 tasks that ran? > > 2) Why are there 690 tasks for my simple recipe anyway? > > You want to see the cooker log. > > If you want to see that as it happens, then for a one-off you can > convince bitbake that it's not running on a vt (bitbake foo | cat -). > > After the event, the cooker logs are in > tmp/logs/cooker/[machine]/[timestamp].log. For convenience, Chris > Larson's excellent 'bb' command has a 'log' mode that if given no > arguments will display the latest cooker log. The new Toaster is pretty great at examining what your build did, if you ran your build in toaster context, afaik. I haven't spent much time playing with it, but it does seem like it's intended to answer just these sort of questions. -- Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
