configure should FAIL when --enable-wayland requirements can't be met #68
Labels
Comments
|
Same rules should apply for --enable-drm --enable-x11 --enable-glx --enable-egl |
xhaihao
referenced
this issue
in xhaihao/libva
Jun 20, 2017
Notify user an error if user provides --enable-x11/--enable-glx/--enable-egl/--enable-wayland however the requirement can't be met. drm has been checked mandatorily in the script v2: Remove XEXT_CFLAGS/XFIXES_CFLAGS from va/x11/Makefile.am and use $X11_PKG_ERRORS in the error message if the requirement is met for VA/X11 This fixes https://github.com/01org/libva/issues/68 Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com> Reviewed-by: U. Artie Eoff <ullysses.a.eoff@intel.com>
xhaihao
referenced
this issue
Aug 16, 2017
Notify user an error if user provides --enable-x11/--enable-glx/--enable-egl/--enable-wayland however the requirement can't be met. drm has been checked mandatorily in the script v2: Remove XEXT_CFLAGS/XFIXES_CFLAGS from va/x11/Makefile.am and use $X11_PKG_ERRORS in the error message if the requirement is met for VA/X11 This fixes https://github.com/01org/libva/issues/68 Signed-off-by: Xiang, Haihao <haihao.xiang@intel.com> Reviewed-by: U. Artie Eoff <ullysses.a.eoff@intel.com> (cherry picked from commit b9a72b9)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, configure silently disables wayland support if requirements cannot be met, even when the user explicitly requests it via
--enable-wayland. If the user does not explicitly request it, then silently disabling it is ok. However, when the user explicitly provides--enable-waylandto configure, configure should fail if wayland requirements/dependencies can't be met.The text was updated successfully, but these errors were encountered: