From: Paolo Bonzini <pbonzini@redhat.com>
To: Roman Bolshakov <r.bolshakov@yadro.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"open list:Block layer core" <qemu-block@nongnu.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Max Reitz" <mreitz@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [PATCH] meson: Propagate gnutls dependency
Date: Mon, 4 Jan 2021 21:50:32 +0100 [thread overview]
Message-ID: <af0194cd-cdcc-44a3-f023-80d73d96c9e8@redhat.com> (raw)
In-Reply-To: <X/NPRqMkdM0/IxTh@SPB-NB-133.local>
On 04/01/21 18:24, Roman Bolshakov wrote:
> Hi Paolo,
>
> I'm sorry I didn't reply earlier. As I showed in an example to Peter
> (https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg00085.html):
> https://github.com/mesonbuild/meson/commit/ff5dc65ef841857dd306694dff1fb1cd2bf801e4
>
> The approach doesn't propogate dependencies of crypto beyond libcrypto.
> i.e. if you specify crypto somewhere else as depedency, it won't pull
> CFLAGS needed for gnutls.
Hi Roman,
After writing the meson patch in fact I noticed that get_dependencies()
is used only for linker flags. I got a very quick reply from the Meson
maintainer (https://github.com/mesonbuild/meson/pull/8151):
The fact that header flags are not passed transitively but libraries
are (in some cases) is intentional. Otherwise compiler flag counts
explode in deep hierarchies. Because of this include paths must be
exported manually, typically by adding the appropriate bits to a
declare_dependency.
Libs are a bit stupid, because you need to add direct dependencies
if, for example, you link to a static library.
Does it work if you do:
crypto_ss.add(authz, qom)
libcrypto = static_library('crypto', crypto_ss.sources() + genh,
dependencies: crypto_ss.dependencies(),
...)
crypto = declare_dependency(link_whole: libcrypto,
dependencies: crypto_ss.dependencies())
? If so, that is also a good option. If not, I will try to extend the
test case to pitch the Meson change.
Paolo
next prev parent reply other threads:[~2021-01-04 20:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 12:52 [PATCH] meson: Propagate gnutls dependency Roman Bolshakov
2021-01-02 13:25 ` Peter Maydell
2021-01-02 14:16 ` Roman Bolshakov
2021-01-02 19:43 ` Paolo Bonzini
2021-01-04 17:24 ` Roman Bolshakov
2021-01-04 20:50 ` Paolo Bonzini [this message]
2021-01-05 14:37 ` Roman Bolshakov
2021-01-05 17:41 ` Paolo Bonzini
2021-01-07 11:41 ` Paolo Bonzini
2021-01-07 15:56 ` Roman Bolshakov
2021-01-07 16:23 ` Paolo Bonzini
2021-01-07 18:18 ` Roman Bolshakov
2021-01-07 18:22 ` Paolo Bonzini
2021-01-07 19:36 ` Roman Bolshakov
2021-01-07 19:41 ` Paolo Bonzini
2021-01-08 19:29 ` Roman Bolshakov
2021-01-08 20:02 ` Paolo Bonzini
2021-01-04 12:21 ` Daniel P. Berrangé
2021-01-04 12:30 ` Paolo Bonzini
2021-01-04 13:21 ` Peter Maydell
2021-01-04 14:40 ` Paolo Bonzini
2021-01-04 15:19 ` Peter Maydell
2021-01-04 17:49 ` Paolo Bonzini
2021-01-04 17:51 ` 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=af0194cd-cdcc-44a3-f023-80d73d96c9e8@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.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).