On Mon, Apr 09, 2018 at 04:23:23PM +0800, Peter Xu wrote:
> We don't need to detect GTK ABI if GTK is disabled in general.
> Otherwise we could get this warning (when host is installed with GTK ABI
> version 2) even when configure with "--disable-gtk":
>
> WARNING: Use of GTK 2.0 is deprecated
On Mon, Apr 09, 2018 at 07:37:11PM +0200, Paolo Bonzini wrote:
> On 09/04/2018 11:24, Peter Maydell wrote:
> > On 9 April 2018 at 09:31, Daniel P. Berrangé wrote:
> >> Feels to me that since we've deprecated 2.0, we could just *never* auto
> >> detect - just do test -z "$gtkabi" && gtkabi=3.0
On 09/04/2018 11:24, Peter Maydell wrote:
> On 9 April 2018 at 09:31, Daniel P. Berrangé wrote:
>> Feels to me that since we've deprecated 2.0, we could just *never* auto
>> detect - just do test -z "$gtkabi" && gtkabi=3.0
>>
>> Anyone who wants gtk2 should have to use an explicit --with-gtkab
On 9 April 2018 at 09:31, Daniel P. Berrangé wrote:
> Feels to me that since we've deprecated 2.0, we could just *never* auto
> detect - just do test -z "$gtkabi" && gtkabi=3.0
>
> Anyone who wants gtk2 should have to use an explicit --with-gtkabi=2.0
I think if we still work with gtk2 then w
On Mon, Apr 09, 2018 at 04:23:23PM +0800, Peter Xu wrote:
> We don't need to detect GTK ABI if GTK is disabled in general.
> Otherwise we could get this warning (when host is installed with GTK ABI
> version 2) even when configure with "--disable-gtk":
>
> WARNING: Use of GTK 2.0 is deprecated
We don't need to detect GTK ABI if GTK is disabled in general.
Otherwise we could get this warning (when host is installed with GTK ABI
version 2) even when configure with "--disable-gtk":
WARNING: Use of GTK 2.0 is deprecated and will be removed in
WARNING: future releases. Please switch