openembedded-core.git/meta/recipes-graphics, branch uninative-1.4 Mirror of openembedded-core encodings: Add dependency to mkfontdir-native 2016-09-23T13:55:17+00:00 Gratian Crisan gratian.crisan@ni.com 2016-09-21T18:40:25+00:00 aa8a7b2962f9a77bdd347843c41f86dc291b783e Currently adding a font recipe to an image doesn't have enough dependencies to cause mkfontdir-native to be included in the native sysroot. This creates problems with the postinstall scripts for fonts which call mkfontdir to create font index files: font.dir. The end result is missing font.dir files in the built image and a malfunctioning font system. Dependencies for the relevant recipes currently look like this: * <font.bb> [D ] -> font-util-native [R ] -> encodings, font-util [RN] -> font-util-native * font-util [D ] -> encodings [R ] -> mkfontdir, mkfontscale, encodings [RN] -> mkfontdir-native, mkfontscale-native * encodings [D ] -> mkfontscale-native, font-util-native * mkfontdir [R ] -> mkfontscale [RN] -> mkfontscale-native * mkfontscale [D ] -> libfontenc * libfontenc [D ] -> font-util Where: * D = DEPENDS * R = RDEPENDS * RN = RDEPENDS_class-native * <font.bb> e.g. font-adobe-100dpi*.bb Some details where omitted for clarity e.g. dependencies on util-macros. I believe the intent behind the RDEPENDS_class-native chain: * <font.bb> -> font-util-native -> mkfontdir-native was to provide the necessary dependency on mkfontdir. However because the native sysroot is not built from packages this RDEPENDS_class-native chain doesn't have the desire effect (i.e. it doesn't pull in mkfontdir-native). Changing the RDEPENDS_class-native chain into a DEPENDS_class-native chain is a non-starter because of the build time dependency loop it creates: * font-util-native -> mkfontscale-native -> libfontenc-native -> font-util-native Having upstream remove the build time dependency of libfontenc on font-util is also a non-starter[1] even though it does create problems in other distributions, for example on Debian see [2], [3]. Instead add a DEPENDS on mkfontdir-native in the encodings recipe in addition to the mkfontscale-native dependency it already contains. This solves the missing mkfontdir in the native sysroot problem without introducing a build dependency loop. [1] https://bugs.freedesktop.org/show_bug.cgi?id=97631 [2] https://wiki.debian.org/CircularBuildDependencies [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717843 Signed-off-by: Gratian Crisan <gratian.crisan@ni.com> Signed-off-by: Ross Burton <ross.burton@intel.com> 
Currently adding a font recipe to an image doesn't have enough
dependencies to cause mkfontdir-native to be included in the native
sysroot. This creates problems with the postinstall scripts for fonts
which call mkfontdir to create font index files: font.dir. The end
result is missing font.dir files in the built image and a malfunctioning
font system.

Dependencies for the relevant recipes currently look like this:

  * <font.bb>   [D ] -> font-util-native
                [R ] -> encodings, font-util
                [RN] -> font-util-native

  * font-util   [D ] -> encodings
                [R ] -> mkfontdir, mkfontscale, encodings
                [RN] -> mkfontdir-native, mkfontscale-native

  * encodings   [D ] -> mkfontscale-native, font-util-native

  * mkfontdir   [R ] -> mkfontscale
                [RN] -> mkfontscale-native

  * mkfontscale [D ] -> libfontenc

  * libfontenc  [D ] -> font-util

Where:
  * D = DEPENDS
  * R = RDEPENDS
  * RN = RDEPENDS_class-native
  * <font.bb> e.g. font-adobe-100dpi*.bb
Some details where omitted for clarity e.g. dependencies on util-macros.

I believe the intent behind the RDEPENDS_class-native chain:
  * <font.bb> -> font-util-native -> mkfontdir-native
was to provide the necessary dependency on mkfontdir. However because
the native sysroot is not built from packages this RDEPENDS_class-native
chain doesn't have the desire effect (i.e. it doesn't pull in
mkfontdir-native).

Changing the RDEPENDS_class-native chain into a DEPENDS_class-native
chain is a non-starter because of the build time dependency loop it
creates:
  * font-util-native -> mkfontscale-native -> libfontenc-native -> font-util-native

Having upstream remove the build time dependency of libfontenc on
font-util is also a non-starter[1] even though it does create problems
in other distributions, for example on Debian see [2], [3].

Instead add a DEPENDS on mkfontdir-native in the encodings recipe in
addition to the mkfontscale-native dependency it already contains. This
solves the missing mkfontdir in the native sysroot problem without
introducing a build dependency loop.

[1] https://bugs.freedesktop.org/show_bug.cgi?id=97631
[2] https://wiki.debian.org/CircularBuildDependencies
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717843

Signed-off-by: Gratian Crisan <gratian.crisan@ni.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
xserver-xorg: fix qa warnings 2016-09-23T13:53:55+00:00 Kai Kang kai.kang@windriver.com 2016-09-22T10:04:24+00:00 5f94d2dd7a16ae9f327c88636822539f79e983eb When build lib32-xserver-xorg it has qa warning: | WARNING: lib32-xserver-xorg-2_1.18.4-r0 do_package_qa: QA Issue: | Package lib32-xf86-video-modesetting contains Xorg driver | (modesetting_drv.so) but no xorg-abi- dependencies [xorg-driver-abi] The qa check xorg-driver-abi has been skipped for xserver-xorg and make it to skip for multilib package too. Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
When build lib32-xserver-xorg it has qa warning:

| WARNING: lib32-xserver-xorg-2_1.18.4-r0 do_package_qa: QA Issue:
| Package lib32-xf86-video-modesetting contains Xorg driver
| (modesetting_drv.so) but no xorg-abi- dependencies [xorg-driver-abi]

The qa check xorg-driver-abi has been skipped for xserver-xorg and make
it to skip for multilib package too.

Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
libdrm: Explicitly disable cunit tests 2016-09-14T21:20:06+00:00 Jussi Kukkonen jussi.kukkonen@intel.com 2016-09-13T08:46:41+00:00 cd287235fc5b9d0c174a10a89e31ffd391806113 Add patch to control building cunit-tests explicitly. Disable them in the recipe. Fixes [YOCTO #9849]. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Add patch to control building cunit-tests explicitly. Disable
them in the recipe.

Fixes [YOCTO #9849].

Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
piglit: Backport linker flag patch 2016-09-14T21:20:05+00:00 Jussi Kukkonen jussi.kukkonen@intel.com 2016-09-13T08:46:40+00:00 cd67959c4794b132cb9fd20a2a37cf862e172bed Use the correct build system patch instead of adding linker flags in recipe. Also update upstream status for the other build patch. Fixes [YOCTO #9851]. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Use the correct build system patch instead of adding linker flags
in recipe. Also update upstream status for the other build patch.

Fixes [YOCTO #9851].

Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
clutter-1.0: do not use the prepackaged clutter.types file when generating gtk-doc 2016-09-09T11:12:17+00:00 Alexander Kanavin alexander.kanavin@linux.intel.com 2016-09-02T11:39:10+00:00 98a9a30abdc7b877be574ac5914ec02f16c00887 Doing so will fail when x11 is disabled in particular. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> 
Doing so will fail when x11 is disabled in particular.

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
pango: fix gtk-doc build when x11 is not in use 2016-09-09T11:12:17+00:00 Alexander Kanavin alexander.kanavin@linux.intel.com 2016-09-02T11:15:48+00:00 516d1a797d56e2753cbdd596387724f933350122 Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> 
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
harfbuzz: enable gtk-doc 2016-09-09T11:12:16+00:00 Alexander Kanavin alexander.kanavin@linux.intel.com 2016-08-25T15:03:38+00:00 014c55e09764052f30c43390aa4ea3e604ea7760 Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> 
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
cairo: enable gtk-doc 2016-09-09T11:12:16+00:00 Alexander Kanavin alexander.kanavin@linux.intel.com 2016-08-25T15:03:19+00:00 60c10d8c07c92e3b275a2cc422b9013cbcf3c93a Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> 
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
x11-common: Remove Xserver script 2016-09-08T07:25:18+00:00 Jussi Kukkonen jussi.kukkonen@intel.com 2016-08-30T08:32:09+00:00 877851cf0f76a5052900954670fb64aed27a7a1f X startup is now handled in xserver-nodm-init. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
X startup is now handled in xserver-nodm-init.

Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
xserver-nodm-init: Deprecate /etc/X11/Xserver 2016-09-08T07:25:18+00:00 Jussi Kukkonen jussi.kukkonen@intel.com 2016-09-01T06:53:04+00:00 e8ce3d2626e505924a75de96650abca166fd230a This commit should provide the same functionality as before, but should make meta-oe xserver-nodm-init-2.0 obsolete as well as keep systemd and sysvinit startup better in sync. /etc/X11/Xserver is not called anymore: it is provided by both x11-common and xserver-common with no useful differences (but some annoying ones). Instead xserver-nodm-init provides /etc/xserver-nodm/Xserver as the startup script and /etc/default/xserver-nodm as the default settings file. These are used by both init systems. The Xserver script could be completely removed (with sysv and systemd calling xinit directly), but to keep compatibility with meta-oes xserver-nodm-init-2.0 the Xserver script sources /etc/X11/xserver-common if one exists -- and systemd EnvironmentFile cannot do that. x11-common used to have a packageconfig to easily control screen blanking. Move this to xserver-nodm-init. Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
This commit should provide the same functionality as before, but
should make meta-oe xserver-nodm-init-2.0 obsolete as well as
keep systemd and sysvinit startup better in sync.

/etc/X11/Xserver is not called anymore: it is provided by both
x11-common and xserver-common with no useful differences (but some
annoying ones). Instead xserver-nodm-init provides
/etc/xserver-nodm/Xserver as the startup script and
/etc/default/xserver-nodm as the default settings file. These are
used by both init systems.

The Xserver script could be completely removed (with sysv and
systemd calling xinit directly), but to keep compatibility with
meta-oes xserver-nodm-init-2.0 the Xserver script sources
/etc/X11/xserver-common if one exists -- and systemd EnvironmentFile
cannot do that.

x11-common used to have a packageconfig to easily control screen
blanking. Move this to xserver-nodm-init.

Signed-off-by: Jussi Kukkonen <jussi.kukkonen@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>