Paul Eggleton db55d31dc2 devtool: handle virtual providers ... For modify / extract / upgrade, if the specified "recipe" is not actually a recipe but a virtual target such as virtual/kernel, map it correctly to the actual recipe and make sure we use that name within the workspace. Thanks to Chris Larson for reminding me this was still broken and for a hint on how to fix it. (From OE-Core rev: 1f7752282ffb47d2621030ddb2fa42a5e491d6d2) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2015-10-21 22:56:03 +01:00
..
__init__.py	devtool: update-recipe: enable var history tracking	2015-10-01 15:07:48 +01:00
build-image.py	devtool: second fix for running from a different directory	2015-09-24 17:54:24 +01:00
build.py	devtool: check that source tree still exists	2015-09-23 09:53:14 +01:00
deploy.py	devtool: second fix for running from a different directory	2015-09-24 17:54:24 +01:00
package.py	devtool: second fix for running from a different directory	2015-09-24 17:54:24 +01:00
runqemu.py	devtool: runqemu: avoid recipe parse	2015-09-24 17:54:25 +01:00
sdk.py	classes/populate_sdk_ext: drop work-config.inc	2015-09-23 09:53:12 +01:00
search.py	devtool: second fix for running from a different directory	2015-09-24 17:54:24 +01:00
standard.py	devtool: handle virtual providers	2015-10-21 22:56:03 +01:00
upgrade.py	devtool: handle virtual providers	2015-10-21 22:56:03 +01:00