openembedded-core.git/bitbake/doc/manual, branch master

bitbake: Remove in-tree version

2011-02-23T18:48:51Z

Bitbake should be used by checking it out from its own repo Signed-off-by: Khem Raj

manual: document scmdata=keep for CVS, SVN and Git

2011-01-04T14:46:51Z

(Bitbake rev: f42e6d33b986183eee2c74aa7b1bbc9b339276a9) Signed-off-by: Andreas Oberritter Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

*: use print() as a function

2010-07-16T14:10:40Z

to make python3 happy (Bitbake rev: c82926ccdd4ec4e3ad6e78a381dacb96adf9b409) Signed-off-by: Bernhard Reutner-Fischer Signed-off-by: Richard Purdie

Fix a couple typos in the CVS Fetcher section.

2010-07-02T14:41:35Z

"DL_DIRS" -> "DL_DIR" Remove superfluous trailing ">" after CVSDIR. (Bitbake rev: 34f396e749303367e657911bf10c43086dff7552) Signed-off-by: Robert P. J. Day Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

bb.event: NotHandled and Handled are on the way out

2010-07-02T14:41:31Z

(Bitbake rev: ed35b30f8e09b0bfc15102fa6483c55d6b7d61de) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

Implement BBVERSIONS

2010-03-25T17:25:45Z

This implements a feature similar to BBCLASSEXTEND, but for generating multiple versions of a given recipe. For example: BBVERSIONS = "1.0 2.0 git". In addition to the above, one can utilize [a-b] style patterns, and can have a : postfix, which allows you to essentially name the range of versions. Both the current version and the basever end up in OVERRIDES, and the basever gets placed into the BPV variable. The default BPV, if none is specified, is the original PV of the recipe, before bbversions processing. In this way, you can do things like: BBVERSIONS = "1.0.[0-6]:1.0.0+ 1.0.[7-9]:1.0.7+" SRC_URI_append_1.0.7+ = "file://some_extra_patch.patch;patch=1" Or you can create a recipe per range, and name the recipe file as such: nano_1.0.7+.bb. (Bitbake rev: 4ee9a56e16f1eb3c1649eaa3127b09ab0e93d1ec) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

usermanual.xml: Add documentation on bblayers.conf

2010-03-25T17:25:30Z

(Bitbake rev: 879229d12c2830dba9e0cb794e61e3c698b8dcc7) Signed-off-by: Richard Purdie

Implement ??= operator

2010-03-22T15:02:59Z

??= is a lazy, conditional assignment. Whereas a ?= immediately assigns to the variable if the variable has not yet been set, ??= does not apply the default assignment until the end of the parse. As a result, the final ??= for a given variable is used, as opposed to the first as in ?=. Note that the initial implementation relies upon finalise() to apply the defaults, so a "bitbake -e" without specifying a recipe will not show the defaults as set by ??=. Moving application of the default into getVar adds too large a performance hit. We may want to revisit this later. (Bitbake rev: 74f50fbca194c9c72bd2a540f4b9de458cb08e2d) Signed-off-by: Chris Larson Signed-off-by: Richard Purdie

bitbake: usermanual.xml: Add section for ?= var setting.

2010-02-10T16:25:35Z

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

bitbake: Switch to bitbake-dev version (bitbake master upstream)

2010-01-20T18:46:02Z

Signed-off-by: Richard Purdie