Boost logo

Boost :

From: Robert Ramey (ramey_at_[hidden])
Date: 2005-05-22 22:59:14


I've looked at this a tiny bit. Here are the facts as I understand them

a) According to www.boost.org/more/separate_compilation.html Autolinking
will be enabled only if BOOST_ALL_NO_LIB and BOOST_SERIALIZATION_NO_LIB are
not defined. The auto link code in the serialization library is written to
conform to this

b) Two platforms - MSVC and VC7 - fail to link for lack of libraries whose
name signatures suggest auto-linking is enabed during compilation. That is
neither of the two macros above seems to be defined.

c) Other platforms which implement autolinking - VC 7.1, VC 8.0, Borland and
CW don't seem to have any problems linking.

So I believe there is some issue re autolink with these particular
compilers. It may be an error in the serialization library or some
compiler/preprocessor quirk.

I went back to the posts referenced and at this point don't doubt my
original conclusions.

Robert Ramey

JOAQUIN LOPEZ MU?Z wrote:
> I'd like to know which the circumstances are
> under which Boost.Serialization autolinking feature
> kicks in.
>
> Last time I discuseed with Robert about this
> (see http://lists.boost.org/MailArchives/boost/msg78596.php)
> seemed that autolinking won't affect programs
> that are only including boost/serialization/* headers
> but *not* including any of *_?archive.hpp.
> But recent tests in the mslater regression runner
> (for instance http://tinyurl.com/a3n6u) suggest
> that this may not longer be true. Clarification,
> please? Thank you,
>
> Joaquín M López Muñoz
> Telefónica, Investigación y Desarrollo
>
> _______________________________________________
> Unsubscribe & other changes:
> http://lists.boost.org/mailman/listinfo.cgi/boost


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk