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 *.
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
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freede
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,
> >
> > This is
On Mon, 5 Dec 2016 14:13:23 +0300
Andrew Kosteltsev wrote:
> Hi guys,
>
> This is no versioning question. I think when the host,target is not equal
> to build (I mean configure options --build,--taget,--host) we can compile
> two scanners:
Sorry, indeed, this thread was hijacked for the version
Hi guys,
This is no versioning question. I think when the host,target is not equal
to build (I mean configure options --build,--taget,--host) we can compile
two scanners:
1) scanner built by cross compiler and has original name (wayland-scanner)
2) scanner built by BUILD_CC and has complex name,
On Fri, 2 Dec 2016 17:06:29 +
Emil Velikov wrote:
> On 2 December 2016 at 14:55, Pekka Paalanen wrote:
> > On Fri, 8 Jul 2016 11:29:16 +0100
> > Emil Velikov wrote:
> >
> >> Hi all,
> >>
> >> Jumping the gun a bit, hope you'll forgive me :-)
> >>
> >> On 8 July 2016 at 09:17, Quentin Glid
On 2 December 2016 at 14:55, Pekka Paalanen wrote:
> On Fri, 8 Jul 2016 11:29:16 +0100
> Emil Velikov wrote:
>
>> Hi all,
>>
>> Jumping the gun a bit, hope you'll forgive me :-)
>>
>> On 8 July 2016 at 09:17, Quentin Glidic
>> wrote:
>> > On 18/05/2016 14:55, Andrew Kosteltsev wrote:
>>
>> >> T
On Fri, 8 Jul 2016 11:24:15 +0200
Quentin Glidic wrote:
> On 08/07/2016 10:46, Andrew Kosteltsev wrote:
> > 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 wou
On Fri, 8 Jul 2016 11:29:16 +0100
Emil Velikov wrote:
> Hi all,
>
> Jumping the gun a bit, hope you'll forgive me :-)
>
> On 8 July 2016 at 09:17, Quentin Glidic
> wrote:
> > On 18/05/2016 14:55, Andrew Kosteltsev wrote:
>
> >> Then the user can make use this cross-wayland-scanner in his S
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.
Curr
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 the build process on developer
>
Hi Emil,
Unfortunattely Mesa-11.2.2 still requires wayland-scanner. But I will check
it again.
Best Regards,
Andrey K.
8 июля 2016 г. 13:29 пользователь "Emil Velikov"
написал:
Hi all,
Jumping the gun a bit, hope you'll forgive me :-)
On 8 July 2016 at 09:17, Quentin Glidic
wrote:
> On 18/05
Hi all,
Jumping the gun a bit, hope you'll forgive me :-)
On 8 July 2016 at 09:17, Quentin Glidic 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
>> WAILA
On 08/07/2016 10:46, Andrew Kosteltsev wrote:
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 t
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)/
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
16 matches
Mail list logo
