linux/poky.git/bitbake/doc, branch green

Implement BBVERSIONS

2010-03-25T17:25:45+00:00

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:30+00:00

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

Implement ??= operator

2010-03-22T15:02:59+00:00

??= 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:35+00:00

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

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

2010-01-20T18:46:02+00:00

Signed-off-by: Richard Purdie

bitbake: Add tryaltconfigs option to disable the alternative configuration attempts and make the 'continue' more aggresive

2008-10-28T22:15:06+00:00

bitbake: Sync with 1.8 branch upstream

2008-09-30T20:32:33+00:00

git-svn-id: https://svn.o-hand.com/repos/poky/trunk@5345 311d38ba-8fff-0310-9ca6-ca027cbcb966

bitbake: Sync manual updates and version info with bitbake svn

2007-06-12T10:06:56+00:00

git-svn-id: https://svn.o-hand.com/repos/poky/trunk@1920 311d38ba-8fff-0310-9ca6-ca027cbcb966

bitbake: Sync with upstream.

2007-01-08T23:53:01+00:00

* File licence headers were sanitised causing most of the diff. * cooker.py was created from bin/bitbake. * cvs fetcher port option was added * The -f force option was fixed to work correctly * Multiple entries in rrecrdeps are now handled correctly (allows adding do_deploy to image depends) git-svn-id: https://svn.o-hand.com/repos/poky/trunk@1129 311d38ba-8fff-0310-9ca6-ca027cbcb966

Fix typo

2006-12-05T12:13:00+00:00

git-svn-id: https://svn.o-hand.com/repos/poky/trunk@1005 311d38ba-8fff-0310-9ca6-ca027cbcb966