Re: [gtkmm] Help! compile gtkmm2.2.5 with mingw under Windows.



At 04:30 PM 7/24/2003 +0200, Frank Naumann wrote:
Hello!

> > I downloaded libsigc++ 1.2.5, compiled it with mingw, compiled it with
> > MSVC, compiled and run all tests under mingw and MSVC.
>
> Is libsigc++ built as a DLL ?

Now, as static library. I used the MSVC project files shipped with
libsigc++ (btw. there are two folders with MSVC Net2003 project files and
there ís a typo in a filename).

You should build it as a shared library (DLL) only (configure --disable-static). Same for gtkmm. And then hopefully these linking errors related to undefined symbols will disappear.

> Let me repeat my question : did you use
> libtoolize/aclocal/automake/autoconf to recreate libtool and the
> configure script or do you use the ones provided in the official source
> tarball ?

I used the ones provided in the tarball. I thought gtkmm have uptodate
libtool? I will recreate it and try again (but I remember this was not so
easy last time I tried).

gtkmm-2.2.5 builds out of the box on my win2k box. No need to recreate the libtool/configure scripts.

> > So my question, what environment do you used to compile gtkmm under mingw?
>
> cygwin + the latest mingw distribution (currently with gcc-3.2.3).

Is there a significant difference between cygwin and msys as build
environment (especially for the libtool/auto* stuff)?

I don"t really know. I'm happy with the tools provided by the cygwin distribution. You just have to be careful with your mount points and the way directory names are handled.

> See http://bugzilla.gnome.org/show_bug.cgi?id=112809

Ok. Btw. is this the recommended way of supporting MSVC (I mean the
project files; theoretically it's also possible to use the
Makefiles/libtool).

I guess people are more familiar with project files but you should ask the question on bugzilla if you intend to provide support/submit patches for VisualStudio 2003.

Cedric



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]