qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Adam Baxter <voltagex@voltagex.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] NSIS - including DLL dependencies for Windows
Date: Thu, 31 Jan 2019 11:19:04 +0000	[thread overview]
Message-ID: <CAFEAcA_TYKmG+gfm1gUw-xjM3VFXUebCD22rGSPyBuZ9ugWVPQ@mail.gmail.com> (raw)
In-Reply-To: <20190131104911.GF19982@redhat.com>

On Thu, 31 Jan 2019 at 10:50, Daniel P. Berrangé <berrange@redhat.com> 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.

I think my concern here potentially is a licensing one -- if we don't
actually ship installer binaries then that's fine for us, but an
installer script that automatically pulls in DLLs for glib and others
is a bit of a footgun for anybody that uses it since it will very likely
create an installer binary that is very difficult to ship to anybody
whilst remaining compliant with the licenses for our dependencies.

thanks
-- PMM

  parent reply	other threads:[~2019-01-31 11:19 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 [this message]
2019-01-31 11:28     ` Daniel P. Berrangé
2019-01-31 13:27       ` Stefan Weil
2019-02-13  9:32   ` Daniel P. Berrangé
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=CAFEAcA_TYKmG+gfm1gUw-xjM3VFXUebCD22rGSPyBuZ9ugWVPQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=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).