summaryrefslogtreecommitdiffstats
path: root/bitbake/bin
Commit message (Collapse)AuthorAgeFilesLines
* bitbake: bin/bitbake: Ensure early errors are shown to the userRichard Purdie2013-05-091-5/+16
| | | | | | | | | | Currently if errors occur early in the init process, the errors may not be shown to the user. This change ensures that if a failure does occur, the messages are flushed from the queue and shown to the user. (Bitbake rev: fda84c4285e0bc31c249b6dd5464aeb6ad622a9a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: remove stack trace depth limitationBogdan Marinescu2013-05-031-1/+1
| | | | | | | | | | | | In case of an error in bitbake, the stack trace is limited to 5 items. This is an endless source of confusion and it makes bugs reports impractical, since a full stack trace can't be included in the bug report. This patch simply removes the depth limit. (Bitbake rev: 02629c42fb09413d9da16cfe43e03338ce7db3ff) Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update to version 1.19.0 for masterRichard Purdie2013-05-031-1/+1
| | | | | | (Bitbake rev: c47088a86fd8ad06c1810d04d9537c4cd01e8bef) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update to version 1.18.0Richard Purdie2013-04-101-1/+1
| | | | | | (Bitbake rev: 94b54788cadabf6ebfb7711674646dbea6204805) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-layers: fix duplicated help infoRobert Yang2013-03-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | There are two "help" lines when run bitbake help under python 2.6.6 (perhaps all python 2.6): $ bitbake-layers help [snip] help display general help or help on a specified command [snip] help display general help or help on a specified command This is because the cmd.py in python 2.6.6 also has a do_help() function as our bitbake-layers, and the cmd.Cmd.get_names() doesn't consider the overload, this has been fixed in python 2.7, use set() to remove the duplicated would fix the problem. [YOCTO #3428] (Bitbake rev: 324ed96e28ec31cff8cef1824d20d40f9a5d46ad) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-layers: make show-cross-depends avoid long pathRobert Yang2013-02-151-8/+48
| | | | | | | | | | | | | | | | | | | | | | | | | The "bitbake-layers show-cross-depends" print the absolute path in the past, now it will print the relative path (relative to the layer dir) by default, and add the "-f" option to make it print the absolute path. For example: $ bitbake-layers show-cross-depends [snip] meta-intel/meta-jasperforest/conf/machine/jasperforest.conf requires meta/conf/machine/include/ia32-base.inc [snip] $ bitbake-layers show-cross-depends -f [snip] /path/to/poky/meta-intel/meta-jasperforest/conf/machine/jasperforest.conf requires /path/to/poky/meta/conf/machine/include/ia32-base.inc [snip] [YOCTO #3824] (Bitbake rev: df217701318d60559be0b10214b883b8ce4f5d2a) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake/utils: Improve environment handling to allow UIs access to ↵Richard Purdie2013-02-111-4/+6
| | | | | | | | | | | | | | | | original environment We need to empty out the environment whilst we build the cooker but we need the environment for the UIs since hob uses DISPLAY and other session variables. This patch adapts the utils functions to return removed environment components so we can reinject them for use by the UI, allowing hob to work again. (Bitbake rev: fc330d810099c57fefd4e706159a73ad8401d97c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update version to 1.17.0Richard Purdie2013-02-061-1/+1
| | | | | | (Bitbake rev: d96ef9398356b2a61f7cff765821616bf1e55492) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-layers: print the recipe's depends that crosses a layer ↵Robert Yang2013-01-311-0/+133
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | boundary Figure out the dependency between recipes that crosses a layer boundary * Introduction: - For the .bb file, we need check the following depends: > Check the DEPENDS, RDEPENDS and inherits according to the cooker_data. > The cooker_data doesn't have the info about "require/include xxx", so we need check them manually. - For the .bbclass, .inc and .conf file, we can't get their file depends from the cooker_data, we need check them manually. * Usage: $ bitbake-layer show-cross-depends I don't like the name "show-cross-depends", figure-out-cross-depends might be better, but most of the commands are "show-xxx" for bitbake-layers. * Output: (snipped) /work/poky/meta/recipes-support/libusb/libusb-compat_0.1.4.bb inherits /work/poky/meta-yocto/classes/poky-sanity.bbclass /work/poky/meta-intel/meta-cedartrail/recipes-cdv-media/images/core-image-cdv-media.bb requires /work/poky/meta/recipes-sato/images/core-image-sato.bb /work/poky/meta-yocto/recipes-core/tiny-init/tiny-init.bb RDEPENDS /work/poky/meta/recipes-core/busybox/busybox_1.20.2.bb /work/poky/meta-intel/common/recipes-bsp/amt/lms_7.1.20.bb DEPENDS /work/poky/meta/recipes-devtools/autoconf/autoconf_2.69.bb /work/poky/meta/classes/distrodata.bbclass includes /work/poky/meta-yocto/conf/distro/include/package_regex.inc /work/poky/meta-intel/meta-sys940x/conf/machine/sys940x.conf requires /work/poky/meta/conf/machine/include/tune-atom.inc [YOCTO #3387] (Bitbake rev: 100502ef722bf19b6c125a5e017f31686ad18421) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-diffigs: Don't pull in tinfoil unless we really need/plan ↵Richard Purdie2013-01-251-1/+1
| | | | | | | | | | | to use it This means we can run in parallel with other bitbake processed we're not in task mode. (Bitbake rev: 20222f2f16130e91eed5e68286188ee0e8f8f3bf) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-layers: fix get_file_layerRobert Yang2013-01-251-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | The get_file_layer can't handle the nested layer correctly, e.g.: meta-intel/conf/layer.conf meta-intel/meta-cedartrail/conf/layer.conf They are two layers, the file: meta-intel/common/recipes-bsp/amt/lms_7.1.20.bb belongs to meta-intel's layer, but the get_file_layer() may return meta-cedartrail accordig to BBLAYERS' order, since it uses: for layerdir in self.bblayers: if regex.match(os.path.join(layerdir, 'test')): return self.get_layer_name(layerdir) which doesn't care the filename, re-match the filename would fix the problem. [YOCTO #3387] (Bitbake rev: 7a31b9eac4d894c302f0e052a132c31b17d13d1f) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: hig.py: refactor into individual componentsBogdan Marinescu2013-01-161-1/+3
| | | | | | | | | | | | | | | | | | Since hig.py was becoming too large (which impacted maintenance and operations like git merges) it was split into individual files for the classes that were implemented in hig.py. hig is now a Python package (lib/bb/ui/crumbs/hig/). The patch was tested by building core-image-basic/qemux86 in Hob and accessing the various UI elements implemented in hig. Note that the patch does not change the functionality of Hob in any way, it's just a code refactoring that should make life a bit easier for Hob developers. [YOCTO #3200] (Bitbake rev: a7a2b730f915cafe7aa30539622dd1ca64ae41f5) Signed-off-by: Bogdan Marinescu <bogdan.a.marinescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bin/bitbake, bb/__init__: Move BBDEBUG handling to bin/bitbakeRichard Purdie2012-12-141-0/+5
| | | | | | | | | | | | | The method this older code was accessing doesn't exist. A library shouldn't be changing behaviour based on the environment anyway when sepcific function calls exist to correctly setup the logging. Fix the crash if BBDEBUG was used by moving the code to bin/bitbake. [YOCTO #3319] (Bitbake rev: 3a1b75037fe1e5282ffd40b037e93353405faa45) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update version to 1.17.0Richard Purdie2012-11-261-1/+1
| | | | | | (Bitbake rev: cc7fdbdc607df530f5539b162831bf9998eb48d8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake/server: Remove dead console log codeRichard Purdie2012-11-011-5/+1
| | | | | | | | This code is dead and doesn't do anything so lets remove it. (Bitbake rev: 8d45739f49618757a5d7d79782deda355e3981ec) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update version to 1.16.0Richard Purdie2012-10-021-1/+1
| | | | | | (Bitbake rev: a579754a04bdcf450e6957dde614a15c11df39e2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: Unbuffer stdout for log filesJason Wessel2012-09-241-0/+8
| | | | | | | | | | | | | | | | | | | | It is possible to lose critical log data when python exits in an unorderly fashion via segmentation fault or certain types of crashes. This is because the buffer characteristics are inherited from the top level stdout, which should be set to unbuffered, for the purpose of all the forked children. This pushes the buffering to the OS, instead of having python managing the buffers in its stream handler class. This change is also to provide the ability to tail logs written from processes in "real time" because they would be written in an orderly fashion depending upon the OS characteristics for the file I/O. (Bitbake rev: c6a367bc3224adafca698a4ffc5414ad83842c16) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: runqueue: Add --no-setscene to skip all setscene tasksJason Wessel2012-09-241-0/+2
| | | | | | | | | | | Mainly intended for the purpose of debugging or forcing builds from source, the --no-setscene will prevent any setscene tasks from running. (Bitbake rev: 440e479f3e248482c38c149643403c6907ac7034) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-diffsigs: allow specifying task & follow deps recursivelyPaul Eggleton2012-09-071-5/+92
| | | | | | | | | | | | | | | Add the ability to compare the two most recent runs of a specified task, and follow dependent hash changes recursively. This enables you to trace back and find exactly why a task was re-run after the fact. Note that this relies on the metadata providing a function, hooked in as bb.siggen.find_siginfo, which allows searching in the appropriate places to find signature data files. (Bitbake rev: cc70181659c07e04c205e17832846acf1ff31d28) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: lib/bb/siggen.py: make signature dump/compare functions return a listPaul Eggleton2012-09-072-3/+8
| | | | | | | | | | These functions become a little bit more reusable if they return a list containing the output rather than just printing it. (Bitbake rev: a0ad2a947b71abcc0a1244cf139b9e9dfd8ee049) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: tinfoil: create simple interface for bitbake-based utilitiesPaul Eggleton2012-09-071-99/+47
| | | | | | | | | | | | The code to initialise BitBake within bitbake-layers should be useful for other utilities that need to query configuration or recipe information, so refactor it out into its own class, "Tinfoil" (to continue with our cooking metaphor). (Bitbake rev: e5707e3938ace47c4a8d1fa2e81583fd4dc6b95d) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bin/bitbake: Clarify wording in help output for -sTrevor Woerner2012-08-301-1/+1
| | | | | | | | | | The '-s' option shows (input) recipes, not (built/output) packages. Clarify the help wording for this option so it is consistent with how bitbake defines recipes and packages. (Bitbake rev: 0cac6d647c58ae449323959220775fc1afd5bfb0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-layers: use parsable title for show-appendsPaul Eggleton2012-08-221-1/+1
| | | | | | | | | | | Print title text surrounded by === as we do with other subcommands so that you can filter it out in scripts. (You will also want to filter out lines starting with "WARNING:" if you just want the list). (Bitbake rev: ba15ba16a5d863886bcfd5b3f0bdfff2a6de11a0) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-layers: avoid full parse for show-layers subcommandPaul Eggleton2012-08-221-4/+7
| | | | | | | | | | We don't actually need to parse all recipes just to show the configured layers, so just parse the configuration instead. (Bitbake rev: 406477cbae066b6379873e266cb79801e545a61c) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bin/bitbake: Remove knotty2 from the list of valid interfacesRichard Purdie2012-08-171-1/+1
| | | | | | (Bitbake rev: e0f91faf195be63803d39fb42fcd115ad558c79f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake-layers: fix help for show-overlayed to match behaviourPaul Eggleton2012-08-021-1/+1
| | | | | | | | | | 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 <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Update version to 1.15.3Richard Purdie2012-07-191-1/+1
| | | | | | (Bitbake rev: befbb5c9428eaf98b2ff9c4b36b0b3f2dce7fe07) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake/cooker: Print which pkgs would be built in -g outputRobert Yang2012-07-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: tweak help text for -C slightlyPaul Eggleton2012-06-251-1/+1
| | | | | | | | | | | 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 <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: bitbake: add -C option to invalidate a task and rebuild the targetPaul Eggleton2012-06-211-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <jason.wessel@windriver.com>. Implements [YOCTO #2615]. (Bitbake rev: 2530e0faada5775897cfd1b93aba6925826dca73) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image-writer: tweak some stringsKang Kai2012-06-141-5/+5
| | | | | | | | | | Tweak some strings in accord with the script name 'image writer', and remove extra noun 'button'. (Bitbake rev: d2d65335e8fc2417ebd3910f645cc00a4abfbeaa) Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* hob2: create a standalone deploy image toolKang Kai2012-06-081-0/+120
| | | | | | | | | | | | | [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 <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: support $BITBAKE_UI environmentEnrico Scholz2012-05-231-4/+5
| | | | | | | | | | | | | | | | | 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 <enrico.scholz@sigma-chemnitz.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Fixup bitbake-selftestRichard Purdie2012-05-041-0/+0
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Add start of bitbake regression/self testingRichard Purdie2012-05-041-0/+38
| | | | | | | | | | | | | | | 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 <richard.purdie@linuxfoundation.org>
* Update version to 1.15.2 (correspdoning to Yocto 1.2 release)Richard Purdie2012-05-011-1/+1
| | | | | | (Bitbake rev: 270a05b0b4ba0959fe0624d2a4885d7b70426da5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers: hide deprecation warningsPaul Eggleton2012-04-171-0/+2
| | | | | | | | | | | | There are a number of DeprecationWarnings within BitBake code which bitbake itself filters out; bitbake-layers was not doing this, resulting in a stream of warnings printed out when used with Python < 2.7 (these warnings default to disabled on version 2.7 and above.) (Bitbake rev: 0a2378237f07eb1c812e2308e64b7d70781e2b39) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ui/knotty: Add a footer to the build output for interactive terminals as ↵Richard Purdie2012-03-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | knotty2 UI On terminals which support it, add summary information to the end of the build output about the number of tasks currently running and how many tasks we've run so far. This provides a summary at a glace of what the current state of the build is and what the build is currently doing which is lacking in the current UI. Also disable echo of characters on stdin since this corrupts the disable, particularly Crtl+C. The "waiting for X tasks" code can be merged into this code too since that is only useful on interactive terminals and this improves the readability of that output too. Improvements since v0: * The tasks are ordered in execution order. * The display is only updated when the list of tasks changes or there is output above the footer. * Running task x oy y and package messages are supressed from the console This UI can be accessed with "bitbake -u knotty2". (From Poky rev: e38b4569648f2916c4370871c79e6a6090eb8bc1) (Bitbake rev: 156189c799d2bb1f69bdaa04b5cd718fe7881425) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Add bitbake-dumpsig to make it more obvious how to dump a signatures fileRichard Purdie2012-03-211-0/+9
| | | | | | | | [YOCTO #2057] (Bitbake rev: c5fdc6c02fe4712d3114caccfd759a626bd9677b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers: fix traceback in show-overlayed with nothing overlayedPaul Eggleton2012-03-201-1/+1
| | | | | | | | | | There is no logger.note, use logger.plain instead (which is what we really want here anyway.) (Bitbake rev: c4f7fd708c48d4323db4bbeb3074f576f5be7aa2) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake/bitbake-prserv: Set file mode bits "x".Lianhao Lu2012-03-021-0/+0
| | | | | | | [YOCTO #2051] Set 'x' bit to make bitbake-prserv executable. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: add -B option to bind with interfaceDongxiao Xu2012-02-231-3/+14
| | | | | | | | | | When start bitbake as a server only process, we need to assign certain interface to it. (Bitbake rev: 95b97d2dc6466ea3d99371f5b5bd68f6f3c99074) Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers: add copyright noticePaul Eggleton2012-02-091-0/+3
| | | | | | | | | | This ought to have been added earlier. (I consulted with Chris Larson on the notice covering his work.) (Bitbake rev: 69ed02b645bdc28c1bf24e436beeed37d226b56b) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers: list overlayed classes in show-overlayedPaul Eggleton2012-02-011-0/+47
| | | | | | | | | | | | Classes (.bbclass files) can be overlayed in a layer although they are currently located by BitBake in a different way (via BBPATH instead of using layer priority) and thus it is useful to be able to see when this is in effect and which layer's class is actually being used. (Bitbake rev: f6493e4bad005a82580380d800ebf4c438292f5b) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers: add show-recipes subcommandPaul Eggleton2012-02-011-5/+52
| | | | | | | | | | | | | Add a show-recipes subcommand which lists all available recipes, with the layer they are provided by. You can optionally filter the output by recipe name (PN). (This is a generalised version of the show-overlayed subcommand.) (Bitbake rev: 05e86ba966f5a26721891c82b21afa48768a67cc) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers: improve show-overlayed outputPaul Eggleton2012-02-011-11/+105
| | | | | | | | | | | | | | | | | | | | | | Make the following improvements to the show-overlayed subcommand: * Show recipes that are overlayed when the version is higher or lower, not just when it is the same. This gives a much better picture of the influence each layer is having over the metadata used for building. This can be disabled with the -s option if you just want to see recipes with the same version as before. * Default to showing name (PN), layer and version rather than the full path and filename. The old style formatting can be used by specifying the -f option. * Mark skipped recipes as such in the output, and print them in the correct sorted place in the list rather than at the end * Prefix/suffix title line with === so it can be filtered out easily in shell scripts if desired (Bitbake rev: 43b473275d3cb2e60a14e4a52cdc4654b3f4e5e7) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers: use directory name as layer namePaul Eggleton2012-02-011-19/+20
| | | | | | | | | | | | | | | | | | | It turns out that using the collection name as specified within layer.conf (i.e. what gets added to BBFILE_COLLECTIONS) as a name to refer to the layer is not particularly useful, since layer creators aren't necessarily setting these to a meaningful value - e.g. OE-Core uses "normal", meta-oe uses "openembedded-layer", etc. In any case, BitBake uses the directory name in its list of configured layers in the system information presented upon starting a build, so let's just do the same here and avoid confusion. Also rename the get_append_layer function to get_file_layer since it is in no way specific to bbappends. (Bitbake rev: 35d2c1c618826e961dbf4b9889b829f469346d74) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake-layers: use dashes in subcommandsPaul Eggleton2012-02-011-5/+7
| | | | | | | | | | | Rather than the slightly awkward underscores, use dashes in subcommands e.g. show-layers instead of show_layers. (The old underscored forms continue to be accepted however.) (Bitbake rev: 6d311ddc1be04ae5bd0a1ebee94b44968e8a3f27) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Bump the version to 1.15.1Richard Purdie2012-01-231-1/+1
| | | | | | (Bitbake rev: 65c2eb1c095fe7ba3259060aefd4ba0e20cae319) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: Automatically start local PR service.Lianhao Lu2012-01-111-5/+4
| | | | | | | | | | | | | | | | | [YOCTO #1126] A local PR service will be started and stopped automatically along with the bitbake invocation/ternimation. This local PR service will be started only and if only when the PRSERV_HOST is set to 'localhost' and PRSERV_PORT is set to '0'. When started, the sqlite3 database is stored at "${PERSISTEN_DIR}/prserv.sqlite3" or "${CACHE}/prserv.sqlite3". (Bitbake rev: 9d8f45407c67ed0d3c4f820cf646de3c385067c7) Signed-off-by: Lianhao Lu <lianhao.lu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-14 13:44:26 +0000