On 30 September 2017 at 14:45, Otavio Salvador <
otavio.salva...@ossystems.com.br> wrote:
> On Sat, Sep 30, 2017 at 10:43 AM, Fabien Lahoudere
> wrote:
> > On Fri, 2017-09-29 at 11:32 +0100, Burton, Ross wrote:
> >
> > With xserver-xorg I get:
> >
> > | make[2]:
On Sat, Sep 30, 2017 at 10:43 AM, Fabien Lahoudere
wrote:
> On Fri, 2017-09-29 at 11:32 +0100, Burton, Ross wrote:
>
> With xserver-xorg I get:
>
> | make[2]: *** No rule to make target
>
On Fri, 2017-09-29 at 11:32 +0100, Burton, Ross wrote:
> With xserver-xorg I get:
> | make[2]: *** No rule to make target
> '//usr/share/wayland-protocols/unstable/relative-
> pointer/relative-pointer-unstable-v1.xml', needed by
> 'relative-pointer-unstable-v1-client-
> protocol.h'. Stop.
>
>
With xserver-xorg I get:
| make[2]: *** No rule to make target
'//usr/share/wayland-protocols/unstable/relative-pointer/relative-pointer-unstable-v1.xml',
needed by 'relative-pointer-unstable-v1-client-protocol.h'. Stop.
(in the xwayland directory)
Ross
On 28 September 2017 at 17:01, Fabien
this is a good patch. Thanks
On Thu, Sep 28, 2017 at 9:01 AM, Fabien Lahoudere
wrote:
> This patch modify the way we manage wayland path issues.
> Instead of patching each recipe to make it work with wayland and its
> protocols,
> it is better to patch wayland
This patch modify the way we manage wayland path issues.
Instead of patching each recipe to make it work with wayland and its protocols,
it is better to patch wayland to fix its path issues.
So wayland-scanner.pc, wayland-client.pc and wayland-protocols.pc are patched
to change paths.
Then we