From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Cc: Helge Konetzka <hk@zapateado.de>
Subject: Re: [ITP] Qemu
Date: Tue, 20 Jul 2021 14:11:53 +0100 [thread overview]
Message-ID: <7aa10fd4-2a2a-8796-f5f3-7b97ae71a4c1@dronecode.org.uk> (raw)
In-Reply-To: <955d1013-6f2e-6490-a044-e27c699d62ee@zapateado.de>
On 30/06/2021 14:35, Helge Konetzka wrote:
> Hello,
>
>
> I would like to package Qemu for Cygwin.
> See https://www.qemu.org/
Thanks for looking into this, and sorry for the delay in responding.
> Qemu is included in Debian.
> See https://packages.debian.org/source/buster/qemu
>
> Qemu is released under the GNU General Public License, version 2. Parts
> of Qemu have specific licenses, see file LICENSE.
> See https://qemu-project.gitlab.io/qemu/system/license.html
>
>
> I've prepared cygports for the packages as a POC. See
> https://gitlab.com/hejko-cygwin/cygports
>
> Qemu binaries and resources were packaged in mingw64-x86_64-qemu and
> mingw64-i686-qemu. To make Qemu accessible in a transparent way, I've
> created qemu-integration. It mainly consists of a wrapper and a setup
> script.
> See
> https://gitlab.com/hejko-cygwin/qemu-integration
I assume that it's not straightforward to build cygwin executables of
QEMU, but mentioning some of this issues would help.
Given that: do we really need to build our own MinGW QEMU packages? Can
the integration script just rely on the official Windows packages being
installed?
> For download of POC packages see
> https://www.zapateado.de/cygwin/
>
>
> Any interest for Qemu packages in Cygwin?
> If so, I would split Qemu into several packages and add all licenses
> included in Qemu source before final upload.
next prev parent reply other threads:[~2021-07-20 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 13:35 Helge Konetzka
2021-07-20 13:11 ` Jon Turney [this message]
2021-07-21 13:43 ` Helge Konetzka
2021-07-22 13:13 ` Jon Turney
2021-07-26 20:15 ` Helge Konetzka
2021-08-04 13:03 ` Jon Turney
2021-08-09 8:37 ` Helge Konetzka
2021-08-09 20:01 ` Jon Turney
2021-08-13 8:52 ` Helge Konetzka
2021-08-14 11:26 ` Jon Turney
2021-08-14 13:02 ` Helge Konetzka
2021-08-10 2:15 ` Jason Pyeron
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=7aa10fd4-2a2a-8796-f5f3-7b97ae71a4c1@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=hk@zapateado.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).