Boost logo

Boost-Build :

From: David Abrahams (dave_at_[hidden])
Date: 2006-09-19 22:55:09

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

> Just when I thought everything was sweetnes and light, up pops another one:
> Testing with Intel on Win32, the libraries are being named for example:
> Creating library
> ..\..\..\..\..\bin.v2\libs\config\test\link\test\intel-win-8
> .1\release\threading-multi\link_test-81-mt-1_35.lib and object
> ..\..\..\..\..\bi
> n.v2\libs\config\test\link\test\intel-win-8.1\release\threading-multi\link_test-
> 81-mt-1_35.exp
> So with a compiler-version-number, but without a "iw" toolset name.
> The autolink code expects the reverse: for example in this case it would be
> "link_test-iw-mt-1_35.lib".
> I believe the rationale for not versioning the intel toolset, is that what
> matters is the msvc compiler targeted, not the intel compiler version as far
> as binary compatibility is concerned, so basically bbv1 chickened out of
> versioning the toolset names, and the auto-link code followed.

Except that libraries may have #ifdefs that change their ABIs based on
which compiler/version is being used. I think you need the toolset
name in there.

Dave Abrahams
Boost Consulting

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at