From: Laszlo Ersek <lersek@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] docs: describe the QEMU build system structure / design
Date: Wed, 23 Sep 2015 17:46:34 +0200 [thread overview]
Message-ID: <5602C95A.1060705@redhat.com> (raw)
In-Reply-To: <1443002356-22481-1-git-send-email-berrange@redhat.com>
I diffed this version against v1. Thank you for addressing my comments
too; however I found some newly introduced typos:
On 09/23/15 11:59, Daniel P. Berrange wrote:
> +The utility code that is used by all binaries is built into a
> +static archive called libqemuutil.a, which is then linked to all the
> +binaries. In order to provides hooks that are only needed by some of the
to provide[]
> +binaries, code in libqemuutil.a may depend on other functions that are
> +not fully implementd by all QEMU binaries. To deal with this there is a
implement[e]d
To deal with this[,]
> +second library called libqemustub.a which provide dummy stubs for all
[,] which provide[s]
> +these functions. These will get lazy linked into the binary if the real
> +implementation is not present. In this way, the libqemustub.a static
> +library can be thought of as a portable implementation of the weak
> +symbols concept. All binaries should link to both libqemuutil.a and
> +libqemustub.a. e.g.
[,] e.g.[:] -- but I don't feel strongly about this :)
> +
> + qemu-img$(EXESUF): qemu-img.o ..snip.. libqemuutil.a libqemustub.a
> +
> +
> +Windows platform portability
> +----------------------------
> +
> +On Windows all binaries have a 'exe' suffix, so all the Makefile rules
This was
"a .exe suffix"
before, and Jon commented that you probably pronounced it as "a dot-exe
suffix".
Now you've removed the dot, but haven't changed "a" into "an". :)
> +If there are any rules defined in the Makefile.objs file, they should
> +all use $(obj) as a prefix to the target e.g.
target[,] e.g.[:] -- not very necessary though
> +Dynamically created files
> +-------------------------
> +
> +The following files are generated dynamically by configure in order to
> +control the behaviour of the statically defined makefiles. This avoids
> +the need for QEMU makefiles to go through any pre-processing as seen
> +with autotools, where Makefile.am generates Makefile.in which generates
> +Makefile.
> +
I suggest to insert another empty line here, with consistency for the
other entries below. (This is not new in v2, so sorry about pointing it
out now.)
For the next version (v3):
Acked-by: Laszlo Ersek <lersek@redhat.com>
Thanks
Laszlo
next prev parent reply other threads:[~2015-09-23 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 9:59 [Qemu-devel] [PATCH v2] docs: describe the QEMU build system structure / design Daniel P. Berrange
2015-09-23 10:06 ` Paolo Bonzini
2015-09-23 15:13 ` John Snow
2015-09-23 15:46 ` Laszlo Ersek [this message]
2015-09-23 15:47 ` Laszlo Ersek
2015-09-23 15:52 ` John Snow
2015-09-23 16:47 ` Eric Blake
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=5602C95A.1060705@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 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).