On Thursday 12 June 2014 15:52:10 Patrick Doyle wrote:
Thanks.
bitbake foo | cat
is most likely to be what I was looking for. I found the cooker log
shortly after I asked my question. I'll go look through bitbake and
see what it would take to create a symbolic link to the most recent
I'm sure I'll get tired of looking at this eventually, and learn to
love the normal ncurses style interface of bitbake. But things are
still new enough to me that I want to know what's going on.
As you know, when we bitbake a recipe, we see lots of messages about
individual tasks that are run as
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
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…),
Thanks.
bitbake foo | cat
is most likely to be what I was looking for. I found the cooker log
shortly after I asked my question. I'll go look through bitbake and
see what it would take to create a symbolic link to the most recent
logfile, as is done with the logfiles for the individual tasks.
