From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/7] ui patch queue
Date: Tue, 13 Jun 2017 09:26:28 +0100 [thread overview]
Message-ID: <CAFEAcA-yoQuDtKx-hePwCh47S6Um7_nxcdXLiQKUQN5=eHm7Sg@mail.gmail.com> (raw)
In-Reply-To: <4a61a587-6dff-e5fd-58aa-fd168e27f876@redhat.com>
On 13 June 2017 at 06:14, Thomas Huth <thuth@redhat.com> wrote:
> On 12.06.2017 20:08, Peter Maydell wrote:
>> On 12 June 2017 at 19:00, Peter Maydell <peter.maydell@linaro.org> wrote:
>>> This causes configure to barf warnings in my build logs on half
>>> my build machines:
>>>
>>> WARNING: Support for gtk2 will be dropped in future releases.
>>> WARNING: Please consider using gtk3 instead.
>>>
>>> I don't think it is yet possible to drop gtk2.
>>
>> Oh, one of them was the warning about SDL1.2.
>
> Adding the warning does not necessarily mean that we've really got to
> drop support for these in the very near future, but it's a good start to
> remind people that support for the old versions won't be around forever
> ;-) And AFAIK the old versions of these libraries are not maintained by
> the upstream projects anymore, too, so at one point in time, we've
> really got to deprecate support for these in QEMU, too.
>
> So would it at least be feasible to install SDL 2 on that build
> machines? (IMHO installing SDL 2 from sources is not too much of a pain,
> e.g. it does not require lots of other additional libraries around)
Yes, I'll circle back and have a look at whether it's just a matter
of installing an extra -dev package. If it's necessary to build from
source then it's definitely too early to deprecate though.
(Mostly if I have a long pullreq queue than printing warning messages
in my build logs is a good way to get your pull request pushed to
the end of the todo list :-))
thanks
-- PMM
next prev parent reply other threads:[~2017-06-13 8:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 7:07 [Qemu-devel] [PULL 0/7] ui patch queue Gerd Hoffmann
2017-06-08 7:07 ` [Qemu-devel] [PULL 1/7] Improve Cocoa modifier key handling Gerd Hoffmann
2017-06-08 7:07 ` [Qemu-devel] [PULL 2/7] spice: Use proper enum type for kbd led state Gerd Hoffmann
2017-06-08 7:07 ` [Qemu-devel] [PULL 3/7] gtk: prefer gtk3 over gtk2 Gerd Hoffmann
2017-06-08 7:07 ` [Qemu-devel] [PULL 4/7] sdl: prefer sdl2 over sdl1 Gerd Hoffmann
2017-06-08 7:07 ` [Qemu-devel] [PULL 5/7] gtk: add deprecation warning for gtk2 Gerd Hoffmann
2017-06-08 7:07 ` [Qemu-devel] [PULL 6/7] sdl: add deprecation warning for sdl1 Gerd Hoffmann
2017-06-08 7:07 ` [Qemu-devel] [PULL 7/7] spice: don't enter opengl mode in case another UI provides opengl support Gerd Hoffmann
2017-06-12 18:00 ` [Qemu-devel] [PULL 0/7] ui patch queue Peter Maydell
2017-06-12 18:08 ` Peter Maydell
2017-06-13 5:14 ` Thomas Huth
2017-06-13 8:26 ` Peter Maydell [this message]
2017-06-13 10:41 ` Gerd Hoffmann
2017-06-15 12:41 ` Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2016-06-03 7:04 Gerd Hoffmann
2016-06-03 12:04 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFEAcA-yoQuDtKx-hePwCh47S6Um7_nxcdXLiQKUQN5=eHm7Sg@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).