$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
From: Vladimir Prus (ghost_at_[hidden])
Date: 2004-10-04 07:19:19
Tony Juricic wrote:
> "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.
I was thinking that we can use the same scheme which is used for installed
target naming for directories. E.g. a directory would be named gcc-mt-d
instead of gcc/debug/threading=multi
- Volodya