From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Adam Baxter <voltagex@voltagex.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] NSIS - including DLL dependencies for Windows
Date: Wed, 13 Feb 2019 09:32:41 +0000 [thread overview]
Message-ID: <20190213093241.GF13960@redhat.com> (raw)
In-Reply-To: <20190131104911.GF19982@redhat.com>
On Thu, Jan 31, 2019 at 10:49:11AM +0000, Daniel P. Berrangé wrote:
> On Thu, Jan 31, 2019 at 02:45:13PM +1100, Adam Baxter wrote:
> > Hi,
> > How do I gather and include the required DLLs (SDL, zlib etc) in the NSIS
> > installer? (and also in a standalone build to be zipped up, but that's less
> > important)
> >
> > I noticed the wiki doesn't really mention bundling dependencies anywhere.
> >
> > The official unofficial windows builds are documented at
> > https://qemu.weilnetz.de/FAQ but this doesn't cover building the actual
> > installer.
>
> Yeah, this is a pretty major ommision in QEMU's build rules for the NSIS
> installer making it pretty much useless as is. We really need to expand
> it so that it can resolve the dlls that qemu .exe's need, locate them
> on the host and bundle them into the installer automatically.
>
> It seems we can get a list of deps for an .exe using
>
> $ winedump -j import /path/to/binary.exe | grep offset | grep dll | awk '{print $3}'
FYI, I re-discovered a way to do this without needing wine, just plain
binutils
x86_64-w64-mingw32-objdump -p /path/to/binary.exe | grep "DLL Name" | awk '{print $3}'
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-02-13 9:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 3:45 [Qemu-devel] NSIS - including DLL dependencies for Windows Adam Baxter
2019-01-31 10:49 ` Daniel P. Berrangé
2019-01-31 10:54 ` Adam Baxter
2019-01-31 11:19 ` Peter Maydell
2019-01-31 11:28 ` Daniel P. Berrangé
2019-01-31 13:27 ` Stefan Weil
2019-02-13 9:32 ` Daniel P. Berrangé [this message]
2019-02-13 9:47 ` Stefan Weil
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=20190213093241.GF13960@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=voltagex@voltagex.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).