Boost build can exceed Windows max path length limit

[anonymous]

I have been building boost successfully on Windows since 1.33. I usually extract boost do a directory such as:

d:\boost_1_44_0

With 1.44, for the first time I noticed that some binaries were (silently) failing to appear in the build directory. Viewing the build directories, I suspected we were exceeding the windows path limit (256?).

When I renamed to root folder to d:\b, the build suceeded.

I'm afraid I didn't keep the build log, but kept the build command:

bjam toolset=msvc-10.0 link=static runtime-link=static,shared variant="debug,release" threading="multi" define="_SECURE_SCL=0" debug-symbols="on" debug-store=database address-model=64 pch=off

I suspect its the long list of options that have extended the path length.

Platform: Windows 7 x64 Enterprise.

[Steven Watanabe]

You can use --abbreviate-paths or --hash to make the paths shorter.

[David Ward <davidjward30@…>]

Workaround confirmed. Thanks.

[Riona]

You can try Long Path Tool.