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 *.
Ok.
At least I can use USE_HOST_SCANNER variable or continue to patch Wayland
Makefiles. That is not a problem for me.
Best Regards,
Andrey K.
On Mon, Dec 5, 2016 at 3:23 PM, Pekka Paalanen wrote:
> On Mon, 5 Dec 2016 14:13:23 +0300
> Andrew Kosteltsev wrote:
>
> > Hi guys,
u'll forgive me :-)
> > >>
> > >> On 8 July 2016 at 09:17, Quentin Glidic net> wrote:
> > >> > On 18/05/2016 14:55, Andrew Kosteltsev wrote:
> > >>
> > >> >> Then the user can make use this cross-wayland-scanner in his SDK,
17 AM, Quentin Glidic <
sardemff7+wayl...@sardemff7.net> 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
&g
Of course, not an old lib with a never scanner! only the same.
On Fri, Jul 8, 2016 at 12:24 PM, Quentin Glidic <
sardemff7+wayl...@sardemff7.net> wrote:
> On 08/07/2016 10:46, Andrew Kosteltsev wrote:
>
>> Hi Quentin.
>>
>> I see. My suggestion related to simplify
wrote:
> On 18/05/2016 14:55, Andrew Kosteltsev wrote:
>> 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
>>
Afaict
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 du
