From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Adam Baxter <voltagex@voltagex.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Building nsis installer - cross compile for Windows
Date: Mon, 28 Jan 2019 14:56:42 +0000 [thread overview]
Message-ID: <20190128145642.GA3437@redhat.com> (raw)
In-Reply-To: <CAFEAcA9gvX_9HDadd1VaC214CLDg7w1dOdCaKXuG5PXxC+-quA@mail.gmail.com>
On Mon, Jan 28, 2019 at 01:46:57PM +0000, Peter Maydell wrote:
> On Mon, 28 Jan 2019 at 13:34, Adam Baxter <voltagex@voltagex.org> wrote:
> >
> > I'm getting stuck trying to build the NSIS installer for Windows
> >
> >
> > export CFLAGS="-Wno-stringop-truncation"
> > ./configure --python=$(command -v python3)
> > --cross-prefix=x86_64-w64-mingw32- --enable-docs
> > echo 3.99.99 > VERSION
> > make -j`nproc`
> > make -j`nproc` installer
> >
> > results in:
>
> > File: "/tmp/qemu-nsis\*.bmp" -> no files found.
> > Usage: File [/nonfatal] [/a] ([/r] [/x filespec [...]] filespec [...] |
> > /oname=outfile one_file_only)
> > Error in script "/drone/src/qemu.nsi" on line 122 -- aborting creation process
> > make: *** [Makefile:915: qemu-setup-3.99.99.exe] Error 1
>
> I suspect this is because we've recently removed the
> qemu-icon.bmp but didn't update the NSIS installer script,
> which is now looking for a wildcard that doesn't match anything
> (and isn't trying to install the new .png icon files).
> If you try this on a commit before a8260d3876389eb52 does it
> work?
Opps, I'll cook up a fix that.
>
> qemu-icon.bmp seems also to still be listed in the LINKS
> in configure which defines what we symlink from the source
> tree to the build tree (and again, the png files are not).
Wierd, I don't understand why we need any of that LINKS stuff in
configure. Not having the png files listed doesn't cause any
obvious problem that I can see. For that matter nor does having
the (now deleted) qemu-icon.bmp seem to cause a failure, as we
silent ignore source tree files that don't exist.
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-01-28 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 4:34 [Qemu-devel] Building nsis installer - cross compile for Windows Adam Baxter
2019-01-28 13:46 ` Peter Maydell
2019-01-28 14:56 ` Daniel P. Berrangé [this message]
2019-01-28 15:03 ` Peter Maydell
2019-01-28 15:11 ` Daniel P. Berrangé
2019-01-28 15:15 ` Peter Maydell
2019-07-13 15:38 ` 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=20190128145642.GA3437@redhat.com \
--to=berrange@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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.