13 Mar
2015
13 Mar
'15
10:18 p.m.
AMDG On 03/13/2015 04:01 PM, Andrey Semashev wrote:
On Saturday 14 March 2015 00:29:56 you wrote:
Which makes me wonder. (a) When will MS get around to fix this in Windows? (I suspect "never" is the answer). (b) AFAIK, there is Windows API that can work with long paths (32767 chars or something?). Can bjam be updated to use these API to work around the problem?
It probably can. It means more platform specific code, though, as b2 currently just calls fopen.
(c) As an alternative, bjam could have an option to compress the path to a shorter hash value.
b2 --hash (reduces the path to an md5 hash) b2 --abbreviate-paths (shorter but still somewhat human readable) In Christ, Steven Watanabe