wayland/wayland-scanner.m4

AC_DEFUN([WAYLAND_SCANNER_RULES], [
    PKG_PROG_PKG_CONFIG

    PKG_CHECK_MODULES([WAYLAND_SCANNER], [wayland-scanner >= 1.14.0])

    wayland_scanner=`$PKG_CONFIG --variable=wayland_scanner wayland-scanner`
    AC_SUBST([wayland_scanner])

    wayland_scanner_rules=`$PKG_CONFIG --variable=pkgdatadir wayland-scanner`/wayland-scanner.mk
    AC_SUBST_FILE([wayland_scanner_rules])

    AC_SUBST([wayland_protocoldir], [$1])
])
build: Add wayland-scanner.pc. To allow user program to include wayland-scanner.m4 in tarball, move the path variables from it into wayland-scanner.pc. 2013-07-02 18:38:15 +09:00			`AC_DEFUN([WAYLAND_SCANNER_RULES], [`
			`PKG_PROG_PKG_CONFIG`

build: check wayland-scanner version We need the --strict flag, released in wayland 1.14.0. Signed-off-by: Simon Ser <contact@emersion.fr> 2020-01-13 19:27:19 +01:00			`PKG_CHECK_MODULES([WAYLAND_SCANNER], [wayland-scanner >= 1.14.0])`
scanner: check for wayland-scanner.pc before using variables If wayland-scanner.pc can't be found the variables end up being set irrespectively, leaving the user with odd compiler errors about missing headers, etc. 2013-08-07 11:05:59 +10:00
build: Add wayland-scanner.pc. To allow user program to include wayland-scanner.m4 in tarball, move the path variables from it into wayland-scanner.pc. 2013-07-02 18:38:15 +09:00			wayland_scanner=`$PKG_CONFIG --variable=wayland_scanner wayland-scanner`
			`AC_SUBST([wayland_scanner])`

			wayland_scanner_rules=`$PKG_CONFIG --variable=pkgdatadir wayland-scanner`/wayland-scanner.mk
			`AC_SUBST_FILE([wayland_scanner_rules])`

			`AC_SUBST([wayland_protocoldir], [$1])`
			`])`