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...<br><br><div class="gmail_quote">On Thu, May 19, 2011 at 2:21 AM, Matthew Chambers <span dir="ltr">&lt;<a href="mailto:matt.chambers42@gmail.com">matt.chambers42@gmail.com</a>&gt;</span> wrote:<br>

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