On 10/02/15 14:42, Emil Velikov wrote: > Currently we use the wayland-scanner executable as found with > AC_PATH_PROG, and after that check the presence of wayland-scanner.pc > > Even if the latter is pointing to another wayland-scanner we silently > ignore it. Rework things to check for the relevant variable in the *.pc > file first, and then fall back to checking via AC_PATH_PROG.
I'm not sure this works when cross compiling. What you really want to do is look for wayland-scanner on the build machine rather than the target. With these changes we will try and run wayland-scanner for the target (assuming it has been built). It doesn't look like there is currently any way of using the m4 macros shipped with pkg-config to run the right one. For now I think it is better to just look in PATH, although getting the feature into the pkg-config m4 scripts and then using it would be good in future. _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
