All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: John Snow <jsnow@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] docs: describe the QEMU build system structure / design
Date: Thu, 24 Sep 2015 13:20:40 +0200	[thread overview]
Message-ID: <5603DC88.9090303@redhat.com> (raw)
In-Reply-To: <1443088173-3449-1-git-send-email-berrange@redhat.com>

On 09/24/15 11:49, Daniel P. Berrange wrote:
> Developers who are new to QEMU, or have a background familiarity
> with GNU autotools, can have trouble getting their head around the
> home-grown QEMU build system. This document attempts to explain
> the structure / design of the configure script and the various
> Makefile pieces that live across the source tree.
> 
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> 
> Changed in v3:
> 
>  - More speling eror fixes
>  - Rephrased more paragraphs as suggested
> 
> Changed in v2:
> 
>  - Misc speling eror fixes
>  - Rephrased some paragraphs as suggested
>  - Added note about config-host.h file generation & use
> 
>  docs/build-system.txt | 507 ++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 507 insertions(+)
>  create mode 100644 docs/build-system.txt

Diffed this against v2; I have only one comment:

> +the userspace emulator targets as the global $(LIBS), or more targetted

This is new in v3, and it seems to reintroduce the (otherwise correct
en_GB?) spelling of "targetted". If I recall correctly, it has been
suggested to spell it as "targeted" (and that form can in fact be found
in the same paragraph).

Otherwise, ACK.

Thanks
Laszlo

      reply	other threads:[~2015-09-24 11:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24  9:49 [Qemu-devel] [PATCH v3] docs: describe the QEMU build system structure / design Daniel P. Berrange
2015-09-24 11:20 ` Laszlo Ersek [this message]

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=5603DC88.9090303@redhat.com \
    --to=lersek@redhat.com \
    --cc=berrange@redhat.com \
    --cc=jsnow@redhat.com \
    --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 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.