On 16 February 2015 at 13:04, Andrew Oakley <[email protected]> wrote: > 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). > Imho one should not build/install wayland-scanner for the target machine. It makes little to no sense considering it's designed/meant to be ran at build time. That said I'm not familiar with the way people handle/build wayland so my thinking may be a bit off :P
That aside - the common direction is towards checking via AC_PATH_PROG and using the wayland-scanner.pc as a fall-back. So let's cook something up. -Emil _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
