Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bitbake-devel <bitbake-devel@lists.openembedded.org>
Cc: poky <poky@lists.yoctoproject.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Bitbake in server mode
Date: Wed, 21 Aug 2013 15:26:25 +0100	[thread overview]
Message-ID: <1377095185.25999.116.camel@ted> (raw)

I've just realised that we have some new functionality that has sneaked
in but most people are unaware of. You can now run bitbake as a server
in the background and then just connect the knotty UI to it with
commands. The usage is:

bitbake --server-only -t xmlrpc -B localhost:1234

which starts a server on localhost port 1234 and then you can run
commands with:

BBSERVER=localhost:1234 bitbake <somecommand>

and 

BBSERVER=localhost:1234 bitbake -m

to shut it down.

Known issues:

a) Parsing is slower. Probably due to all the debug messages going over
the IPC/xmlrpc. UI event filtering should fix it.
b) Something is causing a cache reparse initially. Need to figure out
what. Maybe the BBSERVER variable itself?

This is still development so I'd not recommend everyone use this for
production just yet but it gives some nice insight into what the future
holds!

We should be able to make bitbake in this mode much more responsive to
commands since there is no cache overhead.

Cheers,

Richard



             reply	other threads:[~2013-08-21 14:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-21 14:26 Richard Purdie [this message]
2013-08-21 15:56 ` [bitbake-devel] Bitbake in server mode Chris Larson
2013-08-21 16:19   ` 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=1377095185.25999.116.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=poky@lists.yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox