On Wed, 2013-08-21 at 08:56 -0700, Chris Larson wrote: > > 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! > > 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 _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
