linux/poky.git/bitbake/bin, branch 1.5_M4.rc2

bitbake: bitbake-worker: import needed signal module

2013-07-31T05:59:59+00:00

bitbake-worker makes use of the signal module but it doesn't import it. This patch fixes the issue. [YOCTO #4750] (Bitbake rev: c2ed639690f135994199eb24d964e37f57259e3a) Signed-off-by: Valentin Popa Signed-off-by: Richard Purdie

bitbake: bitbake: read BBSERVER environement for remote server

2013-06-17T15:09:10+00:00

This change allows bitbake to connect to a remote server by reading the BBSERVER environment variable and effecting the config. Basically a shortcut to the command line parameters. (Bitbake rev: 81929f86c57ed0a4ad0cda7aaa820fceabaa61e9) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: knotty, bitbake: add option to terminate a remote server

2013-06-17T15:09:10+00:00

I add an option to terminate a remote server gracefully as not to need a kill command. (Bitbake rev: 7495f835666a9561c2c7d84da7aaa74e4df55b9a) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: knotty, xmlrpc: add observer-only mode

2013-06-17T15:09:10+00:00

I add an observer only mode for the knotty UI and the XMLRPC server that will allow the UI to register a callback with a server in order to receive events. The observer-UI is able to send read-only commands to the server, and also is able to register as an event handler. Read-only commands are the commands that do not change the state of the server and have been marked as such in the command module. The observer can switch to a full client if it calls addClient at any time, and the server has no other client running. (Bitbake rev: 4de9ee21f1fa4d04937cc7430fb1fc8b7a8f61e2) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: bitbake: Update version to 1.19.1

2013-06-14T11:52:58+00:00

(Bitbake rev: 6acd444a557bba977ae1772371fdadf5f510e3b6) Signed-off-by: Richard Purdie

bitbake: prserv: Adapt autostart to bitbake-worker

2013-06-14T11:52:57+00:00

With the change to bitbake-worker we need to ensure the workers know how to contact the PR service, the magic 0 port and singleton is no longer enough. (Bitbake rev: c761751e259bb8e940552a28794b45887b5a72d9) Signed-off-by: Richard Purdie

bitbake: runqueue: Split runqueue to use bitbake-worker

2013-06-14T11:52:56+00:00

This is a pretty fundamental change to the way bitbake operates. It splits out the task execution part of runqueue into a completely separately exec'd process called bitbake-worker. This means that the separate process has to build its own datastore and that configuration needs to be passed from the cooker over to the bitbake worker process. Known issues: * Hob is broken with this patch since it writes to the configuration and that configuration isn't preserved in bitbake-worker. * We create a worker for setscene, then a new worker for the main task execution. This is wasteful but shouldn't be hard to fix. * We probably send too much data over to bitbake-worker, need to see if we can streamline it. These are issues which will be followed up in subsequent patches. This patch sets the groundwork for the removal of the double bitbake execution for psuedo which will be in a follow on patch. (Bitbake rev: b2e26f1db28d74f2dd9df8ab4ed3b472503b9a5c) Signed-off-by: Richard Purdie

bitbake: bitbake-layers: fix for move of data object to cooker

2013-06-10T09:32:58+00:00

(Bitbake rev: 063ee01935767ac4c9518d7477c8c85da1c9969a) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: bitbake: Improve remote server handling

2013-06-07T13:13:18+00:00

Two fixes in bitbake related to running remote servers - * can now specify correctly the bind port * the information in print conforms to common server infrastructure (Bitbake rev: b657208ee15ae065e5fcc2dd6e0051e03d246727) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

bitbake: Drop bitbake-runtask (removed upstream a while ago)

2013-06-04T10:54:23+00:00

Signed-off-by: Richard Purdie