[Boost-build] Too many features generatesa path beyond Windows max 260 chars

From: Eoin (eoin-keyword-boost.jam.dca6c0_at_[hidden])
Date: 2006-10-20 08:13:39

Hello all,

On a current project I ran into a build error which I am pretty sure is 
the result of exceeding Windows maximum path length. The library in 
question was boost.serialization and the offending path was the 
monstrous one which follows

C:\Develop\C++\Libraries\Boost\boost\bin.v2\libs\serialization\build\msvc-8.0\...
...release\address-model-64\architecture-x86\asynch-exceptions-on\...
...dht-support-on\link-static\logging-none\runtime-link-static\...
...threading-multi\libboost_serialization-vc80-mt-s-1_35.lib

This totals 263 characters and BBv2 aborted with an error trying to 
create the file. The dht-support and  logging are features added by the 
libtorrent library ver 0.11 rc.

This raises a second important question. While propagation of these 
features down to my project which relies on libtorrent makes perfect 
sense, propagating them back to the Boost libraries isn't beneficial as 
they know nothing of those features and who presumably compile 
identically regardless of how they are set.

In this particular case there are a number of solutions, e.g. moving the 
Boost directory path, but still it does mean you have your back right up 
against the wall in terms of directory layout or future feature additions.

This is just an observation of mine and not meant to be critical of the 
boost.build v2 system (in fairness the Windows max path length seems 
much to low). I am very interested to hear form those more familiar with 
BBv2 as to whether these issues have cropped up before, and have 
workaround been proposed.

Kind regards, Eoin.