[boost] Re: Long toolset names

From: Tony Juricic (tonygeek_at_[hidden])
Date: 2004-10-01 10:09:58

"Aleksey Gurtovoy"  wrote:

> What should we do about the following Boost.Build toolsets which
> filename's length exceeds 31 characters:
>
>     tools/build/v1/como-win32-4.3.3-vc7.1-tools.jam
>     tools/build/v1/intel-win32-7.1-vc6-stlport-4.5.3-tools.jam

While boost build file and directory names are really self-explanatory, it
looks to me it is pushing it too far.
I don't have a problem with the length of file names (even if some
shortcuts, like I for intel, getting rid of dashes, and similar could help)
but build directory hierarchy is really getting too deep, especially when
you consider builds for various CRT linkage combinations.

As far as MS VS IDE is concerned, build directory names like "debug
runtime-static threading-multi" (with the space character) would make life
easier than directory tree like the current
"...debug/runtime-static/threading-multi" because the string "debug
runtime-static threading-multi" can become $(ConfigurationName) macro in
IDE.

This would be more helpful if you generate project configurations from IDE
but maybe also if you have some tool that automatically generates MS IDE
vcproj XML.

Tony