openembedded-core.git/bitbake, branch master

bitbake: Remove the remaining files that came in with merge from yocto

2011-03-01T21:38:54Z

Signed-off-by: Khem Raj

bitbake/hob: only show one progress dialog when changing machine

2011-03-01T11:46:46Z

Remove a spurious signal emission which resulted in two progress dialogs being shown after changing the machine. Signed-off-by: Joshua Lock

bitbake: Add new UI hob, a prototype Gtk+ GUI for creating images

2011-03-01T11:46:34Z

Hob is a first stab at implementing an interactive GUI for BitBake. Signed-off-by: Joshua Lock

bitbake: introduce crumbs.TaskListModel a gtk.ListStore subclass

2011-03-01T11:46:24Z

Provide a gtk.ListStore subclass which includes a function, populate(), which takes as input the data emitted by bb.event.TargetsTreeGenerated and fills the ListStore model appropriately. Furthermore convenience functions are provided by which the caller can get gtk.TreeModel subclasses which provide filtered views of the data. Signed-off-by: Joshua Lock

bitbake: Remove in-tree version

2011-02-23T18:48:51Z

Bitbake should be used by checking it out from its own repo Signed-off-by: Khem Raj

bitbake/build.py: Fix TaskFailed parameters

2011-02-23T15:06:34Z

Signed-off-by: Richard Purdie

bitbake/data_smart: Improve Variable expansion error handling

2011-02-23T13:13:31Z

If expanding a variable triggers an exception the caller currently has no way to supress the error message or otherwise handle the siutation. An example of where this is a problem is "bitbake -e" showing tracebacks and errors for variables like SRCPV in OE/Poky. Secondly in a chained expansion fails, log mesages are recorded for every step of the expansion, not just the innermost error which is where the real failure occured. To fix this we introduce a new exception ExpansionError which callers can handle as appropriate. Signed-off-by: Richard Purdie

bitbake/data_smart: Improve the way lazyassignment works

2011-02-23T11:48:01Z

Currently, if a variable has been set with ??= and the code looks it up before the data finalisation phase, no value is found. This is causes serious problems for anonymous python functions which manipulate data, or for the fetcher revision handling code where revisions can be set with ??=. There is also a significant performance implication for processing lazy assignment in finalise. Moving the check for a default value into getVarFlag addresses both the timing issue and the performace. This change gives a 7% real time performance improvement to parsing the Poky metadata. The cost of the check at this point is minimal since we have all the data flags available. This should also fix Yocto bug 752. Signed-off-by: Richard Purdie

bitbake/fetch2: Ensure SRCREV_pn-PN is checked for a revision when the SRC_URI is unnamed

2011-02-23T11:47:50Z

Signed-off-by: Richard Purdie

bitbake/cooker: Fix parsing failure zombie problem

2011-02-23T11:09:07Z

When parsing if a SystemExit event is triggered, it causes the parsing thread to exit and the main process hangs waiting for it to finish indefintely. Add code to catch BaseExceptions and raise these with the main process gracefully instead of just hanging indefinitely with zombie processes. Signed-off-by: Richard Purdie