meta-phosphor: Don't build debug tarball implicitly
In previous builds, the debug tarball was built as part of the
obmc-phosphor-image implicitly. This increases the build times by a
trivial amount, which matters, but is not that important. It also makes
debugging image dependencies (using bitbake -g) a bear, given that it
includes all dependencies for the debug tarball, as well as the actual
image. Given that it's pretty trivial to build this manually via
bitbake obmc-debug-tarball
and (at least in my opinion) injecting the task seems like a bit of a
violation of the yocto intracacies, and gives a surprising result to the
user, this patchset removes the task add, and makes
obmc-phosphor-debug-tarball a truly separate build target.
(From meta-phosphor rev: 5c848ab3436bd0ed1062c4657f35a6a6890992ad)
Signed-off-by: Ed Tanous <ed.tanous@intel.com>
Change-Id: Ie2294f8e324249a44ef73aa10d57f332e8f54168
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
diff --git a/meta-phosphor/classes/obmc-phosphor-image.bbclass b/meta-phosphor/classes/obmc-phosphor-image.bbclass
index 17cbdcd..807c9c4 100644
--- a/meta-phosphor/classes/obmc-phosphor-image.bbclass
+++ b/meta-phosphor/classes/obmc-phosphor-image.bbclass
@@ -98,8 +98,6 @@
OBMC_IMAGE_EXTRA_INSTALL ?= ""
-do_image_complete[depends] += "obmc-phosphor-debug-tarball:do_image_complete"
-
# The /etc/version file is misleading and not useful. Remove it.
# Users should instead rely on /etc/os-release.
remove_etc_version() {