Bitbake in server mode
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
Quoted 7 lines · Richard Purdie
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?
Quoted 7 lines
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.
I expect the obvious question to be, what happens if a recipe is altered between starting the server and running a command :)
Signature · 5 lines
Christopher Larson clarson at kergoth dot com Founder - BitBake, OpenEmbedded, OpenZaurus Maintainer - Tslib Senior Software Engineer, Mentor Graphics
Quoted 18 lines · Chris Larson
On Wed, Aug 21, 2013 at 7:26 AM, Richard Purdie
<[email protected]> wrote:
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!
Quoted 6 lines
We should be able to make bitbake in this mode much more responsive to
commands since there is no cache overhead.I expect the obvious question to be, what happens if a recipe is altered between starting the server and running a command :)
I should have been clearer, it will reparse, the normal cache checks take effect, it just doesn't have to unpickle cache bits from disk which is where the time is taken.
What happens if you edit recipes whilst bitbake is running a command? Do not do that, just like today!
Cheers,
Richard