From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LjsoA-0003Ad-7m for qemu-devel@nongnu.org; Wed, 18 Mar 2009 06:15:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ljso5-00039u-5P for qemu-devel@nongnu.org; Wed, 18 Mar 2009 06:15:33 -0400 Received: from [199.232.76.173] (port=45770 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ljso4-00039r-Dy for qemu-devel@nongnu.org; Wed, 18 Mar 2009 06:15:28 -0400 Received: from mx20.gnu.org ([199.232.41.8]:27633) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ljso4-0004H2-6g for qemu-devel@nongnu.org; Wed, 18 Mar 2009 06:15:28 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ljso3-0003Gn-69 for qemu-devel@nongnu.org; Wed, 18 Mar 2009 06:15:27 -0400 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v3 Date: Wed, 18 Mar 2009 10:15:23 +0000 References: <200903172308.47070.paul@codesourcery.com> <49C099E4.9080503@redhat.com> In-Reply-To: <49C099E4.9080503@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200903181015.24614.paul@codesourcery.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Blue Swirl , Avi Kivity On Wednesday 18 March 2009, Avi Kivity wrote: > Paul Brook wrote: > >> This version uses a C tool to parse the options file instead of Perl > >> script. I also added HXCOMM for comment purposes. > >> > >> Does this work on Windows? > > > > I'm pretty sure it doesn't work in cross environments. > > Just have qemu-user run the thing. That's not going to work for several reasons: - You might not be building qemu-user. - qemu-user only supports a very small subset of systems. e.g. it's no use for linux->windows cross builds, which I expect to be the most common case - The necessary runtime libraries might not be installed. Even if they are, qemu probably doesn't know where to find them. Paul