When using the sstate from another build machine, the path to the pixbuf
loader's cache points to a path on the remote machine. Hence, the update
of the icon cache fails on host.
(From OE-Core rev: f2cb906bdce08441a20eab927ca9e2a2a9735ed0)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
gtk-update-icon-cache-native is the only provider now
(From OE-Core rev: 7e437aa3e0ec862aac69a4434be0b2b652d26972)
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The only part required from native build is gtk-update-icon-cache. This is
provided by gtk-update-icon-cache-native_3.4.4. This version works properly
with gtk+. The patch was tested for gnome-icon-theme and hicolor-icon-theme by:
1. building xfce/gtk+ (gtk3-less) image
2. checking for existing icon-theme.cache in rootfs
3. running image / open menus + test applications
4. executing 'gtk-update-icon-cache-2.0 --validate <both icon-themes-dirs>'
5. executing 'gtk-update-icon-cache-2.0 -f <both icon-themes-dirs>' + exact size checking
(From OE-Core rev: 8d6406849bcad2a7bbd4483ccfa4e0f3d9b4ae21)
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This recipe builds natively just the gtk-update-icon-cache binary that is
required to run the gtk-icon-cache.bbclass postinstall scripts.
The advantage of doing this is it means running 400 less tasks which takes four
minutes on my machine, as the alternative is building GTK+ natively (and so
libX11, freetype, fontconfig...).
(From OE-Core rev: 8265ef7f3a3598ff4535da1e5f9329fcf236f776)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
remove automake patch as it been fixed upstream
(From OE-Core rev: e2a404f3263337e505b60acd6c7d10be2c915ac9)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This will allow gconftool-2 to run when configuration source addresses
contain the '+' sign.
[YOCTO #3893]
(From OE-Core rev: 5ba4d947189f76692ea6cc75500d9295417a2055)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- gnome-common finally is GPLv2+
- omf.patch is included in the new version
(From OE-Core rev: dba2105d2f6f5788d8f827edad4e8c601a409d1f)
Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- configure-nm.patch updated to apply
- hardcoded_libtool.patch updated to apply
- obsolete_automake_macros.patch removes as it's now part of upstream
(From OE-Core rev: a4ed7da18d8622fc0b6e3d32ac8ce9456b912322)
Signed-off-by: Marko Lindqvist <cazfi74@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In order to have the proper postinst/postrm scriptlets generated for
gtk+ immodules packages, use the already existing class.
[YOCTO #3853]
(From OE-Core rev: 1c5646dde09008662f064ce7e7400c4d68775278)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The native install was invoking a binary in $S, but it's been built into $B.
(From OE-Core rev: b6ffded282d2b4aeb924db443169a9263aade014)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When $B != $S the relative paths are wrong, so add an explict $S.
(From OE-Core rev: 68838f1d61f91229ee489889ad2c7f4b61a1f95c)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- DirectFB is not supported by gtk versions >= 2.18
[YOCTO #3642]
(From OE-Core rev: 87dc338bf631577d947a9c172ec5711b9f306530)
Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
GUPnP is now in meta-multimedia, so remove it from this SDK packagegroup.
(From OE-Core rev: 356a5ee5a74f9cee112eac2c595c13ef707eca82)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
cross.patch was accepted upstream, so update this patch with the commit that was
merged.
(From OE-Core rev: 8e5ffa370c4259f925a0454fe7fd81c80ef2174b)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add obsolete_automake_macros.patch that replaces automake macros
no longer supported by automake-1.13 with modern constructs.
(From OE-Core rev: 0beee6281fed3926b6871dbfdd907416d4a04886)
Signed-off-by: Marko Lindqvist <cazfi74@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add obsolete_automake_macros.patch that replaces automake macros
no longer supported by automake-1.13 with modern constructs.
(From OE-Core rev: 388939c4cebabce8ef05c8aec5b9dccf390b75f0)
Signed-off-by: Marko Lindqvist <cazfi74@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Mostly taken from meta-gnome, with some changes.
Instead of depending on gtk+-native, depend on just gdk-pixbuf-native and build
the tool required for the host directly. This saves building the entire GTK+
stack natively just for one tool.
Append a version suffix and use update-alternatives on gtk-update-icon-cache as
with GTK+ 2.
(From OE-Core rev: 16c0556808029a0f6a3f91a726b14626e9489498)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With GTK+ 3 being added soon we'll have potentially two providers of
gtk-update-icon-cache. Append a version to the binary and use
update-alternatives to ensure that the unversioned name works.
For gtk+-native the alternatives won't take effect, so install a symlink
explicitly. This will break if we have a gtk+3-native but we can fix that if
and when that happens.
(From OE-Core rev: a9e71b41463c6c8e2be50d40403a0017d3cdf146)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- add postinst using gsettings.bbclass
- modify the recipe according to the meta-gnome variant
(From OE-Core rev: 337add4a13275b906a98476321f48d75141c5399)
Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Part of the sato trimming process
(From OE-Core rev: cff5f9494f5bbb0df00ba8733d5356d381dde14b)
Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
crosscompile.patch: removed
- schema_bindings binary not generated anymore
remove-yelp-help-rules-var.patch: added
- YELP_HELP_RULES var is not used
[Other changes]
- the 2.34.13 version requires the gsettings-desktop-schemas
(add it to DEPENDS)
(From OE-Core rev: 3c6262dd270a7c2f709c84335501b345f2b47d38)
Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Part of the sato trimming process
(From OE-Core rev: a328741eff50cf00d1553a915fc81af41400a5fc)
Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- this is needed by metacity 2.34.13
(From OE-Core rev: 59d7b8b3bdef47c1ad45fc404b1b169b5f2980b7)
Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
sysrooted-pkg-config.patch: adapt to the new version
use-usr-bin-env-for-python-in-xml2po.patch: adapt to the new version
xsltproc_nonet.patch: adapt to the new version
(From OE-Core rev: f801dbb0af3ac01e2c8b53600c7a37aa82b08343)
Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removed patch as it was incorporated in new version
(From OE-Core rev: 5b671669e461a0f61ae178cb1ee2102fdedc13dc)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
since there are no providers
(From OE-Core rev: 90abd8d1cfbafd89c84d848020d1866b1f04a772)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is needed in order to point where the pixbuf loaders.cache is
located and avoid warnings like the one below that appear when the
sstate is fetched from a remote machine:
(gtk-update-icon-cache:8913): GdkPixbuf-WARNING **: Cannot open pixbuf
loader module file '/REMOTE/MACHINE/PATH/loaders.cache': No such file or directory
(From OE-Core rev: 6665a41c6506039e6ba6cfdbaa941369e42d682f)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is needed when sstate cache is fetched from another build server.
In this case, the postinstall will fail because the backend libraries
path will be from the build server.
(From OE-Core rev: bba414bc9d14eb2d29b54c68259d13ddbe6567fa)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Store node type separately in RsvgNode
commit 34c95743ca692ea0e44778e41a7c0a129363de84 upstream
The node name (formerly RsvgNode:type) cannot be used to infer
the sub-type of RsvgNode that we're dealing with, since for unknown
elements we put type = node-name. This lead to a (potentially exploitable)
crash e.g. when the element name started with "fe" which tricked
the old code into considering it as a RsvgFilterPrimitive.
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2011-3146https://bugzilla.gnome.org/show_bug.cgi?id=658014
[YOCTO #3581]
[ CQID: WIND00376773 ]
Upstream-Status: Backport
(From OE-Core rev: 64de49bed598ce9d4ee0b448badc38a433712aff)
Signed-off-by: Li Wang <li.wang@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This packagegroup is a toolset that contains most
of the native packages.
[YOCTO #3298]
(From OE-Core rev: 77092eeaadfd89375a6aea6d170664f4d3e6f6dd)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Apparently gdk-pixbuf-query-loaders always returns 0 but writes any
errors to stderr. So, the conditional exit at the end of the command was
useless. Write the errors to a file and exit only if the file size is
greater than 0.
(From OE-Core rev: 901fbfac48918db7bf809ded3df533504141c5ca)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This will generate the loaders.cache file for pixbuf, at rootfs time.
(From OE-Core rev: 5ba420bc0e282a1cbf000ce32034ad7ab15c01d5)
Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The new GLib has deprecated some functions, and libunique was building with
-Werror. Take a patch from upstream to update the build system and rationalise
the warning flags.
(From OE-Core rev: 713e1c82d32a477be84951d1dba8326b0342c8ca)
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Laurentiu Palcu
Andreas Müller
Ross Burton
Saul Wold
Constantin Musca
Marko Lindqvist
Jesse Zhang
Marcin Juszkiewicz
Li Wang
Hongxu Jia
Richard Purdie