diff options
| author | Ross Burton <ross.burton@intel.com> | 2016-10-13 20:36:35 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-10-15 09:49:10 +0100 |
| commit | 03cdb3366ded46cd760656e4cda0be37c1f82109 (patch) | |
| tree | 688dcc6180aac475a8639e328946974cb6818c7f /oe-init-build-env-memres | |
| parent | fcfd3e76eb52353345aa9a1f7ec0f9795e607493 (diff) | |
| download | openembedded-core-03cdb3366ded46cd760656e4cda0be37c1f82109.tar.gz openembedded-core-03cdb3366ded46cd760656e4cda0be37c1f82109.tar.bz2 openembedded-core-03cdb3366ded46cd760656e4cda0be37c1f82109.zip | |
pixbufcache: handle gdk-pixbuf not being present
It's possible - albeit unlikely - that gdk-pixbuf isn't present in the sysroot
when a recipe inheriting this class is and the sysroot is finalised.
One example would be if the sstate archive has librsvg but not gdk-pixbuf:
librsvg will be extracted from the sstate but gdk-pixbuf will be built to "fill
in the gap". In this situation the setscene completion hook installed by
pixbufcache.bbclass will attempt to execute gdk-pixbuf-query-loaders, but that
binary hasn't been installed by gdk-pixbuf yet.
Also add gdk-pixbuf-native to DEPENDS in native builds to ensure that the
binaries we expect will be present, as it's possible to build loaders without
linking to GdkPixbuf.
[ YOCTO #10420 ]
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'oe-init-build-env-memres')
0 files changed, 0 insertions, 0 deletions