From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: [PATCH] meson.build: Always require an objc compiler on macos hosts
Date: Mon, 11 Mar 2024 13:36:54 +0000 [thread overview]
Message-ID: <Ze8I9hDQIJGGv0nt@redhat.com> (raw)
In-Reply-To: <20240311133334.3991537-1-peter.maydell@linaro.org>
On Mon, Mar 11, 2024 at 01:33:34PM +0000, Peter Maydell wrote:
> We currently only insist that an ObjectiveC compiler is present on
> macos hosts if we're building the Cocoa UI. However, since then
> we've added some other parts of QEMU which are also written in ObjC:
> the coreaudio audio backend, and the vmnet net backend. This means
> that if you try to configure QEMU on macos with --disable-cocoa the
> build will fail:
>
> ../meson.build:3741:13: ERROR: No host machine compiler for 'audio/coreaudio.m'
>
> Since in practice any macos host will have an ObjC compiler
> available, rather than trying to gate the compiler detection on an
> increasingly complicated list of every bit of QEMU that uses ObjC,
> just require it unconditionally on macos hosts.
>
> Resolves https://gitlab.com/qemu-project/qemu/-/issues/2138
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> Per the commit message, in theory we could allow a no-objc
> build and disable coreaudio, vmnet, etc. But I didn't really see
> a reason why that would be useful, and it's bound to keep
> breaking unless we actively defend it in CI. So I preferred
> to simply require ObjC on macos.
Yeah, I think simplicity wins here, unless someone can provide
a compelling reason why they absolutely must be able to build
without objc being present, even if it were unused.
> meson.build | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>
> diff --git a/meson.build b/meson.build
> index f9dbe7634e5..e3fab8ce9ff 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -66,7 +66,7 @@ if host_os == 'windows' and add_languages('cpp', required: false, native: false)
> cxx = meson.get_compiler('cpp')
> endif
> if host_os == 'darwin' and \
> - add_languages('objc', required: get_option('cocoa'), native: false)
> + add_languages('objc', required: true, native: false)
> all_languages += ['objc']
> objc = meson.get_compiler('objc')
> endif
> --
> 2.34.1
>
With 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:[~2024-03-11 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 13:33 [PATCH] meson.build: Always require an objc compiler on macos hosts Peter Maydell
2024-03-11 13:36 ` Daniel P. Berrangé [this message]
2024-03-11 14:17 ` Philippe Mathieu-Daudé
2024-03-12 8:15 ` 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=Ze8I9hDQIJGGv0nt@redhat.com \
--to=berrange@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).