[Boost-build] Mangling target output directories

Subject: [Boost-build] Mangling target output directories
From: Belcourt, Kenneth (kbelco_at_[hidden])
Date: 2012-07-16 16:46:36

Hi,

Forgive me if this has been discussed before but I now see the compiler name (icpc) showing up in the target output path, e.g.

intel-darwin.compile.c++ ../bin.v2/libs/mesh/build/intel-darwin-icpc/debug/case_insensitive_string.o

this with trunk.  Can someone explain why this is an improvement over just, e.g. intel-darwin, and what the driver is for this additional component?  I'm concerned about memory / disk consumption for our internal projects (which have very long paths already due to heavy use of features), as well as for testing reasons.

-- Noel