|
Boost-Build : |
Subject: Re: [Boost-build] Prevent building when exceeding Windows' path length limit
From: Rene Rivera (grafikrobot_at_[hidden])
Date: 2011-05-18 12:08:17
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?
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org (msn) - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim,yahoo,skype,efnet,gmail
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