From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:59628) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKaQN-0003vo-A1 for qemu-devel@nongnu.org; Thu, 12 May 2011 14:15:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QKaQM-0004uW-5L for qemu-devel@nongnu.org; Thu, 12 May 2011 14:15:47 -0400 Received: from mail-iy0-f173.google.com ([209.85.210.173]:59258) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKaQM-0004u8-2B for qemu-devel@nongnu.org; Thu, 12 May 2011 14:15:46 -0400 Received: by iym10 with SMTP id 10so1708192iym.4 for ; Thu, 12 May 2011 11:15:44 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <1305023443-8722-1-git-send-email-kraxel@redhat.com> <201105101624.08253.bradh@frogmouth.net> <4DCBA79B.5040608@redhat.com> <4DCBFBFF.7000203@redhat.com> <4DCBFE2F.7040202@codemonkey.ws> <4DCC0981.4070801@codemonkey.ws> Date: Thu, 12 May 2011 20:15:43 +0200 Message-ID: From: Peter Maydell Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] qdev device documentation (Re: [PATCH 0/2] usb-linux: physical port handling.) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster Cc: amit.shah@redhat.com, qemu-devel@nongnu.org, Gerd Hoffmann , Brad Hards On 12 May 2011 19:58, Markus Armbruster wrote: > Anthony Liguori writes: >> But for things like Spice where the lack of libspice influences >> whether the device is available, how do I extract formal documentation >> to publish on qemu.org reliably? > > If no maintainer of QEMU can build with Spice enabled, it got more > serious problems than extracting its documentation. The point isn't that you can arrange to build with option Foo enabled but that if the build environment changes accidentally there's not much warning that the official docs have suddenly lost some devices. The spice probe in configure will barf if you said "--enable-spice" and spice wasn't found, but I bet not all configure checks that influence availability of a device do that. And since there isn't currently an '--enable-all' option to configure the docs builder would have to keep track of every new --enable-foo switch and add it to the configure command... Which looks pretty ugly and not very reliable to me. -- PMM