
"These macros will be undef'ed at the end of the header, further this header has no include guards - so be sure to include it only once from your library!" What is the rationale for the above? What happens if its violated. I'm sort of struggling implementind a dll version of the serialization library with autolink. The basic difficulty is that I would like to have the dlls mirror the structure of the the static libraries. That is libboost_serialization.lib libboost_wserializaton.lib depends on theabove wserialization.dll is both autolinked and uses serializaton.dll so Its kind of confusing. Robert Ramey

"These macros will be undef'ed at the end of the header, further this header has no include guards - so be sure to include it only once from your library!"
What is the rationale for the above? What happens if its violated. I'm sort of struggling implementind a dll version of the serialization library with autolink. The basic difficulty is that I would like to have the dlls mirror the structure of the the static libraries. That is
libboost_serialization.lib libboost_wserializaton.lib depends on theabove
wserialization.dll is both autolinked and uses serializaton.dll so Its kind of confusing.
I think I may have over stated that, more correctly: It's up to you to ensure that it is included only once for any give definition of BOOST_LIB_NAME, so obviously if you need to link to two or more libs then include it more than once with a different BOOST_LIB_NAME each time. John.
participants (2)
-
John Maddock
-
Robert Ramey