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? Bruce Sherwood --------------------------- iconv.dll intl.dll libatk-1.0-0.dll libatkmm-1.6-1.dll libcairo-2.dll libcairomm-1.0-1.dll libfontconfig-1.dll libfreetype-6.dll libgdk-win32-2.0-0.dll libgdk_pixbuf-2.0-0.dll libgdkglext-win32-1.0-0.dll libgdkmm-2.4-1.dll libglade-2.0-0.dll libglademm-2.4-1.dll libglib-2.0-0.dll libglibmm-2.4-1.dll libgmodule-2.0-0.dll libgobject-2.0-0.dll libgthread-2.0-0.dll libgtk-win32-2.0-0.dll libgtkglext-win32-1.0-0.dll libgtkmm-2.4-1.dll libpango-1.0-0.dll libpangocairo-1.0-0.dll libpangoft2-1.0-0.dll libpangomm-1.4-1.dll libpangowin32-1.0-0.dll libpng12.dll libsigc-2.0-0.dll libxml2.dll zlib1.dll 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),[snip] 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.