qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Stefan Weil" <sw@weilnetz.de>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Konstantin Kostiuk" <kkostiuk@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	QEMU <qemu-devel@nongnu.org>,
	"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: Debian MinGW cross compilation (was: Re: [PULL 2/3] qga-win32: Add support for NVME but type)
Date: Fri, 3 Jun 2022 15:15:52 +0200	[thread overview]
Message-ID: <0a3e29b2-5dff-94bb-b4f0-f4f2a7859ece@redhat.com> (raw)
In-Reply-To: <625aa52e-731c-c80c-791f-12ef8a6c5c3d@weilnetz.de>

On 03/06/2022 15.09, Stefan Weil wrote:
> Am 03.06.22 um 14:56 schrieb Thomas Huth:
> 
>> On 24/05/2022 15.38, Daniel P. Berrangé wrote:
>>> On Tue, May 24, 2022 at 03:28:37PM +0200, Thomas Huth wrote:
>> ...
>>>>
>>>> Daniel, do you remember whether we supported Debian for MinGW
>>>> cross-compilation in the past?
>>>
>>> At one time we used to have Debian with the 3rd party 'mxe' builds
>>> of mingw added. It broke periodically and we deleted it in the
>>> end. It wasn't adding value over what Fedora mingw could provide
>>> as both more or less tracked the same versions of software in
>>> their mingw packages.
>>
>> I wonder whether anybody still tried to compile with this mxe repo in 
>> recent times...?
>> Should we adjust our support statement and just mention Fedora there? 
>> Otherwise we should maybe explicitly mention MXE there next to "Debian", 
>> too, so that people don't get the impression that QEMU can be compiled 
>> with a vanilla MinGW installation on Debian?
>>
>>  Thomas
> 
> 
> My QEMU for Windows builds are all done on Debian. They use the cross tools 
> which are provided in the normal Debian distribution. I don't use the (few) 
> cross libraries from Debian.
> 
> Until end of last year, I added library packages from Cygwin (plus a few 
> self compiled libraries, for example for braille support). See 
> https://qemu.weilnetz.de/debian/.
> 
> In 2022 I switched to using the library packages from msys (I still have to 
> write some documentation for that).

Ok, thanks for the info. Seems like there are multiple ways to get the 
missing packages for the MinGW installation on Debian, so let's simply keep 
the support statement in the current shape.

  Thomas



  reply	other threads:[~2022-06-03 13:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 19:41 [PULL 0/3] qemu-ga patches Konstantin Kostiuk
2022-05-23 19:41 ` [PULL 1/3] qga: add guest-get-diskstats command for Linux guests Konstantin Kostiuk
2022-05-23 19:41 ` [PULL 2/3] qga-win32: Add support for NVME but type Konstantin Kostiuk
2022-05-23 20:55   ` Richard Henderson
2022-05-24  9:26     ` Konstantin Kostiuk
2022-05-24 10:01       ` Konstantin Kostiuk
2022-05-24 10:14         ` Marc-André Lureau
2022-05-24 10:24           ` Thomas Huth
2022-05-24 13:00             ` Konstantin Kostiuk
2022-05-24 13:13               ` Thomas Huth
2022-05-24 13:17                 ` Konstantin Kostiuk
2022-05-24 13:28                   ` Thomas Huth
2022-05-24 13:33                     ` Thomas Huth
2022-05-24 13:38                     ` Daniel P. Berrangé
2022-06-03 12:56                       ` Debian MinGW cross compilation (was: Re: [PULL 2/3] qga-win32: Add support for NVME but type) Thomas Huth
2022-06-03 13:09                         ` Stefan Weil via
2022-06-03 13:15                           ` Thomas Huth [this message]
2022-05-24 10:16       ` [PULL 2/3] qga-win32: Add support for NVME but type Peter Maydell
2022-05-23 19:41 ` [PULL 3/3] trivial: qga: Log version on start Konstantin Kostiuk

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=0a3e29b2-5dff-94bb-b4f0-f4f2a7859ece@redhat.com \
    --to=thuth@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kkostiuk@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=sw@weilnetz.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 NNTP newsgroup(s).