From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-block@nongnu.org, "Max Reitz" <mreitz@redhat.com>
Subject: [PATCH v2 0/3] nbd: build qemu-nbd on Windows
Date: Tue, 25 Aug 2020 11:38:47 +0100 [thread overview]
Message-ID: <20200825103850.119911-1-berrange@redhat.com> (raw)
We are already building the NBD client and server on Windows when it is
used via the main system emulator binaries. This demonstrates there is
no fundamental blocker to buildig the qemu-nbd binary too.
Changed in v2:
- Split second patch into two parts
- Use HAVE_NBD_DEVICE condition to disable SIGTERM handler not WIN32
Daniel P. Berrangé (3):
block: add missing socket_init() calls to tools
nbd: skip SIGTERM handler if NBD device support is not built
nbd: disable signals and forking on Windows builds
meson.build | 7 ++-----
qemu-img.c | 2 ++
qemu-io.c | 2 ++
qemu-nbd.c | 11 ++++++++++-
4 files changed, 16 insertions(+), 6 deletions(-)
--
2.26.2
next reply other threads:[~2020-08-25 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 10:38 Daniel P. Berrangé [this message]
2020-08-25 10:38 ` [PATCH v2 1/3] block: add missing socket_init() calls to tools Daniel P. Berrangé
2020-08-25 10:38 ` [PATCH v2 2/3] nbd: skip SIGTERM handler if NBD device support is not built Daniel P. Berrangé
2020-09-02 21:27 ` Eric Blake
2020-08-25 10:38 ` [PATCH v2 3/3] nbd: disable signals and forking on Windows builds Daniel P. Berrangé
2020-09-02 21:27 ` Eric Blake
2020-09-02 22:07 ` 罗勇刚(Yonggang Luo)
2020-09-02 23:29 ` Eric Blake
2020-09-03 7:06 ` 罗勇刚(Yonggang Luo)
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=20200825103850.119911-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--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).