Create cross wayland-scanner for toolchain or cross-development environment

[Andrew Kosteltsev]

I think now the simplest way to fix cross-builder's problem is that:

When the  USE_HOST_SCANNER variable is set we have to allow to redefine
wayland_scanner variable in the same way as CC or CC_FOR_BUILD. For example
by command line arguments:

WAYLAND_SCANNER_FOR_BUILD=/usr/bin/wayland-scanner *./configure*
--prefix=/usr --use-host-scanner=yes

or

WAYLAND_SCANNER=/usr/bin/wayland-scanner *./configure* --prefix=/usr
--use-host-scanner=yes

In this case we can avoid building errors (without patching) related to
using scanner built (right now) for target machine on the development host.

Best Regards,
Andrey K.





On Tue, Dec 6, 2016 at 6:18 PM, Emil Velikov <emil.l.velikov at gmail.com>
wrote:

> Yes I fully agree that things are not perfect atm, and we want to work
> towards improving things.
> I'll see to "polishing" the scanner as early as possible.
>
> Thanks
> Emil
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-devel/attachments/20161206/b3d8956b/attachment.html>