From: Samuel Thibault <samuel.thibault@gnu.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: pbonzini@redhat.com, Yonggang Luo <luoyonggang@gmail.com>,
qemu-devel@nongnu.org,
Chris Hofstaedtler <chris@hofstaedtler.name>
Subject: Re: [PATCH] meson: fix ncurses detection on macOS
Date: Mon, 28 Dec 2020 18:53:52 +0100 [thread overview]
Message-ID: <20201228175352.4jkugx4umznygooe@function> (raw)
In-Reply-To: <ad2133a5-522d-b283-9abb-4c07e790c233@redhat.com>
Philippe Mathieu-Daudé, le lun. 28 déc. 2020 18:20:13 +0100, a ecrit:
> On 12/28/20 4:16 PM, 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.
>
> Seems reasonable, but still Cc'ing more developers.
That looks sensible indeed.
> > 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'
next prev parent reply other threads:[~2020-12-28 17:55 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 [this message]
2020-12-28 19:50 ` 罗勇刚(Yonggang Luo)
2020-12-30 16:28 ` Peter Maydell
2021-01-07 11:47 ` Paolo Bonzini
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=20201228175352.4jkugx4umznygooe@function \
--to=samuel.thibault@gnu.org \
--cc=chris@hofstaedtler.name \
--cc=luoyonggang@gmail.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--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).