From: Paolo Bonzini <pbonzini@redhat.com>
To: "Pierrick Bouvier" <pierrick.bouvier@linaro.org>,
"Erwin Jansen" <jansene@google.com>,
"Roque Arcudia Hernandez" <roqueh@google.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
sw@weilnetz.de, lvivier@redhat.com,
"Patrick Leis" <venture@google.com>,
"Nabih Estefan" <nabihestefan@google.com>,
"Danny Rosen" <dannyrosen@google.com>,
"JP Cottin" <jpcottin@google.com>,
berrange@redhat.com, "Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: QEMU patches for native windows support through clang-cl
Date: Thu, 21 Nov 2024 19:24:20 +0100 [thread overview]
Message-ID: <f45226a9-7664-41e7-849d-e8939f692d49@redhat.com> (raw)
In-Reply-To: <61ca5164-3d81-4e2c-b581-304cf3cdecc0@linaro.org>
On 11/21/24 19:17, Pierrick Bouvier wrote:
> On 11/21/24 09:36, Erwin Jansen wrote:
>> The Android Emulator team has successfully ported QEMU 8 to compile
>> with clang-cl, enabling Windows compilation and better integration
>> with the Microsoft ecosystem. This involved:
>>
>> * Replacing shell scripts with Python for enhanced Windows
>> compatibility.
It would be useful to know what scripts. configure? :)
If it's just scripts/make-config-poison.sh or scripts/qemu-version.sh,
no objection at all.
>> * Implementing fixes within existing scripts.
>> * Introducing a small set of header stubs and a series of compilation
>> fixes.
If you can add this configuration to the GitLab CI, I don't see any
blocker. Otherwise there's risk of bitrot.
Paolo
next prev parent reply other threads:[~2024-11-21 18:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP52u7a_CA-PEw2gMgc32rCKGt8mqsjCkEedkzTgOosazrTs-w@mail.gmail.com>
2024-11-21 18:17 ` QEMU patches for native windows support through clang-cl Pierrick Bouvier
2024-11-21 18:24 ` Paolo Bonzini [this message]
[not found] ` <Zz99VtNtZCx-P5Mx@redhat.com>
2024-11-21 18:47 ` Paolo Bonzini
2024-11-21 21:42 ` Erwin Jansen
2024-11-22 8:08 ` Paolo Bonzini
2024-11-24 0:38 ` Pierrick Bouvier
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=f45226a9-7664-41e7-849d-e8939f692d49@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=dannyrosen@google.com \
--cc=jansene@google.com \
--cc=jpcottin@google.com \
--cc=lvivier@redhat.com \
--cc=nabihestefan@google.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=roqueh@google.com \
--cc=sw@weilnetz.de \
--cc=venture@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.