poky - Poky Build Tool and Metadata

Age	Commit message (Collapse)	Author
2011-11-27	bitbake: Update users of getVar/setVar to use the data store functions directly	Richard Purdie
	Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-11-25	bitbake: Update and fix bitbake-runtask	Robert Yang
	Since bitbake switched back to the fork instead of the exec model, it no longer used bitbake-runtask and the code has suffered some bitrot. bitbake-runtask is a useful tool for excuting the task without the scheduler of bitbake, so that the external tool can invoke it easily. It also provides a useful example of how to invoke exec_task() with low overhead without a lot of the bitbake threading/UI overhead. Significant changes: * This patch changes the argument order so that the commonly used and mandatory arguments come first. * The taskhash file and dryrun options are now optional * It now uses the bitbake logging mechanisms to provide processed logging output to the console. * The process handling to do with stdout/stderr redirection are removed since they're no longer required. [YOCTO #1229] RP: Logging updates to the patch based on Roberts original patch Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2010-12-10	bitbake/bitbake-runtask: Since the parent has set the environment up cleanly ↵	Richard Purdie
	we don't need to filter this ourselves anymore Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-12-09	bitbake: Overhaul environment handling	Richard Purdie
	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>
2010-10-14	bitbake-runtask: Ensure logging settings take effect in the worker process ↵	Richard Purdie
	(and pass verbose setting) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-10-11	bitbake-runtask: Ensure logging options are inherited from the parent	Richard Purdie
	[BUGID #291] Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-09-29	bitbake/bitbake-runtask: Signatures are needed in task context and have ↵	Richard Purdie
	little overhead so enable in worker context Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-09-28	bitbake: Pass task hash information to subprocesses	Richard Purdie
	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>
2010-09-13	bitbake/build.py: Set BB_FILENAME to represent the .bb file being built ↵	Richard Purdie
	(including any virtual prefix) Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-09-07	bitbake/bitbake-runtask: Ensure signals to the parent don't pass to the ↵	Richard Purdie
	children directly Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-08-20	bitbake: Correctly route events from the worker to the server	Richard Purdie
	Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
2010-08-19	bitbake: Switch to use subprocess for forking tasks and FAKEROOTENV to run ↵	Richard Purdie
	shell and python under a fakeroot environment Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>