All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Kenneth Adam Miller <kennethadammiller@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: QEMU System and User targets
Date: Fri, 16 Jul 2021 16:37:32 +0100	[thread overview]
Message-ID: <CAFEAcA8rGR9=f9Nt+Z0FeFR_m77OvC4SrmJ91+fU5NjR4ATcKg@mail.gmail.com> (raw)
In-Reply-To: <CAK7rcp9uNpQcFepqMugg6qv2LWMY5O=TPBDp7uKAUs0whjmrbQ@mail.gmail.com>

On Fri, 16 Jul 2021 at 16:16, Kenneth Adam Miller
<kennethadammiller@gmail.com> wrote:
>
> When I go to build the qemu softmmu target the shared files - the i386_ss of my arch - gives problems where the build system isn't specifying the include headers for the compiler to find the surrounding headers that belong to different parts of the qemu library. I was able to edit my own source only so much before recursive header dependencies had included their own respective qemu library components subdirectories, at which point the build fails with cannot find header. I want to know, are these shared source set files not supposed to include those qemu subcomponents? Or resolve a different way for each target using #ifdef guards? I would think that this would be modularized from within the qemu subcomponent library. And I think that configure and meson are working together to generate the correct build commands to these shared components. So I'm unsure what to do.

Upstream QEMU builds fine for me, so you'll need to be more
specific about what you're trying to do and how it fails.
The top level meson.build always includes the current source
directory and the top level include/ directory on the compiler
include path, which should be all you need.

thanks
-- PMM


  reply	other threads:[~2021-07-16 15:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 15:57 QEMU System and User targets Kenneth Adam Miller
2021-07-15 16:17 ` Peter Maydell
2021-07-15 16:25   ` Kenneth Adam Miller
2021-07-15 16:34     ` Peter Maydell
2021-07-15 16:39       ` Kenneth Adam Miller
2021-07-16 15:16         ` Kenneth Adam Miller
2021-07-16 15:37           ` Peter Maydell [this message]
2021-07-16 17:50             ` Kenneth Adam Miller
2021-07-16 18:04               ` Peter Maydell
2021-07-16 18:20                 ` Kenneth Adam Miller
2021-07-16 20:06                   ` Kenneth Adam Miller
2021-07-17 10:04                     ` Peter Maydell

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='CAFEAcA8rGR9=f9Nt+Z0FeFR_m77OvC4SrmJ91+fU5NjR4ATcKg@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=kennethadammiller@gmail.com \
    --cc=qemu-devel@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 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.