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
_______________________________________________
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
