qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: Stefan Weil <sw@weilnetz.de>,
	Brian Cain <brian.cain@oss.qualcomm.com>,
	qemu-devel@nongnu.org
Cc: "Mahmoud Mandour" <ma.mandourr@gmail.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Thomas Huth" <thuth@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Stefano Garzarella" <sgarzare@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Alexandre Iooss" <erdnaxe@crans.org>
Subject: Re: [PATCH v4 0/3] Enable clang build on Windows
Date: Tue, 18 Feb 2025 23:01:53 -0800	[thread overview]
Message-ID: <290b3ab2-70a2-4846-a53e-ec18f848d1c9@linaro.org> (raw)
In-Reply-To: <dc259719-c030-4c71-bf31-c505ca66bb48@weilnetz.de>

On 2/18/25 22:39, Stefan Weil wrote:
> Am 19.02.25 um 00:17 schrieb Pierrick Bouvier:
> 
>> On 2/18/25 12:59, Stefan Weil wrote:
>>>
>>> I could run a QEMU cross compile on Debian with the llvm toolchain and
>>> msys2 clangarm64 packages installed with pacman. The resulting installer
>>> is here:
>>>
>>
>> Have you installed the msys2 clangarm64 packages on a windows machine
>> first, and then copy them to your Debian machine?
> 
> 
> No, the packages were directly installed on Linux like in this older
> script which shows how this can be done for i686 and x86-64::
> 
> https://github.com/stweil/qemu/blob/master/.github/workflows/pacman.sh
> 
> Newer Debian distributions already provide a package for pacman which
> simply needs the right configuration. For older distributions I had to
> build pacman first.
> 
> I should also have noted that I used a Linux aarch64 build host, so its
> binutils were able to find the DLL dependencies. This requirement will
> be fixed with a pure Python script for the same purpose.
> 

Oh excellent! I wondered if it was possible or not to do this (didn't 
know if some post install hooks try to execute native code).
Thanks for the link.

> 
>>
>>> https://qemu.weilnetz.de/aarch64/
>>>
>>> The only tool which was missing and which I had to build before running
>>> the QEMU build is aarch64-w64-mingw32-windmc.
>>>
>>> It looks like the NSIS installer is i386 code, so I don't know whether
>>> it can be used on Windows for aarch64.
>>>
>>> I also have no suitable Windows host for testing the binaries, so no
>>> test was done.



  reply	other threads:[~2025-02-19  7:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10 20:33 [PATCH v4 0/3] Enable clang build on Windows Pierrick Bouvier
2025-01-10 20:33 ` [PATCH v4 1/3] win32: remove usage of attribute gcc_struct Pierrick Bouvier
2025-01-13 23:38   ` Michael S. Tsirkin
2025-01-10 20:34 ` [PATCH v4 2/3] docs/devel/style: add a section about bitfield, and disallow them for packed structures Pierrick Bouvier
2025-01-10 20:34 ` [PATCH v4 3/3] plugins: enable linking with clang/lld Pierrick Bouvier
2025-01-10 20:37 ` [PATCH v4 0/3] Enable clang build on Windows Pierrick Bouvier
2025-01-11 15:47   ` Philippe Mathieu-Daudé
2025-01-12 18:03     ` Philippe Mathieu-Daudé
2025-01-13  6:26     ` Thomas Huth
2025-01-13 20:17       ` Pierrick Bouvier
2025-01-13 21:19         ` Alex Bennée
2025-01-13 21:22           ` Pierrick Bouvier
2025-01-11 22:08 ` Stefan Weil via
2025-01-12 17:54   ` Pierrick Bouvier
2025-02-18  4:11   ` Brian Cain
2025-02-18 16:22     ` Pierrick Bouvier
2025-02-18 16:26       ` Daniel P. Berrangé
2025-02-18 20:59       ` Stefan Weil via
2025-02-18 23:17         ` Pierrick Bouvier
2025-02-19  6:39           ` Stefan Weil via
2025-02-19  7:01             ` Pierrick Bouvier [this message]
2025-02-19  7:38               ` Stefan Weil via
2025-01-14  8:20 ` Alex Bennée
2025-01-14  8:35   ` Philippe Mathieu-Daudé

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=290b3ab2-70a2-4846-a53e-ec18f848d1c9@linaro.org \
    --to=pierrick.bouvier@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=brian.cain@oss.qualcomm.com \
    --cc=erdnaxe@crans.org \
    --cc=ma.mandourr@gmail.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=sw@weilnetz.de \
    --cc=thuth@redhat.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 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).