openembedded-core.git/bitbake/bin/bitbake-runtask, branch masterhttps://trygvis.io/git/2012/05/openembedded-core.git/atom?h=master2011-02-23T18:48:51Zbitbake: Remove in-tree version2011-02-23T18:48:51ZKhem Rajraj.khem@gmail.com2011-02-23T18:48:51Zurn:sha1:951cbf3f65f347c7a7bbcae193218f9187a15fbf
Bitbake should be used by checking it out from its own repo
Signed-off-by: Khem Raj <raj.khem@gmail.com>
bitbake/bitbake-runtask: Since the parent has set the environment up cleanly we don't need to filter this ourselves anymore2010-12-10T12:40:23ZRichard Purdierpurdie@linux.intel.com2010-12-10T12:40:23Zurn:sha1:c47cfc56c779304a575507793618dccad178432f
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake: Overhaul environment handling2010-12-09T13:16:14ZRichard Purdierpurdie@linux.intel.com2010-11-28T17:39:09Zurn:sha1:0ba9a9fffee966ec912eec5fd52c468338560e6a
Currently, anything whitelisted in the environment makes it into the worker
processes. This is undesireable and the worker environment should be as
clean as possible. This patch adapts bitbake sosme variables are loaded into
bitbake's datastore but not exported by default. Any variable can be exported
by setting its export flag.
Currently, this code only finalises the environment in he worker as doing so
in the server means variables are unavailable in the worker. If we switch
back to fork() calls instead of exec() this code will need revisting.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake-runtask: Ensure logging settings take effect in the worker process (and pass verbose setting)2010-10-14T19:07:15ZRichard Purdierpurdie@linux.intel.com2010-10-12T16:46:47Zurn:sha1:229b6630af72f2914d75ab6b0ba081b5feb25172
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake-runtask: Ensure logging options are inherited from the parent2010-10-11T11:52:57ZRichard Purdierpurdie@linux.intel.com2010-10-11T11:52:57Zurn:sha1:ff539b11acca9831b72f3bc951a6ef20cd293786
[BUGID #291]
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake/bitbake-runtask: Signatures are needed in task context and have little overhead so enable in worker context2010-09-29T11:12:26ZRichard Purdierpurdie@linux.intel.com2010-09-29T10:25:10Zurn:sha1:624924bdcde0d1c7a6d2b68d860ff0d81de62729
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake: Pass task hash information to subprocesses2010-09-28T14:34:27ZRichard Purdierpurdie@linux.intel.com2010-09-27T14:57:13Zurn:sha1:ec4d6b989aad5f4564e367c99c62c59f962b57ea
Pass task has informaiton to work processes, allowing full manipulation of
the hash data in the task context allowing checksums to be usable.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake/build.py: Set BB_FILENAME to represent the .bb file being built (including any virtual prefix)2010-09-13T14:39:07ZRichard Purdierpurdie@linux.intel.com2010-09-13T14:39:07Zurn:sha1:89c72609311c18045e47822649fbcc25099e4860
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake/bitbake-runtask: Ensure signals to the parent don't pass to the children directly2010-09-07T22:54:15ZRichard Purdierpurdie@linux.intel.com2010-09-07T22:54:15Zurn:sha1:7b580b488cb60ce4166ef2539496e83385779aa7
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake: Correctly route events from the worker to the server2010-08-20T11:26:19ZRichard Purdierpurdie@linux.intel.com2010-08-20T11:25:19Zurn:sha1:616e75523b0b1bbe730631dba70224b55cfaaa57
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>