linux/poky.git/bitbake/bin/bitbake-layers, branch 1.3_M2.rc1

bitbake-layers: hide deprecation warnings

2012-04-17T10:41:31+00:00

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 Signed-off-by: Richard Purdie

bitbake-layers: fix traceback in show-overlayed with nothing overlayed

2012-03-20T15:21:32+00:00

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 Signed-off-by: Richard Purdie

bitbake-layers: add copyright notice

2012-02-09T14:14:20+00:00

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 Signed-off-by: Richard Purdie

bitbake-layers: list overlayed classes in show-overlayed

2012-02-01T15:08:42+00:00

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 Signed-off-by: Richard Purdie

bitbake-layers: add show-recipes subcommand

2012-02-01T15:08:42+00:00

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 Signed-off-by: Richard Purdie

bitbake-layers: improve show-overlayed output

2012-02-01T15:08:41+00:00

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 Signed-off-by: Richard Purdie

bitbake-layers: use directory name as layer name

2012-02-01T15:08:41+00:00

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 Signed-off-by: Richard Purdie

bitbake-layers: use dashes in subcommands

2012-02-01T15:08:41+00:00

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 Signed-off-by: Richard Purdie

bitbake-layers: close files in apply_append()

2012-01-10T17:40:42+00:00

It's recommended practice to close files when finished with them and the code in this function was not doing this. (Bitbake rev: 470a160813ce6cf04f83258d46ded5c2ab8bc520) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

bitbake-layers: flatten: warn the user if output structure is incorrect

2012-01-10T17:40:42+00:00

If you flatten layers that have different directory structures you may not end up with a usable layer in the output directory - some files won't be picked up by BitBake. To try to avoid this problem, once flattening has completed, get the BBFILES entries that correspond to the layer from which the output layer's conf/layer.conf came from, and check through all of the .bb/.bbappend files in the output directory to see if any will not be referred to by BBFILES in the output layer. If any are found, show a warning to the user. (Bitbake rev: 8e4dc97614f2022855143b49d18795ca0352b237) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie