Paul Eggleton 30c7e7ac41 devtool: add: properly handle separate build directory ... When we were adding a recipe for software that would typically be built in the same directory as the source, we were always using a separate build directory unless the user explicitly specified not to, leading to errors for software that doesn't expect to be built that way (such as Python modules using distutils). Split out the code that makes this determination automatically from the "devtool modify" and "devtool upgrade" code and re-use that here so the behaviour is consistent. (From OE-Core rev: 320585b7ff6340df0b0dbc63f95ed3ca8fc3a993) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>		2015-09-23 09:53:15 +01:00
..
__init__.py	devtool: add: properly handle separate build directory	2015-09-23 09:53:15 +01:00
build-image.py	devtool: make plugin_init optional	2015-09-12 22:48:30 +01:00
build.py	devtool: check that source tree still exists	2015-09-23 09:53:14 +01:00
deploy.py	devtool: check that source tree still exists	2015-09-23 09:53:14 +01:00
package.py	devtool: check that source tree still exists	2015-09-23 09:53:14 +01:00
sdk.py	classes/populate_sdk_ext: drop work-config.inc	2015-09-23 09:53:12 +01:00
standard.py	devtool: add: properly handle separate build directory	2015-09-23 09:53:15 +01:00
upgrade.py	devtool: add: properly handle separate build directory	2015-09-23 09:53:15 +01:00