From: David Tonge (david.tonge_at_[hidden])
Date: 2004-03-12 08:22:07
Vladimir,
> I actually though that we should have "polymorphic archive" -- one
whose
> operations are virtual. It would have a number of derived class which
wrap
> existing archives in a polymorphic interface.
That sounds cool. It would save me a lot of heartache if I wanted to
use a new type of archive. Right now I have a header which #includes
all of the archives I might ever use, and I have to put that header in
every file before I #include export.hpp.
> Maybe, you could try tweaking the Jamfile so that library is build as
> dynamic and try your test?
Good point. I tried adding the section below (which is based on the
same section in date_time's jamfile) to the jamfile (btw, jamfiles are
very cool). Anyway, that did lead to a .dll, but I guess there aren't
__declspec(dllexports) in the right places because the .dll had no
exported functions (and because of that, the linker didn't bother to
produce a .lib for the stubs). I guess we might need source code
changes.
DT
----
dll boost_serialization
: ## sources ##
../src/$(SOURCES).cpp
: ## requirements ##
<include>$(SPIRIT_ROOT)
<include>$(BOOST_ROOT)
<sysinclude>$(BOOST_ROOT)
<borland><*><cxxflags>-w-8080
<msvc><*><cxxflags>-Gy
<vc7><*><cxxflags>-Gy
<vc7.1><*><cxxflags>-Gy
<define>BOOST_ALL_DYN_LINK=1
# the common names rule ensures that the library will
# be named according to the rules used by the install
# and auto-link features:
common-variant-tag
: ## default-build
debug release
#<runtime-link>static <threading>single
#<runtime-link>static/dynamic
#<runtime-link>dynamic
<runtime-link>dynamic <threading>multi
;