From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v2 0/3] buildsys: Move crypto libraries to per object variables
Date: Wed, 6 Sep 2017 09:27:12 +0800 [thread overview]
Message-ID: <20170906012715.31761-1-famz@redhat.com> (raw)
v2: Add gcrypt as well. [Daniel]
Not all targets need the flags and libs of gcrypt/nettle/gnutls, so move them
out from global variables, as done with other libraries.
There are still other libraries in ./configure that can be converted this way,
which will be sent separatedly.
Fam Zheng (3):
buildsys: Move nettle cflags/libs to per object
buildsys: Move gnutls cflags/libs to per object
buildsys: Move gcrypt cflags/libs to per object
configure | 14 ++++++--------
crypto/Makefile.objs | 20 ++++++++++++++++++++
tests/Makefile.include | 10 +++++-----
3 files changed, 31 insertions(+), 13 deletions(-)
--
2.13.5
next reply other threads:[~2017-09-06 1:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 1:27 Fam Zheng [this message]
2017-09-06 1:27 ` [Qemu-devel] [PATCH v2 1/3] buildsys: Move nettle cflags/libs to per object Fam Zheng
2017-09-06 1:27 ` [Qemu-devel] [PATCH v2 2/3] buildsys: Move gnutls " Fam Zheng
2017-09-06 7:38 ` Fam Zheng
2017-09-06 1:27 ` [Qemu-devel] [PATCH v2 3/3] buildsys: Move gcrypt " Fam Zheng
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=20170906012715.31761-1-famz@redhat.com \
--to=famz@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).