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]
> 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
>> 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?
> 260 characters for the lose. :(
> Unsubscribe & other changes:
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk