poky/scripts/lib/devtool
Paul Eggleton d193531d5e 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>
2016-01-24 09:40:32 +00:00
..
__init__.py devtool: build: support using BBCLASSEXTENDed names 2016-01-11 15:41:46 +00:00
build-image.py devtool: second fix for running from a different directory 2015-09-24 17:54:24 +01:00
build.py devtool: build: ensure pkgdata is written out 2016-01-24 09:40:32 +00:00
deploy.py devtool: second fix for running from a different directory 2015-09-24 17:54:24 +01:00
package.py devtool: drop unused plugin_init() functions 2015-12-01 21:32:04 +00:00
runqemu.py devtool: runqemu: avoid recipe parse 2015-09-24 17:54:25 +01:00
sdk.py classes/populate_sdk_ext: add option to bring in pkgdata for world 2016-01-24 09:40:32 +00:00
search.py devtool: search: print SUMMARY value 2015-12-01 21:32:04 +00:00
standard.py devtool: reset: support recipes with BBCLASSEXTEND 2016-01-11 15:41:46 +00:00
upgrade.py lib/oe/recipeutils: refactor patch_recipe_file() to use edit_metadata() 2015-12-01 21:32:04 +00:00