From: Mark Hatle <mark.hatle@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: Re: Display mode
Date: Tue, 22 Jan 2013 10:47:58 -0600 [thread overview]
Message-ID: <50FEC2BE.3020902@windriver.com> (raw)
In-Reply-To: <CAHUNapSSaOqnkOZq3_BaMthqY6hG+JTxvi9XpgD_38yT6+wDhA@mail.gmail.com>
On 1/22/13 10:37 AM, Trevor Woerner wrote:
> On Tue, Jan 22, 2013 at 1:20 AM, Trung Hoang <trungiee@gmail.com> wrote:
>> The current git HEAD of bit bake nicely displays the x threads and what is happening on them instead of constantly scrolling in detail what is exactly happening.
>
> This feature is called "knotty".
>
>> Is this feature configurable? How do i enable it on older versions of bitbake? As the gumstix setup scripts check out a older version of bit bake and it displays reams and reams of info.
>
> Knotty was added this past... August (?) (or, perhaps it is more
> correct to say "it was made the default" this past August?). So making
> it work on older versions would require back-porting it to those
> versions.
"In general", newer versions of bitbake work with older systems. There is one
main condition where this can be problematic however. There was a period of
time where, in python functions, tabs were all converted to spaces. So code is
in bitbake to check for this condition.
If you try to use a modern bitbake with an older system that still has tabs, you
can get failures.
Note, it does require testing to verify that the newer bitbake will work on an
older configuration, but it has in my experience.
--Mark
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/bitbake-devel
>
next prev parent reply other threads:[~2013-01-22 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 6:20 Display mode Trung Hoang
2013-01-22 16:37 ` Trevor Woerner
2013-01-22 16:41 ` Chris Larson
2013-01-22 17:34 ` Trevor Woerner
2013-01-22 16:47 ` Mark Hatle [this message]
2013-01-22 22:21 ` Trung Hoang
2013-01-23 12:13 ` Jason Wessel
2013-01-23 15:20 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50FEC2BE.3020902@windriver.com \
--to=mark.hatle@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.