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

Andrew Kosteltsev kosteltsev at
Fri Jul 8 08:46:20 UTC 2016

Hi Quentin.

I see. My suggestion related to simplify the build process on developer
machines which doesn't have pre-installed native Wayland package. And also
I think it would be good if wailand-scanner output will be generated by
scanner which has the same version as target machine scanner.

Currently developers must have installed wayland package and it is not
convenient if developer builds several targets for different CPU (and may
be different versions of some SW packages) at the same time using cross

(for example, GNU file also requires native file utility on developer
machine, moreover it must have same version). I think not all needed tools
can be implemented into toolchain like cross-compiler. Some of them can be
built and added into DevEnv later on build time.

Any way It is up to you. I just suggest.

Best Regards,
Andrey K.

On Fri, Jul 8, 2016 at 11:17 AM, Quentin Glidic <
sardemff7+wayland at> wrote:

> On 18/05/2016 14:55, Andrew Kosteltsev wrote:
>> Hi guys,
>> Currently during cross compilation of the wayland library the
>> wayland-scanner utility is built by cross-gcc and then used on the
>> developer machine which lead build error.
>> I suggest to build development version, for example,
>> $(top_builddir)/build-wayland-scanner and to use this utility during
>> cross-buildin the wayland package.
>> When build is done the user can copy this release of scanner utility
>> into his toolchain or into his SDK for example wit $(host-triplet) preffix
>> cp $(top_builddir)/build-wayland-scanner
>> SDK/bin/$(host_triplet)-wayland-scanner
>> Then the user can make use this cross-wayland-scanner in his SDK, for
>> example, like follow:
>> $ ../MesaLib-10.3.4/configure
>> WAILAND_SCANNER=$(SDK_DIR)/bin/$(target)-wayland-scanner
>> I have attached the patch for you. Please look at this patch and please
>> make decision related to cross building the wayland.
>> Of course after applying attached patch we have to reconfigure src
>> package;
>> $ autoreconf -i
> NAK from me on this patch.
> wayland-scanner does not output host-specific code, so you should simply
> use the one in the PATH of your build machine, via --with-host-scanner.
> Cheers,
> --
> Quentin “Sardem FF7” Glidic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the wayland-devel mailing list