On Fri, 22 May 2015 11:45:56 -0700
Bill Spitzak wrote:
> This seems like a good idea for consistency that the protocol header
> is included for any protocols used by the code. This also means the
> code will compile with headers generated by wayland-scanner -c.
>
> Fixed to use angle brackets.
>
Although it sounds like the distributed header files will not be
generated with -c, I don't see why local header files such as
ivi-application-client-protocol.h, ivi-hmi-controller-client-protocol.h,
and weston-test-client-protocol.h can't be and this patch allows that.
On 05/22/2015 11:45 AM,
This seems like a good idea for consistency that the protocol header
is included for any protocols used by the code. This also means the
code will compile with headers generated by wayland-scanner -c.
Fixed to use angle brackets.
---
clients/ivi-shell-user-interface.c |1 +
tests/weston-test-
On 05/22/2015 12:40 AM, Pekka Paalanen wrote:
On Thu, 21 May 2015 19:20:57 -0700
Bill Spitzak wrote:
This seems like a good idea for consistency as the client and server
protocol should not be treated differently than others. This means the
code will compile even if the protocol headers are
On Thu, 21 May 2015 19:20:57 -0700
Bill Spitzak wrote:
> This seems like a good idea for consistency as the client and server
> protocol should not be treated differently than others. This means the
> code will compile even if the protocol headers are generated with the
> core only (-c) switch.
This seems like a good idea for consistency as the client and server
protocol should not be treated differently than others. This means the
code will compile even if the protocol headers are generated with the
core only (-c) switch.
---
clients/ivi-shell-user-interface.c |1 +
tests/weston-tes
