qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Claudio Fontana <cfontana@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: meson: why no target_user_arch in target/xxx/meson.build ?
Date: Tue, 9 Feb 2021 20:24:12 +0100	[thread overview]
Message-ID: <4b64cbcd-0982-9251-b3c4-d82287df139b@suse.de> (raw)

Hi Paolo,

I am looking at arm code right now in target/

and I would like to build some separate helper-user.c and helper-softmmu.c .

I'd like then to include only the right one depending on CONFIG_SOFTMMU and CONFIG_USER_ONLY.

Any reason why there is no equivalent of target_softmmu_arch called target_user_arch to use for this?

Thanks,

Claudio

-- 
Claudio Fontana
Engineering Manager Virtualization, SUSE Labs Core

SUSE Software Solutions Italy Srl


             reply	other threads:[~2021-02-09 19:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 19:24 Claudio Fontana [this message]
2021-02-09 19:31 ` meson: why no target_user_arch in target/xxx/meson.build ? 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=4b64cbcd-0982-9251-b3c4-d82287df139b@suse.de \
    --to=cfontana@suse.de \
    --cc=pbonzini@redhat.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 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).