From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Stefan Weil <sw@weilnetz.de>
Subject: Re: [Qemu-devel] [PATCH v2 2/4] docs: add build infrastructure for gtkdocs (v2)
Date: Tue, 13 Mar 2012 00:37:12 +0100 [thread overview]
Message-ID: <4F5E88A8.7040203@suse.de> (raw)
In-Reply-To: <20120312204853.GM20654@otherpad.lan.raisama.net>
Am 12.03.2012 21:48, schrieb Eduardo Habkost:
>
> I don't know if this is really the latest version of the series, but I don't
> see any newer version on my qemu-devel folder, so:
FWIW I have a rebased version on my qom-cpu-wip branch (no functional
changes). Note that mine depends on the qom-user series due to some -I
CFLAGS addition.
> On Wed, Dec 14, 2011 at 02:01:12PM -0600, Anthony Liguori wrote:
> [...]
>> +html/index.html: $(DOC_SRC)
>> + $(GTKDOC_SCAN) --module=QEMU --source-dir=$(SRC_PATH)/include && \
>> + cp $(SRC_PATH)/QEMU-docs.xml . && \
>
> When trying to build the docs I get the following error. It looks like the rule
> is assuming an out-of-tree build:
>
> $ make gtkdoc DOC_PREFIX=/home/ehabkost/pessoal/proj/virt/gtk-doc
> /home/ehabkost/pessoal/proj/virt/gtk-doc/gtkdoc-scan --module=QEMU --source-dir=/home/ehabkost/pessoal/proj/virt/qemu/include && \
> cp /home/ehabkost/pessoal/proj/virt/qemu/QEMU-docs.xml . && \
> /home/ehabkost/pessoal/proj/virt/gtk-doc/gtkdoc-mkdb --module=QEMU --output-format=xml --source-dir=/home/ehabkost/pessoal/proj/virt/qemu/include && \
> mkdir -p html && \
> (cd html && /home/ehabkost/pessoal/proj/virt/gtk-doc/gtkdoc-mkhtml QEMU ../QEMU-docs.xml && cd ..) && \
> /home/ehabkost/pessoal/proj/virt/gtk-doc/gtkdoc-fixxref --module=QEMU --module-dir=html
> cp: `/home/ehabkost/pessoal/proj/virt/qemu/QEMU-docs.xml' and `./QEMU-docs.xml' are the same file
> make: *** [html/index.html] Error 1
Never tried an in-tree build of this myself...
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-03-12 23:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 20:01 [Qemu-devel] [PATCH v2 0/4] GTK-DOC build integration (v2) Anthony Liguori
2011-12-14 20:01 ` [Qemu-devel] [PATCH v2 1/4] memory: make memory API parsable by gtkdoc-scan (v2) Anthony Liguori
2011-12-15 9:28 ` Kevin Wolf
2011-12-15 13:25 ` Anthony Liguori
2011-12-14 20:01 ` [Qemu-devel] [PATCH v2 2/4] docs: add build infrastructure for gtkdocs (v2) Anthony Liguori
2012-03-12 20:48 ` Eduardo Habkost
2012-03-12 23:37 ` Andreas Färber [this message]
2011-12-14 20:01 ` [Qemu-devel] [PATCH v2 3/4] memory: update documentation to be in gtk-doc format Anthony Liguori
2011-12-14 20:01 ` [Qemu-devel] [PATCH v2 4/4] memory: move header into include/ and add to QEMU docs Anthony Liguori
2011-12-14 20:54 ` [Qemu-devel] [PATCH v2 0/4] GTK-DOC build integration (v2) Marc-André Lureau
2011-12-14 21:08 ` Anthony Liguori
2011-12-15 5:22 ` Andreas Färber
2011-12-15 9:32 ` Stefan Weil
2011-12-15 10:04 ` Daniel P. Berrange
2011-12-15 10:29 ` Stefan Weil
2011-12-15 11:36 ` Andreas Färber
2011-12-15 11:46 ` Kevin Wolf
2011-12-15 10:21 ` Kevin Wolf
2011-12-18 12:00 ` Stefan Weil
2012-03-12 21:03 ` Lluís Vilanova
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=4F5E88A8.7040203@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=ehabkost@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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.