From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-trivial@nongnu.org
Subject: Re: [PATCH v2] meson.build: Use -Wno-undef only for SDL2 versions that need it
Date: Mon, 5 Jun 2023 10:58:11 +0200 [thread overview]
Message-ID: <96223e15-c17e-21f5-3ed4-464e3055d332@redhat.com> (raw)
In-Reply-To: <ZH2ic6zsehZzRC/u@redhat.com>
On 05/06/2023 10.53, Daniel P. Berrangé wrote:
> On Fri, Jun 02, 2023 at 06:34:52PM +0200, Thomas Huth wrote:
>> There is no need to disable this useful compiler warning for
>> all versions of the SDL. Unfortunately, various versions are
>> buggy (beside SDL 2.0.8, the version 2.26.0 and 2.26.1 are
>> broken, too, see https://github.com/libsdl-org/SDL/issues/6619 ),
>> but we can use a simple compiler check to see whether we need
>> the -Wno-undef or not.
>>
>> This also enables the printing of the version number with
>> good versions of the SDL in the summary of the meson output
>> again.
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> v2: Compile test code instead of hard-coding the version number
>>
>> meson.build | 14 ++++++++++----
>> 1 file changed, 10 insertions(+), 4 deletions(-)
>>
>> diff --git a/meson.build b/meson.build
>> index a61d3e9b06..a4c69616c3 100644
>> --- a/meson.build
>> +++ b/meson.build
>> @@ -1273,10 +1273,16 @@ if not get_option('sdl').auto() or have_system
>> sdl_image = not_found
>> endif
>> if sdl.found()
>> - # work around 2.0.8 bug
>> - sdl = declare_dependency(compile_args: '-Wno-undef',
>> - dependencies: sdl,
>> - version: sdl.version())
>> + # Some versions of SDL have problems with -Wundef
>> + if not cc.compiles('''
>> + #include <SDL.h>
>> + #include <SDL_syswm.h>
>> + int main(int argc, char *argv[]) { return 0; }
>> + ''', dependencies: sdl, args: '-Wundef')
>
> Don't you need to pass '-Werror' there too, otherwise -Wundef will
> merely generate an warning and still succeed.
Of course! Thank you very much ... not sure how I could have missed that
detail :-/
Thomas
prev parent reply other threads:[~2023-06-05 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 16:34 [PATCH v2] meson.build: Use -Wno-undef only for SDL2 versions that need it Thomas Huth
2023-06-03 3:30 ` Richard Henderson
2023-06-05 7:46 ` Thomas Huth
2023-06-05 8:27 ` Paolo Bonzini
2023-06-05 8:47 ` Thomas Huth
2023-06-05 9:05 ` Paolo Bonzini
2023-06-05 9:48 ` Paolo Bonzini
2023-06-05 8:53 ` Daniel P. Berrangé
2023-06-05 8:58 ` Thomas Huth [this message]
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=96223e15-c17e-21f5-3ed4-464e3055d332@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
/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).