From: Laurent Vivier <lvivier@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: "Thomas Huth" <thuth@redhat.com>,
"David Hildenbrand" <david@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
qemu-s390x@nongnu.org, "Gerd Hoffmann" <kraxel@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3 0/5] build: cleanup in Makefile.objs
Date: Mon, 13 May 2019 17:17:51 +0200 [thread overview]
Message-ID: <b8d003fb-1d53-3723-4eef-b39a3d965bc0@redhat.com> (raw)
In-Reply-To: <6f3c5f49-9be7-85cb-d693-d608135975b5@redhat.com>
On 02/04/2019 10:08, Paolo Bonzini wrote:
> On 01/04/19 16:12, Laurent Vivier wrote:
>> This cleanup removes hardware objects from the list of files to be
>> built for linux-user only targets.
>>
>> It also builds traces files only when the related file is built.
>>
>> Tested with all combinations of --{disable,enable}-{system,user,tools}
>>
>> v3:
>> - don't move hw/display to CONFIG_BLOCK section
>> v2:
>> - add CONFIG_TOOLS and CONFIG_BLOCK
>> - replace GENERATED_FILES by generated-files-y
>> and use generated-files-${CONFIG_TRACE_UST} and
>> generated-files-${CONFIG_SOFTMMU}
>> - move chardev-obj-y from SUBDIR_RULES to SOFTMMU_SUBDIR_RULES
>> - use $(CONFIG_BLOCK) in tests/Makefile.include
>> - disable qemu-ga with linux-user only
>>
>> Laurent Vivier (5):
>> trace: only include trace-event-subdirs when they are needed
>> build: replace GENERATED_FILES by generated-files-y
>> configure: qemu-ga is only needed with softmmu targets
>> build: chardev is only needed for softmmu targets
>> build: don't build hardware objects with linux-user
>>
>> Makefile | 43 +++++++-------
>> Makefile.objs | 22 ++++---
>> Makefile.target | 6 +-
>> configure | 4 +-
>> target/s390x/Makefile.objs | 2 +-
>> tests/Makefile.include | 116 ++++++++++++++++++-------------------
>> 6 files changed, 102 insertions(+), 91 deletions(-)
>>
>
> Queued for 4.1, thanks.
Any news?
Thanks,
Laurent
next prev parent reply other threads:[~2019-05-13 15:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 14:12 [Qemu-devel] [PATCH v3 0/5] build: cleanup in Makefile.objs Laurent Vivier
2019-04-01 14:12 ` [Qemu-devel] [PATCH v3 1/5] trace: only include trace-event-subdirs when they are needed Laurent Vivier
2019-04-01 14:12 ` [Qemu-devel] [PATCH v3 2/5] build: replace GENERATED_FILES by generated-files-y Laurent Vivier
2019-04-01 14:12 ` [Qemu-devel] [PATCH v3 3/5] configure: qemu-ga is only needed with softmmu targets Laurent Vivier
2019-04-01 14:50 ` Thomas Huth
2019-04-01 14:12 ` [Qemu-devel] [PATCH v3 4/5] build: chardev is only needed for " Laurent Vivier
2019-04-01 14:12 ` [Qemu-devel] [PATCH v3 5/5] build: don't build hardware objects with linux-user Laurent Vivier
2019-04-02 8:08 ` [Qemu-devel] [PATCH v3 0/5] build: cleanup in Makefile.objs Paolo Bonzini
2019-05-13 15:17 ` Laurent Vivier [this message]
2019-05-13 16:17 ` 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=b8d003fb-1d53-3723-4eef-b39a3d965bc0@redhat.com \
--to=lvivier@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@redhat.com \
--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).