libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] [cygwin|mingw]: Add cross-compile support to cwrapper (take


From: Peter Rosin
Subject: Re: [PATCH] [cygwin|mingw]: Add cross-compile support to cwrapper (take 6)
Date: Fri, 27 Aug 2010 14:36:22 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2

Den 2010-08-27 08:25 skrev Peter Rosin:
> Den 2010-08-27 00:27 skrev Roumen Petrov:
>> Lets wine is correctly configured (Z: drive is linked to the file system 
>> root):
>> $ cd $WINEPREFIX/dosdevices
>> $ winepath -w `pwd`
>> Z:\%WINEPREFIX_CONVERTED_TO_BACKSLASHES%\dosdevices
>>
>> Now lets remove link:
>> $ rm z:
>> $ winepath -w `pwd`
>> \\?\unix\%WINEPREFIX_CONVERTED_TO_BACKSLASHES%\dosdevices
>>
>> So sed should remove leading //?/unix
> 
> This failures are probably comping from inside wine (no mention of

This failure is probably coming (fat fingers today...)

> "//?/unix" or "\\?\unix" in the winepath source), so probably won't
> be seen as failure by winepath. But, if you silently remove \\?\unix,
> then you'll end up with a path that is not complete with a drive
> letter. I think any \\?\unix prefix should be filed as a failure...

Hmmm, I dug deeper into the wine source and wine_unix_to_nt_file_name
in the dlls/ntdll:path.c file seems to sometimes prefix the path with
"\??\unix" (with two question marks), so you seem to have mistyped the
above (and not copy-pasted an actual session as I originally thought).
It also seems we can forget about the forward slash variant? But I'm
not regularly running wine, so someone who does should chime in with
verification.

Cheers,
Peter



reply via email to

[Prev in Thread] Current Thread [Next in Thread]