Re: [PATCH] build: always build wayland-scanner

Hi, On 17 July 2015 at 11:55, Burton, Ross wrote: > Bump. Lots of mails but no concrete acceptance or rejection. Rationale is solid to me. Applied, bikeshedded naming (with Ross's OK), tested, pushed. Cheers, Daniel > Ross > > On 1 July 2015 at 22:51, Ross Burton wrote: >> >> The previous id

Re: [PATCH] build: always build wayland-scanner

Bump. Lots of mails but no concrete acceptance or rejection. Ross On 1 July 2015 at 22:51, Ross Burton wrote: > The previous idiom for building a cross-compiled Wayland is to build once > for > the build host (with --enable-scanner --disable-libraries) to get a > wayland-scanner binary that ca

Re: [PATCH] build: always build wayland-scanner

On Mon, Jul 06, 2015 at 09:02:40PM +0100, Burton, Ross wrote: > On 6 July 2015 at 20:40, Bryce Harrington wrote: > > > An even cleaner solution would be to break the scanner out as a separate > > source package from libwayland. Then all this mess can be handled > > through normal package depende

Re: [PATCH] build: always build wayland-scanner

On 6 July 2015 at 20:40, Bryce Harrington wrote: > An even cleaner solution would be to break the scanner out as a separate > source package from libwayland. Then all this mess can be handled > through normal package dependencies. > For such a small tool with a fairly simple solution in cross c

Re: [PATCH] build: always build wayland-scanner

On Wed, Jul 01, 2015 at 10:51:01PM +0100, Ross Burton wrote: > The previous idiom for building a cross-compiled Wayland is to build once for > the build host (with --enable-scanner --disable-libraries) to get a > wayland-scanner binary that can then be used in a cross-compile (with > --disable-scan

Re: [PATCH] build: always build wayland-scanner

On 3 July 2015 at 17:16, Derek Foreman wrote: > What's the benefit in forcing everyone to build wayland-scanner? Right > now it's not required. Is there actually a reason this ability must be > broken to add the functionality you want? > Just realised you might be talking about cross environme

Re: [PATCH] build: always build wayland-scanner

On 3 July 2015 at 17:16, Derek Foreman wrote: > What's the benefit in forcing everyone to build wayland-scanner? Right > now it's not required. Is there actually a reason this ability must be > broken to add the functionality you want? > Considering a scanner is needed to build all of wayland,

Re: [PATCH] build: always build wayland-scanner

On 03/07/15 10:06 AM, Burton, Ross wrote: > On 3 July 2015 at 15:50, Derek Foreman > wrote: > > On 01/07/15 04:51 PM, Ross Burton wrote: > > The previous idiom for building a cross-compiled Wayland is to build > once for > > the build host (with --enabl

Re: [PATCH] build: always build wayland-scanner

On 3 July 2015 at 15:50, Derek Foreman wrote: > On 01/07/15 04:51 PM, Ross Burton wrote: > > The previous idiom for building a cross-compiled Wayland is to build > once for > > the build host (with --enable-scanner --disable-libraries) to get a > > wayland-scanner binary that can then be used in

Re: [PATCH] build: always build wayland-scanner

On 01/07/15 04:51 PM, Ross Burton wrote: > The previous idiom for building a cross-compiled Wayland is to build once for > the build host (with --enable-scanner --disable-libraries) to get a > wayland-scanner binary that can then be used in a cross-compile (with > --disable-scanner). The problem w

[PATCH] build: always build wayland-scanner

The previous idiom for building a cross-compiled Wayland is to build once for the build host (with --enable-scanner --disable-libraries) to get a wayland-scanner binary that can then be used in a cross-compile (with --disable-scanner). The problem with this is that the cross wayland is missing a w