| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
means selective proxying isn't possible
|
|
|
|
| |
attempts and make the 'continue' more aggresive
|
|
|
|
|
|
| |
The UI starter now dynamically searches for the UI module based on the
parameter given to -u. bitbake advertises the dependency explorer as "depexp"
therefore this module needs renaming.
|
|
|
|
|
|
|
| |
Since the default task is not known/available until the configuration files
are parsed we may return None when the UI requests getCmdLine. We can enforce
the use of the default by querying it again after the configuration is
parsed/cache updated.
|
|
|
|
|
|
|
|
| |
Separate the parsing of the configuration files / recipes into a separate
function to the parsing of the command line. This parsing of the configuration
files now happens when updateCache() is called.
Some functionality has been moved from parseConfiguration() to __init__.
|
|
|
|
|
|
| |
The shell updated the self.configuration.cmd variable since commans relied on
this implicit state. Since those commands now have an explicit task parameter
such state manipulation is no longer necessary.
|
|
|
|
|
| |
Remove the implicit (from configuration.cmd) command/task for these events and
instead use a parameter so that the task is given explicitly.
|
|
|
|
|
| |
The "buildFile" command has a task parameter use it place of
self.configuration.cmd when adding to the runqueue.
|
|
|
|
|
| |
And switch the runqueue to use this rather than keeping it in the
self.configuration.cmd variable
|
|
|
|
|
| |
This allows a UI to read / control which task for the given targets is used.
This makes it more consistent with the "buildFile" command.
|
| |
|
|
|
|
|
| |
This is synonymous with the getVariable command and allows you to set values
in the data dictionary.
|
|
|
|
|
| |
Changing the name of this command makes it more consistent with other command
names.
|
|
|
|
|
|
| |
Change the terminology from online/offline to sync/async when referring to
commands that return a result immediately versus those that produce changes
that are emitted as events over time.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
When the runqueue forks off we save the pid inside the event module for that
thread. When we next fire an event then that PID gets included in the events.
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5551 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
|
|
|
|
| |
handling in the UI
These events are superfluous now that BB operates on a task level granularity.
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5541 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5534 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5529 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
|
|
|
|
| |
Do not clear the environment when saving the environment to the data store.
Instead clear this once the cooker has forked. This ensures that the UI
operates in a filtered (but not empty) environment.
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5526 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5453 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5416 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5415 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5402 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5368 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5362 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
|
|
| |
cache the recipe. Based on work from Heikki Paajanen
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5352 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5351 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5349 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
|
|
| |
bitbake from the environment
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5347 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5346 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
|
|
|
| |
Update bitbake-dev to have extra fixes from Poky's internal (1.8) version of bitbake.
Should be able to use bitbake-dev with Poky now.
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5340 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
|
|
| |
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5339 311d38ba-8fff-0310-9ca6-ca027cbcb966
|
|
git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5337 311d38ba-8fff-0310-9ca6-ca027cbcb966
|