From: John Maddock (john_at_[hidden])
Date: 2006-09-19 14:18:18
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:
.1\release\threading-multi\link_test-81-mt-1_35.lib and object
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
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.
It would be easy enough to change the autolink code to accept names
versioned on either the msvc version or the intel version, or - god
forbid - both. But it would require some discussion on the Boost list to
decide what the right thing to do is.
Probably the easiest course of action, and one that won't hold up the 1.34
release is to do what bbv1 did and add an "iw" toolset name with no compiler
And finally, I hope :-) the borland compiler.
I'm seeing a whole lot of errors along the lines of:
Support for Borland compilers older than BCB2006 is deprecated in Boost 1.34
TLIB 4.5 Copyright (c) 1987, 1999 Inprise Corporation
Warning: 'link_test' not found in library
Fatal: Unable to open file 'LIBLINK_TEST-BCB-MT-1_35.LIB'
"C:/cpp/Borland/CBuilder6/Bin/bcc32.exe" -v -q -tWC -tWR -tWC -WM- -tWM
It seems that the lib's are being named correctly (but I haven't checked
them all), but the link fails because the directory that contains the lib
isn't in the lib search path. Adding a -Lpath-to-lib on the command line
would fix that.
Hopefully that's the lot for now,
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk