From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] bitbake: added -j option
Date: Mon, 21 May 2012 15:07:23 +0100 [thread overview]
Message-ID: <1337609243.22747.4.camel@ted> (raw)
In-Reply-To: <1337527267-2196-1-git-send-email-enrico.scholz@sigma-chemnitz.de>
On Sun, 2012-05-20 at 17:21 +0200, Enrico Scholz wrote:
> This patch adds an -j option which overrides/sets BB_NUMBER_THREADS.
> For some use cases like '-c fetchall' it might be useful to modify
> temporarily the number of parallel running tasks without editing
> bitbake.conf.
>
> Signed-off-by: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
> ---
> bin/bitbake | 4 ++++
> doc/bitbake.1 | 4 ++++
> lib/bb/cooker.py | 7 +++++++
> 3 files changed, 15 insertions(+), 0 deletions(-)
>
> diff --git a/bin/bitbake b/bin/bitbake
> index 478ac06..b29fae9 100755
> --- a/bin/bitbake
> +++ b/bin/bitbake
> @@ -171,6 +171,10 @@ Default BBFILES are the .bb files in the current directory.""")
>
> parser.add_option("-B", "--bind", help = "The name/address for the bitbake server to bind to",
> action = "store", dest = "bind", default = False)
> +
> + parser.add_option("-j", "--jobs", help = "The number of threads BitBake should run at once",
> + action = "store", dest = "number_threads", default = None)
> +
> options, args = parser.parse_args(sys.argv)
>
> configuration = BBConfiguration(options)
I think in this case you may as well just whitelist BB_NUMBER_THREADS
from the environment and set that variable there. I'm not seeing a huge
need for the specific commandline option...
Cheers,
Richard
next prev parent reply other threads:[~2012-05-21 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-20 15:21 [PATCH] bitbake: added -j option Enrico Scholz
2012-05-21 14:07 ` Richard Purdie [this message]
2012-05-21 14:13 ` Peter Seebach
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=1337609243.22747.4.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=enrico.scholz@sigma-chemnitz.de \
/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.