summaryrefslogtreecommitdiffstats
path: root/meta/lib
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2016-01-23 00:59:49 +1300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-01-24 09:40:32 +0000
commitd193531d5ead804380884e97e14ce00cbdccf494 (patch)
tree314729c881accf4e2fd058fbe191c094b484960d /meta/lib
parentd3a4f72896aaea7374bd8915cfe3adaaecc55a2d (diff)
downloadpoky-d193531d5ead804380884e97e14ce00cbdccf494.tar.gz
devtool: build: ensure pkgdata is written out
When you run devtool build, you need to have the pkgdata written out at the end, so that if what you're adding is a library and the next thing you add is something that depends on that library, the necessary information to map the dependency back to the recipe is present. In practical terms all this means is we need do_packagedata to run in addition to do_populate_sysroot. This does mean that do_package needs to run which wasn't running before, and that means that the few package QA tests that run within do_package such as installed-vs-shipped will now be run. This may be a bit bothersome, and prompted a fix for one of our oe-selftest tests as a result, but I don't see an easy way around it. Ultimately if you care about using the recipe in an image you'll need to fix any such errors anyway. Fixes [YOCTO #8887]. (From OE-Core rev: 6579c7120ee5a541427ff5b6b07f838d52f9fe7c) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib')
-rw-r--r--meta/lib/oeqa/selftest/devtool.py7
1 files changed, 6 insertions, 1 deletions
diff --git a/meta/lib/oeqa/selftest/devtool.py b/meta/lib/oeqa/selftest/devtool.py
index 43c7cdade1..d95cb08749 100644
--- a/meta/lib/oeqa/selftest/devtool.py
+++ b/meta/lib/oeqa/selftest/devtool.py
@@ -226,8 +226,13 @@ class DevtoolTests(DevtoolBase):
226 # Clean up anything in the workdir/sysroot/sstate cache (have to do this *after* devtool add since the recipe only exists then) 226 # Clean up anything in the workdir/sysroot/sstate cache (have to do this *after* devtool add since the recipe only exists then)
227 bitbake('libftdi -c cleansstate') 227 bitbake('libftdi -c cleansstate')
228 # libftdi's python/CMakeLists.txt is a bit broken, so let's just disable it 228 # libftdi's python/CMakeLists.txt is a bit broken, so let's just disable it
229 # There's also the matter of it installing cmake files to a path we don't
230 # normally cover, which triggers the installed-vs-shipped QA test we have
231 # within do_package
229 recipefile = '%s/recipes/libftdi/libftdi_%s.bb' % (self.workspacedir, version) 232 recipefile = '%s/recipes/libftdi/libftdi_%s.bb' % (self.workspacedir, version)
230 result = runCmd('recipetool setvar %s EXTRA_OECMAKE -- "-DPYTHON_BINDINGS=OFF"' % recipefile) 233 result = runCmd('recipetool setvar %s EXTRA_OECMAKE -- \'-DPYTHON_BINDINGS=OFF -DLIBFTDI_CMAKE_CONFIG_DIR=${datadir}/cmake/Modules\'' % recipefile)
234 with open(recipefile, 'a') as f:
235 f.write('\nFILES_${PN}-dev += "${datadir}/cmake/Modules"\n')
231 # Test devtool build 236 # Test devtool build
232 result = runCmd('devtool build libftdi') 237 result = runCmd('devtool build libftdi')
233 staging_libdir = get_bb_var('STAGING_LIBDIR', 'libftdi') 238 staging_libdir = get_bb_var('STAGING_LIBDIR', 'libftdi')