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

[Emil Velikov]

On 2 December 2016 at 14:55, Pekka Paalanen <ppaalanen at gmail.com> wrote:
> On Fri, 8 Jul 2016 11:29:16 +0100
> Emil Velikov <emil.l.velikov at gmail.com> wrote:
>
>> Hi all,
>>
>> Jumping the gun a bit, hope you'll forgive me :-)
>>
>> On 8 July 2016 at 09:17, Quentin Glidic <sardemff7+wayland at sardemff7.net> 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 newer mesa releases should include the generated files. Thus
>> one shouldn't need to use the tool, let alone have it.
>>
>> If anything I'd suggest pinging the respective projects to provide
>> complete/comprehensive release tarballs.
>
> Hi Emil,
>
> that would make the project release tar-ball depend on the libwayland
> version of the system where the tar-ball was created. Are you sure you
> want that?
>
Based on my understanding of how release tarball should behave - yes.

> You probably want to fix it in wayland-scanner instead, but that is not
> the reality today, yet. It only works because we haven't changed the
> scanner incompatibly for quite some time now.
>
> I suppose this is the reason you wanted to have the versioning options
> in wayland-scanner. It never occurred to me that people would be
> shipping the generated files. You don't put them into VCS either, and
> Weston takes care to not ship them.
>
There's a couple of ideas which come to mind, why Weston does not ship
the files:
 - Thinko ? Similar to how the interface symbols are _explicitly_
exported while devs lean that each project should have them
statically.
 - The API/ABI generated by wayland-scanner is intentionally meant to
be fluid ? Seriously doubt this is the case.

And yes this is one example/reason why we want the scanner to provide
a consistent API/ABI/other. Unless the user explicitly opts out.

Thanks
Emil