openembedded-core.git/meta/lib/oeqa/selftest/devtool.py, branch 2015-4

oe-selftest: add missing dependency to test_recipetool_create_git

2015-03-20T11:03:14+00:00

libmatchbox links to libjpeg if it is present so just explicitly build
it and then check it appears in DEPENDS.

Signed-off-by: Paul Eggleton 
Signed-off-by: Ross Burton

oe-selftest: add a test for devtool modify on recipes fetching local files

2015-03-20T11:03:13+00:00

With the change to externalsrc we can now handle these, so add a test
to ensure they can be built.

Signed-off-by: Paul Eggleton 
Signed-off-by: Ross Burton

oe-selftest: add a test for devtool deploy-target

2015-03-20T11:03:13+00:00

Whilst this test would seemingly be better placed as a runtime test,
unfortunately the runtime tests run under bitbake and you can't run
devtool within bitbake (since devtool needs to run bitbake itself).
Additionally we are testing build-time functionality as well, so
really this has to be done as an oe-selftest test.

This test does have a few perhaps unusual requirements in order to run:
 * pexpect is installed
 * MACHINE is set to one of the qemu machines
 * runqemu tap devices have been set up

Signed-off-by: Paul Eggleton 
Signed-off-by: Ross Burton

devtool: modify/extract: prevent usage with incompatible recipes

2015-03-20T11:03:11+00:00

Consolidate code for checking compatible recipes and consider meta and
packagegroup recipes as well as package-index and gcc-source to be
incompatible.

Signed-off-by: Paul Eggleton 
Signed-off-by: Ross Burton

devtool: reset: add ability to reset entire workspace

2015-03-20T11:03:11+00:00

Add a -a/--all option to allow you to quickly reset all recipes in your
workspace.

Signed-off-by: Paul Eggleton 
Signed-off-by: Ross Burton

devtool: fix broken clones of git recipes

2015-02-23T08:08:20+00:00

Because we move the workdir when extracting source, then move the source
and delete the temporary workdir, you lose the indirection symlink
pointed to by the alternates file (which is created when the fetcher
clones it from DL_DIR with -s) and the resulting repository is broken.
In any case, for a source repo that the user may put their own changes
into, we can't really rely on a clone made with -s in case the
original goes away - because of cleanall, DL_DIR disappearing, etc. So
repack the repository so that it is a complete, non-shared clone after
unpacking.

(While I'm at it, add a test for devtool modify with a git recipe which
verifies that this works.)

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

devtool: update-recipe: add handling for git recipes

2015-02-23T08:08:19+00:00

When updating git-based recipes, in a lot of cases what you want is to
push the changes to the repository and update SRCREV rather than to
apply patches within the recipe. Updating SRCREV is now the default
behaviour for recipes that fetch from git, but this can be overridden
in both directions using a new -m/--mode option.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

devtool: build: run do_populate_sysroot instead of do_install

2015-02-23T08:08:19+00:00

If you want to be able to make use of libraries in conjunction with
devtool then we need to install them into the sysroot for other recipes
to use. Make it a configuration option in case it needs to be changed at
runtime.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

devtool: reset: run bitbake -c clean on recipe

2015-02-23T08:08:19+00:00

If you've added a new recipe, you want the output cleaned when you do
devtool reset, otherwise cruft from building the recipe may remain which
could interfere with future builds.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

oeqa/selftest: populate pkgdata/shlibs in test_recipetool_create_git

2014-12-25T08:26:01+00:00

Build some recipes so that we have the needed data in the sysroot for
recipetool to refer to when scanning for dependencies.

Signed-off-by: Paul Eggleton