Re: [boost] Windows Develop Tests Failing

Subject: Re: [boost] Windows Develop Tests Failing
From: Raffi Enficiaud (raffi.enficiaud_at_[hidden])
Date: 2015-03-19 13:03:19

Le 19/03/15 16:22, Steven Watanabe a écrit :
> AMDG
>
> On 03/19/2015 08:27 AM, Raffi Enficiaud wrote:
>>
>> fopen can also work with UNC path, which does not have the MAX_PATH=255
>> limitation:
>> - https://msdn.microsoft.com/en-us/library/yeby3zcb.aspx
>> -
>> https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247%28v=vs.85%29.aspx
>>
>>
>> A possible workaround would be to prefix the path name with "\\?\" then.
>>
>
> It's a bit more complicated then that, since
> \\?\ requires an absolute path.  Also, I
> thought that you need to use wchar_t as well.

Right, I made an attempt and most of the files are in relative path. Is 
there any function in C retrieving  the full path? Also, I think that 
the full chain should be in full path as well (eg mkdir in common.jam 
should prefix the absolute path with \\?\ to work).

>
>> If there is an intermediate cmd.exe, I suspect passing filename with the
>> previous prefix works as well.
>>
>> How to debug at which point things start failing?
>>
>
> This particular failure happens towards the end
> of function.c.  You can find it by searching for fopen.
>