diff options
| author | Elliot Smith <elliot.smith@intel.com> | 2016-07-12 15:54:50 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-07-19 08:56:51 +0100 |
| commit | 587275eefd744032f00ebdce35134b2ab2bb7572 (patch) | |
| tree | f8f178cdeacf3122df1ab7abd4550fbf8b4374c0 /meta/recipes-devtools/python-numpy/files/x86/numpyconfig.h | |
| parent | 150e5588a01b1334ae3158c9b13e28bec428af37 (diff) | |
| download | poky-587275eefd744032f00ebdce35134b2ab2bb7572.tar.gz | |
bitbake: toaster: use has_images() methods to display images correctly
In the build dashboard, we had issues with showing images correctly,
as we were using the is_image property of targets to determine
whether a target would have image files. This property can
be set to True if a target refers to an image recipe
(e.g. "core-image-minimal"), even if the task used in the build
didn't produce any image files.
By adding has_images() methods to the Target and Build objects,
which count associated Target_Image_File objects,
we can correctly determine whether a target has image files
associated with it, and if any of the targets for a build has
image files. This means that we can screen out the left-hand
"Images" menu options for builds which contained image-related
targets (e.g. "core-image-minimal") but which didn't produce
any images (e.g. "rootfs" task).
[YOCTO #9500]
[YOCTO #9784]
(Bitbake rev: f6bba0ff254d5ed3163151d4b938f3a43c9acb0a)
Signed-off-by: Elliot Smith <elliot.smith@intel.com>
Signed-off-by: bavery <brian.avery@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/python-numpy/files/x86/numpyconfig.h')
0 files changed, 0 insertions, 0 deletions
