Re: [Boost-build] Windows Develop Tests Failing

Subject: Re: [Boost-build] Windows Develop Tests Failing
From: Raffi Enficiaud (raffi.enficiaud_at_[hidden])
Date: 2015-03-20 11:49:36

Le 19/03/15 19:24, Steven Watanabe a écrit :
> On 03/19/2015 11:03 AM, Raffi Enficiaud wrote:
>> Le 19/03/15 16:22, Steven Watanabe a écrit :

Thread from boost.devel list, sorry for cross posting.

>>>
>>> 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?
>
> No there isn't.  You can get the cwd and
> you can join and normalize paths, though,
> so it wouldn't be very hard to add.

Right. Do you think it is better to put that in the .jam files instead?
I do not know exactly what is computed when we arrive at this point: are 
those expanded commands from the rules?
BTW, is it possible in the .c code to call commands from the .jam files?

>
>> 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).
>>
>
>    I think the first step to handling this would
> be to make sure that Boost.Build handles UNC
> paths correctly.  Once we can pass these paths
> through correctly, we can worry about converting
> paths to UNC.
>
> Right now, I would be somewhat surprised if
> this worked:
>
> exe test : "\\\\?\\C:\\boost\\source.cpp" ;
>

This is not clear to me what happens between this declaration and the 
failing "fopen" we are referring to. If at some point relative paths are 
used, the test you are proposing would not tell us anything.

Best,
Raffi