Re: Static linking on Windows
- From: Bruce Sherwood <Bruce_Sherwood ncsu edu>
- To: gtkmm-list gnome org
- Subject: Re: Static linking on Windows
- Date: Wed, 07 Nov 2007 12:06:12 -0500
Thanks. Just for grins I tried the experiment of trying -static and
indeed the build failed miserably.
With shared libraries, I seem to need to add all of the dll's listed
below, which increases the length of the Python module (compared to
using Windows-specific code) from 4 MB to 40 MB. Not a show-stopper, but
a bit annoying as a download to add to Python. The crude way I figured
out what dll's I needed was to try running the program from a typescript
and get told that I was missing a library, then copying that library
into the module's directory (I had previously changed the name of the
MinGW directory to xxxMinGW to exclude finding the dll there).
Is there a more intelligent way to identify which dll's I need?
Could some of these be loaded statically even if not all of them can?
Murray Cumming wrote:
On Tue, 2007-11-06 at 14:57 -0500, Bruce Sherwood wrote:
I've inherited gtkmm code used on Linux and am trying to use it on
Windows. The current build machinery requires the presence of a large
number of .dll files, which I can pass along to end users (who rarely
will already have gtk installed),
It's fairly well known that GTK+ can't be linked statically, because it
loads some modules at runtime.
I think your life will be simpler if you just ship the DLLs. That seems
fairly normal on Windows anyway.
] [Thread Prev