summaryrefslogtreecommitdiff
path: root/scripts/oe-setup-builddir
diff options
context:
space:
mode:
authorMing Liu <peter.x.liu@external.atlascopco.com>2017-02-26 08:39:19 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-03-01 15:50:19 +0000
commit0cb15d9559e34faffea1ac0be825d0602f225ba9 (patch)
treee664db11fcf6291ec0f720842cd6ff4d1a911a8f /scripts/oe-setup-builddir
parentd0902a5c3babbd3b291fa494462e083794ca4bee (diff)
downloadopenembedded-core-0cb15d9559e34faffea1ac0be825d0602f225ba9.tar.gz
openembedded-core-0cb15d9559e34faffea1ac0be825d0602f225ba9.tar.bz2
openembedded-core-0cb15d9559e34faffea1ac0be825d0602f225ba9.zip
generate-manifest-2.7.py: add logic to generate native manifest
python-native supposes to RPROVIDE all native packages as added in generate-manifest-2.7.py, but it does not so far, this leads a problem that sometimes bitbake cant find a runtime provider for a python-*-native when a new runtime dependency on it being required, this usualy happens after a new native python-* recipe is created or the old native python-* recipes are upgraded. To give a example, the following commit is trying to address such a issue: commit 4583cd1bb15306e8f0ab7bcd80732e6f35aa4533: [ python-native: Make python-native also RPROVIDE python-unittest-native ] To avoid manually extending RPROVIDE every time when a new runtime dependency is introduced, an argument '-n/--native' is added to the manifest generator, allowing it create a native python manifest, with a RPROVIDE line only, the RPROVIDE should contain all the sub-packages. The generated python-native-2.7-manifest.inc is also added which is included by python-native recipe. Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'scripts/oe-setup-builddir')
0 files changed, 0 insertions, 0 deletions