Re: [Boost-build] Prevent building when exceeding Windows' path length limit

Subject: Re: [Boost-build] Prevent building when exceeding Windows' path length limit
From: Joshua Boyce (raptorfactor_at_[hidden])
Date: 2011-05-19 13:26:49

Why does the build system not use the wide/Unicode APIs under Windows? This
would allow use of paths up to (approx) 32767 characters long...

On Thu, May 19, 2011 at 2:21 AM, Matthew Chambers <matt.chambers42_at_[hidden]
> wrote:

> On 5/18/2011 11:08 AM, Rene Rivera wrote:
>
>> On 5/18/2011 10:57 AM, Matthew Chambers wrote:
>>
>>> Having been bitten a few times by this in the middle of a build - at
>>> which point I had to restart with --hash - it got me thinking that this
>>> should be tested as much as possible before starting the action phase.
>>> Just run through all the target output paths and make sure they don't
>>> exceed MAX_PATH. How hard would this be to implement? It won't catch
>>> cases inside the actions of custom make targets, but it'd catch almost
>>> everything.
>>>
>>
>> Which MAX_PATH are you referring to? And how, or if, does it correspond to
>> the actual allowed max
>> path length of the filesystem used during the build?
>>
>
> http://msdn.microsoft.com/en-us/library/aa365247%28v=vs.85%29.aspx#maxpath
>
> 260 characters for the lose. :(
>
> -Matt
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost-build
>