[PATCH weston] configure.ac: honour the wayland-scanner.pc

Andrew Oakley aoakley at espial.com
Tue Feb 17 03:46:02 PST 2015

On 16/02/15 22:07, Daniel Stone wrote:
> Hi,
> On 16 February 2015 at 20:46, Bill Spitzak <spitzak at gmail.com> wrote:
>> I'm pretty certain there was an old version that looked in the PATH, but
>> this has the really unfortunate effect that the build does not work, you
>> have to manually create the wayland_scanner and put it in the path, then run
>> the build.
>> Would it be possible to search the path, and if not found, search the
>> install location? Anybody doing cross-compilation can the do the extra work
>> to put the build machine's wayland-scanner on the path, but somebody
>> building wayland for their own machine will get a working copy right away.

Yes, I think that would work in most environments (cross compiled or not).

> If they're building Weston on a machine which doesn't have the Wayland
> development libraries installed, they're going to need to have pointed
> PKG_CONFIG_PATH at a Wayland install anyway ...

So searching the install directory and looking for pc files will give
the same answer in most cases.  I don't think it matters which one you
do (and in the cross compiled case both will be wrong).

Note that the old behaviour described in this patch commit message is to
look in the path, then look in the pc files so no change would be
required (apart from possibly a comment explaining why).

More information about the wayland-devel mailing list