[boost] Re: How to handle name mangling in "versioned" toolsets?

From: David Abrahams (dave_at_[hidden])
Date: 2004-06-28 09:33:21

"John Maddock" <john_at_[hidden]> writes:

> At present we have two types of toolsets:
>
> 1) Unversioned toolsets such as "intel-win32", which produce unversioned
> toolset suffixes to library names, "iw" in this case.
>
> 2) Versioned toolsets such as "intel-win32-7.1-vc6-stlport-4.5.3" which
> produce versioned toolset suffixes to library names, "iw71" in this case.
>
> This produces a problem with the autolinking code which can take either
> approach, but not both (or at least not both auto-magically, and this is
> causing some regression test failures at present).  In other words I'm
> asking for some kind of consistent policy here;  note that if the choice is
> to consistently use "versioned" toolsets then we're committing ourselves to
> constantly updating the build system and autolinking code to keep up with
> new compiler releases.  So, I guess I'm leaning towards "unversioned"
> mangled toolset names, but would like more some feedback, so: what does
> everyone else think?

It seems to me that versioned mangling should only be neccessary where
it indicates an ABI change, so indicating which version of the intel
compiler you're using is pointless -- unless you want to consider ODR
violations caused by verion-specific workarounds in header files?

-- 
Dave Abrahams
Boost Consulting
http://www.boost-consulting.com