Re: [gtkmm] gtkmm-2.4 on MSVC

["Murray Cumming" <murrayc murrayc com>]

> A few weeks ago I set out to reach a similar goal, but to my shame the
> attempt petered. The reason was that fixing the linking problems required
> a
> dllimport/dllexport to be added in front of all class declarations (in the
> .hg and .ccg files to keep those changes), plus some other places, namely
> statically declared functions in .ccg files and all global objects, which
> should keep their 'extern' specifier in their declaration. Well, I tried
> to
> disentangle the m4 macro files but didn't have enough time to pursue.

You probably want to put these directly into the .hg files, though you
might find somewhere appropriate in glibmm/tools/m4/class_*.m4.

See glibmm/docs/internal/ for fuller information about our code generation.

I suggest that you base the macro on the one from libsigc++.

Didn't this work already with gtkmm 2.0, or was that just for static
libraries?

> So Tim, I would gladly join up, but unless someone explains exactly what
> should be added to which m4 files, I'm afraid we are beyond a simple
> configuration issue. We could make a lot of changes to the post-m4 .h and
> .cc files but those changes would be lost at next version. (I tried to do
> that by the way, and I think I got it to link cleanly. However there were
> still some issues probably revolving around some msvc-template stuff I
> didn't have the energy to investigate upon).

Murray Cumming
murrayc murrayc com
www.murrayc.com
www.openismus.com