Re: [boost] [build] File / path lengths difficult to manage on Windows

...

On a related note, is it unreasonable to ask that an --abbreviate-paths build of boost limit itself to 130 characters? I acknowledge that

From: Vladimir Prus On 13.11.2013 18:16, Ben Craig wrote: this

...

one is a bit harder to solve as there can be a large number of build "pivots" that all add to the path, but some clients (like me) need to layer other build pivot and version information on top of what boost already provides, and I need some amount of character wiggle room to make that happen.

I suppose you can always build with --hash to trade path readability for previty. It will replace all properties with just md5 checksum thereof.

- Volodya

I was not aware of --hash. That can do the trick on the build side. It would be nice for --hash and --abbreviate-paths to be documented better, but this will do. The file name lengths in the zip still need to be addressed though.