From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MXUSL-000223-JV for qemu-devel@nongnu.org; Sun, 02 Aug 2009 02:22:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MXUSG-0001wP-2J for qemu-devel@nongnu.org; Sun, 02 Aug 2009 02:22:04 -0400 Received: from [199.232.76.173] (port=44748 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MXUSF-0001wH-VL for qemu-devel@nongnu.org; Sun, 02 Aug 2009 02:21:59 -0400 Received: from moutng.kundenserver.de ([212.227.126.187]:54536) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MXUSF-0002n3-Ew for qemu-devel@nongnu.org; Sun, 02 Aug 2009 02:21:59 -0400 Message-ID: <4A753022.1090404@mail.berlios.de> Date: Sun, 02 Aug 2009 08:20:18 +0200 From: Stefan Weil MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Win32: Fix default prefix References: <1249068645-6893-1-git-send-email-weil@mail.berlios.de> <865C000A1E46452DA75315BE97C8B6DA@FSCPC> <5b31733c0908011446s340709c0q6a416aefaf00f1b9@mail.gmail.com> In-Reply-To: <5b31733c0908011446s340709c0q6a416aefaf00f1b9@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Filip Navara Cc: Anthony Liguori , Juan Quintela , qemu-devel@nongnu.org, Sebastian Herbszt Filip Navara schrieb: > On Sat, Aug 1, 2009 at 11:35 PM, Sebastian Herbszt wrote: > >> Stefan Weil wrote: >> >>> The old code resulted in wrong escape sequences: >>> >>> #define CONFIG_QEMU_SHAREDIR "c:\Program Files\Qemu" >>> >>> gcc warnings: >>> >>> vl.c:5708:20: warning: unknown escape sequence '\P' >>> vl.c:5708:20: warning: unknown escape sequence '\Q' >>> >> Looks like this got broken by "Generate config-host.h from config-host.mak" >> (create_config). >> >> >>> Windows can handle slash (/) path separators, >>> and QEMU already adds directories using slash, >>> so there is no need to fight with the correct number >>> of backslashes. >>> >> Do all versions handle them correctly? >> > > At least all NT-based versions do and I believe Win 9x handles them > correctly too. > > Best regards, > Filip Navara > > Even IBM BIOS and all versions of MSDOS I know accept slash and backslash in parameters for file system calls. So do all versions of Windows, too, Regards Stefan Weil