Synopsis - Issue Tracker

Add the usual machinery to support DSOs for MSVC.
The same infrastructure will allow to control
symbol visibility with gcc 4.0 and higher, greatly
enhancing library size and load times.
See http://www.nedprod.com/programs/gccvisibility.html
for more.

Hartmut, you once indicated you'd be interested
into working on this. Is this still the case ?
If so, can you assign this issue to you please ?

I can take this on. I would suggest however, to use a more neutral word than DLLEXPORT to express dynamic interface. Something like SYNOPSIS_API, which can take the value __declspec(dllexport/dllimport), depending on an external #define. Usually, this external define is provided by the VS.NET project system (something like SYNOPSIS_EXPORTS), but it can be controlled by a define as the first line of every implementation file (see boost::program_options or other boost dynamically linked libraries), which is more portable, although more verbose.

I will need some guidance on which interface should be exposed at first.

OK, sounds good. I agree SYNOPSIS_API would be a 
good name for the macro. As far as coverage is
concerned, I think the first goal might be to get
the tool applets in src/tools/ compile (and link !)
with MSVC, i.e. make whatever declarations are
required there 'public'.

Thanks !

(PS: I have checked in some modifications that
 may address your build problem on windows.
Please post about that to the list, or submit
a separate bug report, so we can track that down.)