aboutsummaryrefslogtreecommitdiffstats
path: root/meta/recipes-graphics
diff options
context:
space:
mode:
authorElizabeth Flanagan <elizabeth.flanagan@intel.com>2013-07-02 15:29:29 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-07-05 15:34:25 +0100
commitefaa5ab1031d893829085ed13938a37a0a2a8ede (patch)
treecc136f04995af3630d2c6597b29a058372a096ca /meta/recipes-graphics
parent4770cff7b90a50643973ec31ff536bc2950f77e4 (diff)
downloadopenembedded-core-contrib-efaa5ab1031d893829085ed13938a37a0a2a8ede.tar.gz
layer.conf: Bumping LAYERVERSION_core
Bumping LAYERVERSION_core to denote where meta-toolchain* is being depreciated. This goes back to my RFC: http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/39016 As we are removing meta-toolchain* and replacing it with bitbake <imagename> -c populate_sdk this causes issues with those of us who need to do automated builds both on the current development branch and on prior development branches. Example: For prior releases, I need to build meta-toolchain*. Without having a simple way to figure out where this is no longer the case, I (and other folks who run automated builds) end up having to jump through a lot of hoops trying to figure out where this layer changed. Utilizing LAYERVERSION_* to do it makes sense as there is a significant change that would cause issues for build engineers. (From OE-Core rev: 41053141cdc04fd6d8490b54b8b8dc59dc0fe93a) Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-graphics')
0 files changed, 0 insertions, 0 deletions