RE: How to recreate GLib binary bundle for Windows

Hi Dieter,

many many thanks for your quick and exhaustive reply. I own a MSVC10 license, using it allows me to obtain the PDB files, too that
can ease Windows development but then I will have runtime DLLs built with MinGW and import libraries built with MSVC, and I do
not think this is very coherent. I already use the lib.exe tool to create import libraries from MinGW build, but in this case I cannot
obtain the above useful PDB files.

Anyway, status is now clear to me, I will try to manage my environment accordingly to my needs.

Best regards,

From: Dieter Verfaillie [dieterv optionexplicit be]
Sent: Wednesday, April 04, 2012 9:21 PM
To: Pampolini Matteo
Cc: gtk-devel-list gnome org
Subject: Re: How to recreate GLib binary bundle for Windows

On Wed, 04 Apr 2012 16:29:22 +0200, Matteo Pampolini wrote:
>  I'm currently working on a GStreamer-based Windows application,
> until
> now the binary version of GLib that comes with the GTK+ binary bundle
> was OK for me, but then I had to recompile GLib itself. With some
> issues I was finally able to recompile GLib with both MinGW and MSVC
> 10, this because I'm using MinGW to recompile GStreamer but I also
> have an MSVC project that refers to GLib through GStreamer.
>  Everything seems fine, but when I start my application I get an
> error
> on a libffi missing symbol. My suspect is that I probably made some
> confusion with the two sets binaries: which one should I use, the
> runtime DLLs generated by MinGW or the ones generated by MSVC? In
> simple words, which of them are distributed inside GTK+ binary
> bundle?

The win32 gtk+-bundle and separate per package binaries on are built with
a MinGW/MSYS installation on a window xp machine. Those packages
also include msvc compatible import libraries built with the
lib.exe version included with the Windows Server 2003 R2 Platform
SDK from

The original maintainer used msvc 6 which is next to
impossible to get these days and msvc 9 for some modules, but I
lack a visual studio license, hence the SDK.

I'm currently keeping track of the scripts used to build the
packages and bundle plus an informative description of the
setup provided by the original maintainer here:

Please don't hesitate to ask if something should be unclear,

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