linux/poky.git/bitbake/bin, branch 1.3_M3.final

bitbake: bitbake-layers: fix help for show-overlayed to match behaviour

2012-08-02T16:05:06+00:00

show-overlayed actually lists the same recipe in multiple layers regardless of priority, so change the help description to match. (Bitbake rev: 17217ff707e41780cb473b9cdd2621dd18b982c2) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: Update version to 1.15.3

2012-07-19T09:24:50+00:00

(Bitbake rev: befbb5c9428eaf98b2ff9c4b36b0b3f2dce7fe07) Signed-off-by: Richard Purdie

bitbake: bitbake/cooker: Print which pkgs would be built in -g output

2012-07-09T16:19:32+00:00

This is for giving the user a clear list to show which pkg would be built, we have the "bitbake -g", but it is not easy to read for people, it is for "dot". Improve the "bitbake -g" to also save a pn-buildlist: $ bitbake -g core-image-sato ... NOTE: PN build list saved to 'pn-buildlist' [snip] The contents of pn-buildlist: busybox shadow-native pth sysfsutils qemu-helper-native curl-native ncurses-native gdbm xserver-xorg linux-libc-headers [snip] [YOCTO #2404] (Bitbake rev: 18aff925aece774d0172894e25584353519ca03f) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

bitbake: bitbake: tweak help text for -C slightly

2012-06-25T13:57:15+00:00

What is specified is a command (or "cmd" as in the help text for -f) rather than a task - i.e. you specify compile, not do_compile, so change the sentence to reflect that and reorder it slightly so it makes sense. (Bitbake rev: 9ab269410ef5cd4753fe11ec74759f421685bb7b) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake: bitbake: add -C option to invalidate a task and rebuild the target

2012-06-21T12:10:32+00:00

This new command line option forces the specified task and all dependent tasks up to the default task to re-run. This means that the following single step: bitbake -C compile somerecipe is equivalent to the following two steps (with the recent change to -f): bitbake -c compile -f somerecipe bitbake somerecipe Note that to work this option needs full hashing enabled (i.e. BB_SIGNATURE_HANDLER must be set to a signature handler that inherits from BasicHash). If this is not the case, -C effectively does nothing. Based on a previous implementation of this option by Jason Wessel . Implements [YOCTO #2615]. (Bitbake rev: 2530e0faada5775897cfd1b93aba6925826dca73) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

image-writer: tweak some strings

2012-06-14T13:07:17+00:00

Tweak some strings in accord with the script name 'image writer', and remove extra noun 'button'. (Bitbake rev: d2d65335e8fc2417ebd3910f645cc00a4abfbeaa) Signed-off-by: Kang Kai Signed-off-by: Richard Purdie

hob2: create a standalone deploy image tool

2012-06-08T11:13:43+00:00

[Yocto 2388] Create a deploy image tool using the existing dialog including DeployImageDialog and ImageSelectionDialog. This tool writes bootable images to USB devices, and it can be run directly without hob. Signed-off-by: Kang Kai Signed-off-by: Richard Purdie

bitbake: support $BITBAKE_UI environment

2012-05-23T10:35:11+00:00

Patch adds support for a $BITBAKE_UI environment variable which allows to configure the preferred user interface. Although an '-u' option (which will override the environment variable) exists already, it was required to specify this option on every invocation of bitbake. Because user interface is instanciated very early in the program it is not possible to use bitbake.conf for setting up a default. An environment variable (which acts in a similar category like $PAGER or $EDITOR) is a simple way for configuring the default. (Bitbake rev: e3c213015953d1a0afb5ef4be59e1264990e5cee) Signed-off-by: Enrico Scholz Signed-off-by: Richard Purdie

bitbake: Fixup bitbake-selftest

2012-05-04T16:41:47+00:00

Signed-off-by: Richard Purdie

bitbake: Add start of bitbake regression/self testing

2012-05-04T15:58:35+00:00

This adds some basic unit testing for the codeparser and data store code. Many of the actual test cases were taken from work by Chris Larson's OE-Signatures work but with changes to adapt to the current bitbake APIs we need to test. I also imported CoW tests written by Holger Freyther from the original bitbake-test codebase: http://svn.berlios.de/wsvn/bitbake/trunk/bitbake-tests/tests/ and some tests from the doctests that were removed in commit: http://git.openembedded.org/bitbake/commit?id=3a11c2807972bbbddffde2fa67fc380d159da467 (Bitbake rev: ae4a95780e3e08cf73c854efa8cd93379e00c4e5) Signed-off-by: Richard Purdie