qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Stefan Weil <sw@weilnetz.de>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	"John Snow" <jsnow@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: Windows installer builds apparently broken since October?
Date: Fri, 15 Jan 2021 15:57:46 +0000	[thread overview]
Message-ID: <CAFEAcA9R3+tnmJa6qpVaSD-e-rQJu7QJ_ptg4=eZwJCAVOLwqQ@mail.gmail.com> (raw)
In-Reply-To: <03e68d8d-9446-ebec-7be0-21764b567dda@weilnetz.de>

On Fri, 15 Jan 2021 at 15:52, Stefan Weil <sw@weilnetz.de> wrote:
> I forgot to mention that some of the problems with the Meson build also
> occur on macOS with Homebrew: they always happen when a software package
> requires special compiler flags to find its include files or libraries,
> but the Meson build does not use the result from pkg-config for them.

Yeah -- we fixed that in commit 3eacf70bb5a83e4 for gnutls, which
is the main one homebrew was running into. Is Windows having
problems with other libs too?

Paolo: did we come up with a generic solution for this or
do we really have to add entries to dependency lists all
over the build system for every library we use?

thanks
-- PMM


  reply	other threads:[~2021-01-15 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 14:01 Windows installer builds apparently broken since October? Peter Maydell
2021-01-15 15:19 ` Peter Maydell
2021-01-15 15:52   ` Stefan Weil
2021-01-15 15:57     ` Peter Maydell [this message]
2021-01-15 17:34       ` Paolo Bonzini
2021-01-15 15:34 ` Stefan Weil
2021-01-15 15:40   ` Peter Maydell
2021-01-15 17:57   ` 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='CAFEAcA9R3+tnmJa6qpVaSD-e-rQJu7QJ_ptg4=eZwJCAVOLwqQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).