On 4 September 2017 at 07:31, Gerd Hoffmann <kra...@redhat.com> wrote: > Hi, > >> > diff --git a/configure b/configure >> > index dd73cce62f..73760430b0 100755 >> > --- a/configure >> > +++ b/configure >> > @@ -930,8 +930,6 @@ for opt do >> > ;; >> > --with-system-pixman) pixman="system" >> >> Is there any use case for '--with-system-pixman now? > > There is "--without-pixman" (so you can turn off pixman if you don't > want build the system emulation). So IMHO it makes sense to leave the > opposite switch in. The name is a bit strange now, but changing it > might break build scripts, so I left it as-is. Maybe configure should > accept both "--with-pixman" and "--with-system-pixman"?
There's an argument that we don't need any configure options for pixman any more: * if you're not building the system emulation then we can just automatically skip the pixman check * if you are building the system emulation then we need a pixman and have to complain if it doesn't exist The usual reason for a --with-foo is for the "if foo doesn't exist then we can still build but with some feature disabled", in which case distros want to be able to say "fail if foo not present rather than proceeding in degraded mode". That doesn't apply for pixman. (We don't have a --with-glib flag either). This patch passed on all my build-test machines and configs, which surprised me a bit but is good news as it suggests that system pixman is present pretty much everywhere :-) thanks -- PMM
