From: Paolo Bonzini <pbonzini@redhat.com>
To: Chris Hofstaedtler <chris@hofstaedtler.name>, qemu-devel@nongnu.org
Subject: Re: [PATCH] meson: fix ncurses detection on macOS
Date: Thu, 7 Jan 2021 12:47:08 +0100 [thread overview]
Message-ID: <509d7467-3747-cbfd-61e2-f92f3a9c67f8@redhat.com> (raw)
In-Reply-To: <20201228151652.235542-1-chris@hofstaedtler.name>
On 28/12/20 16:16, Chris Hofstaedtler wrote:
> Without this, meson fails with "curses package not usable"
> when using ncurses 6.2. Apparently the wide functions
> (addwstr, etc) are hidden behind the extra define, and
> meson does not define it at that detection stage.
>
> Signed-off-by: Chris Hofstaedtler <chris@hofstaedtler.name>
> ---
> meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meson.build b/meson.build
> index 9c152a85bd..7b9d92c14a 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -510,7 +510,7 @@ if have_system and not get_option('curses').disabled()
> endforeach
> msg = get_option('curses').enabled() ? 'curses library not found' : ''
> if curses.found()
> - if cc.links(curses_test, dependencies: [curses])
> + if cc.links(curses_test, args: '-DNCURSES_WIDECHAR', dependencies: [curses])
> curses = declare_dependency(compile_args: '-DNCURSES_WIDECHAR', dependencies: [curses])
> else
> msg = 'curses package not usable'
>
Already fixed by commit 0dbce6efb5ff2e7113734d3a0cabbf87fc56feec
meson: fix detection of curses with pkgconfig
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Sorry for the delay in applying it.
Thanks,
Paolo
prev parent reply other threads:[~2021-01-07 11:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 15:16 [PATCH] meson: fix ncurses detection on macOS Chris Hofstaedtler
2020-12-28 17:20 ` Philippe Mathieu-Daudé
2020-12-28 17:53 ` Samuel Thibault
2020-12-28 19:50 ` 罗勇刚(Yonggang Luo)
2020-12-30 16:28 ` Peter Maydell
2021-01-07 11:47 ` Paolo Bonzini [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=509d7467-3747-cbfd-61e2-f92f3a9c67f8@redhat.com \
--to=pbonzini@redhat.com \
--cc=chris@hofstaedtler.name \
--cc=qemu-devel@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).