From: Thomas Huth <thuth@redhat.com>
To: Joshua Watt <jpewhacker@gmail.com>, qemu-devel@nongnu.org
Cc: QEMU Trivial <qemu-trivial@nongnu.org>,
pbonzini@redhat.com, luoyonggang@gmail.com
Subject: Re: [PATCH v2] configure: MinGW respect --bindir argument
Date: Wed, 13 Jan 2021 06:33:20 +0100 [thread overview]
Message-ID: <8c52fcc8-eb2e-c068-9187-1d007e15d1af@redhat.com> (raw)
In-Reply-To: <20210112210239.28836-1-JPEWhacker@gmail.com>
On 12/01/2021 22.02, Joshua Watt wrote:
> There are two cases that need to be accounted for when compiling QEMU
> for MinGW32:
> 1) A standalone distribution, where QEMU is self contained and
> extracted by the user, such as a user would download from the QEMU
> website. In this case, all the QEMU executable files should be
> rooted in $prefix to ensure they can be easily found by the user
> 2) QEMU integrated into a distribution image/sysroot/SDK and
> distributed with other programs. In this case, the provided
> arguments for bindir/datadir/etc. should be respected as they for a
> Linux build.
>
> Restructures the MinGW path configuration so that all of the paths
> except bindir use the same rules as when building for other platforms.
> This satisfies #2 and #1 since these files do not need to be directly in
> $prefix anyway.
>
> The handling for --bindir is changed so that it defaults to $prefix on
> MinGW (maintaining the compatibility with #1), but if the user specifies
> a specific path when configuring it can also satisfy #2.
>
> Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
> ---
> configure | 17 ++++++-----------
> 1 file changed, 6 insertions(+), 11 deletions(-)
>
> diff --git a/configure b/configure
> index 5860bdb77b..092e2926bc 100755
> --- a/configure
> +++ b/configure
> @@ -1571,20 +1571,15 @@ libexecdir="${libexecdir:-$prefix/libexec}"
> includedir="${includedir:-$prefix/include}"
>
> if test "$mingw32" = "yes" ; then
> - mandir="$prefix"
> - datadir="$prefix"
> - docdir="$prefix"
> - bindir="$prefix"
> - sysconfdir="$prefix"
> - local_statedir="$prefix"
> + bindir="${bindir:-$prefix}"
> else
> - mandir="${mandir:-$prefix/share/man}"
> - datadir="${datadir:-$prefix/share}"
> - docdir="${docdir:-$prefix/share/doc}"
> bindir="${bindir:-$prefix/bin}"
> - sysconfdir="${sysconfdir:-$prefix/etc}"
> - local_statedir="${local_statedir:-$prefix/var}"
> fi
> +mandir="${mandir:-$prefix/share/man}"
> +datadir="${datadir:-$prefix/share}"
> +docdir="${docdir:-$prefix/share/doc}"
> +sysconfdir="${sysconfdir:-$prefix/etc}"
> +local_statedir="${local_statedir:-$prefix/var}"
> firmwarepath="${firmwarepath:-$datadir/qemu-firmware}"
> localedir="${localedir:-$datadir/locale}"
Yes, I think this makes most sense, thanks for the update!
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2021-01-13 5:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 21:38 [PATCH] configure: Add flags for MinGW32 standalone build Joshua Watt
2021-01-08 7:25 ` Thomas Huth
2021-01-08 18:30 ` Joshua Watt
2021-01-11 7:04 ` Thomas Huth
2021-01-11 7:29 ` Stefan Weil
2021-01-11 7:44 ` Paolo Bonzini
2021-01-11 16:01 ` Joshua Watt
2021-01-11 17:34 ` Paolo Bonzini
2021-01-12 21:02 ` [PATCH v2] configure: MinGW respect --bindir argument Joshua Watt
2021-01-13 5:33 ` Thomas Huth [this message]
2021-01-13 10:01 ` Paolo Bonzini
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=8c52fcc8-eb2e-c068-9187-1d007e15d1af@redhat.com \
--to=thuth@redhat.com \
--cc=jpewhacker@gmail.com \
--cc=luoyonggang@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.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).