> > + if test "x$enable_glx" = xno; then > + AC_MSG_ERROR([cannot build libglvnd without GLX]) > + fi > + > + if test "x$enable_xlib_glx" = xyes; then > + AC_MSG_ERROR([cannot build libgvnd when Xlib-GLX is enabled]) > + fi >
This doesn't consider the gallium-xlib implementation. GLX configure options are specified differently now as of: a92910a glx: Refactor the configure options for glx implementation choice (v3) Basically all implementations are controlled via a single --enable-glx=implementation option. If you move the logic to after the enable_glx option is validated, the you are guaranteed it's value will be one of no, dri, xlib, or gallium-xlib. Your logic can then be: case "x$enable_glx" in xno) AC_MSG_ERROR([cannot build libglvnd without GLX]) ;; xxlib | xgallium-xlib ) AC_MSG_ERROR([cannot build libgvnd when Xlib-GLX or Gallium-Xlib-GLX is enabled]) ;; xdri) ;; esac
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
