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 15:11:28 +0000 [thread overview]
Message-ID: <20190128151128.GB3437@redhat.com> (raw)
In-Reply-To: <CAFEAcA9cDvq3VRaQfAgEvc-sKA4TYEC9PuFX_Vofo18bSbip=Q@mail.gmail.com>
On Mon, Jan 28, 2019 at 03:03:34PM +0000, Peter Maydell wrote:
> On Mon, 28 Jan 2019 at 14:56, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > On Mon, Jan 28, 2019 at 01:46:57PM +0000, Peter Maydell wrote:
> > > 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.
>
> The LINKS stuff is so that you can run binaries from out of
> the build directory and have them find things like the BIOS
> blobs. In this case presumably a QEMU run from the build
> dir wouldn't find its icon (unless somebody had done a
> 'make install' on the system in the past). Though something
> doesn't seem quite right here, because the sdl2.c code is
> looking for icon files in a hicolor/ subdirectory that
> doesn't exist in the source tree.
That directory is the standard icon installation directory for
application icons. The QEMU icons are placed there by 'make install',
but in the source dir they are in a flat layotu.
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:11 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é
2019-01-28 15:03 ` Peter Maydell
2019-01-28 15:11 ` Daniel P. Berrangé [this message]
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=20190128151128.GB3437@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.