[OE-core] [PATCH 02/11] devtool: build-image: stop using add_md5
Ed Bartosh
ed.bartosh at linux.intel.com
Sun Aug 30 16:08:35 UTC 2015
It doesn't make sense to use it as image recipe is not
in workspace. It means that we can't do 'devtool reset'
for the recipe, which is a main point of using add_md5.
Signed-off-by: Ed Bartosh <ed.bartosh at linux.intel.com>
---
scripts/lib/devtool/build-image.py | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/scripts/lib/devtool/build-image.py b/scripts/lib/devtool/build-image.py
index d8e7b12..ebd9c59 100644
--- a/scripts/lib/devtool/build-image.py
+++ b/scripts/lib/devtool/build-image.py
@@ -21,7 +21,7 @@ import os
import logging
from bb.process import ExecutionError
-from devtool import exec_build_env_command, add_md5
+from devtool import exec_build_env_command
LOG = logging.getLogger('devtool')
@@ -38,8 +38,6 @@ def build_image(args, config, basepath, workspace):
afile.write('IMAGE_INSTALL_append = " %s"\n' % \
' '.join(workspace.keys()))
- add_md5(config, image, appendfile)
-
try:
exec_build_env_command(config.init_path, basepath,
'bitbake %s' % image, watch=True)
--
2.1.4
More information about the Openembedded-core
mailing list