From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:41215)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <sw@weilnetz.de>) id 1Rb7gk-0007AF-NE
	for qemu-devel@nongnu.org; Thu, 15 Dec 2011 04:33:22 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <sw@weilnetz.de>) id 1Rb7ge-0002nl-QP
	for qemu-devel@nongnu.org; Thu, 15 Dec 2011 04:33:18 -0500
Received: from v220110690675601.yourvserver.net ([78.47.199.172]:50666)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <sw@weilnetz.de>) id 1Rb7ge-0002nR-Jx
	for qemu-devel@nongnu.org; Thu, 15 Dec 2011 04:33:12 -0500
Message-ID: <4EE9BEA4.5020004@weilnetz.de>
Date: Thu, 15 Dec 2011 10:32:20 +0100
From: Stefan Weil <sw@weilnetz.de>
MIME-Version: 1.0
References: <1323892874-13234-1-git-send-email-aliguori@us.ibm.com>	<CAJ+F1CKNMGk6qikGNiyPgxfs6EpakTOxhm9V3HTHFUeyfE=0_Q@mail.gmail.com>	<4EE91045.9070109@codemonkey.ws>
	<4EE98433.9080205@suse.de>
In-Reply-To: <4EE98433.9080205@suse.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [PATCH v2 0/4] GTK-DOC build integration (v2)
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?ISO-8859-1?Q?Andreas_F=E4rber?= <afaerber@suse.de>
Cc: Peter Maydell <peter.maydell@linaro.org>, =?ISO-8859-1?Q?Marc-Andr=E9_Lureau?= <marcandre.lureau@gmail.com>, Avi Kivity <avi@redhat.com>, qemu-devel@nongnu.org

Am 15.12.2011 06:22, schrieb Andreas F=E4rber:
> Their website has the following:
>
> "GTK-Doc wasn't originally intended to be a general-purpose
> documentation tool, so it can be a bit awkward to setup and use. For a
> more polished general-purpose documentation tool you may want to look a=
t
> Doxygen. However GTK-Doc has some special code to document the signals
> and properties of GTK+ widgets and GObject classes which other tools ma=
y
> not have."
> http://www.gtk.org/gtk-doc/
>
> Don't know if Doxygen has less restrictions though.
>
> Andreas

With doxygen, the documentation looks like this:
http://qemu.weilnetz.de/doxygen/

I only modified the first lines of memory.h to get
the global C functions, but of course more changes
are needed if we choose doxygen as our standard.

Regards,
Stefan Weil