diff options
author | Chris Larson <chris_larson@mentor.com> | 2010-03-19 17:22:19 -0700 |
---|---|---|
committer | Richard Purdie <rpurdie@linux.intel.com> | 2010-03-25 17:25:45 +0000 |
commit | c24424327409544807a781bba4e6f9a8e178dcce (patch) | |
tree | 5df97b6f8665f6cdf9a9698c05e2a98f58bd5975 /build | |
parent | cefeeb1aa30a9d8744a6ff9c51811ebc8d18c735 (diff) | |
download | openembedded-core-c24424327409544807a781bba4e6f9a8e178dcce.tar.gz openembedded-core-c24424327409544807a781bba4e6f9a8e178dcce.tar.bz2 openembedded-core-c24424327409544807a781bba4e6f9a8e178dcce.zip |
Implement BBVERSIONS
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
:<basever> 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 <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Diffstat (limited to 'build')
0 files changed, 0 insertions, 0 deletions