On Wed, Mar 19, 2003 at 04:44:08PM -0600, John Hunter wrote: > > I am building pygtkglext-0.0.2 using mingw. I am able to compile it > without incident, but when I try to import gtk.glext, I get a DLL > error. If I try and open either the gtkgl or gdkgl pyd files in > Dependency Walker, it has says it cannot find > /c/windows/system/python22.dll, which is a direct dependent of the > gdkgl module. > > The problem is that the paths are reversed. Every other dll that is > required has its path listed as, eg, c:\GTK\2.2\lib\some.dll. If I > look in the pyd binary file directly, sure enough the full string > /c/windows/system/python22.dll is in there, where as for other DLLs > just the DLL name is listed and the system finds the path to it with > dynamic linking, as it should. > > BTW, python22.dll *is* located in c:\windows\system. > > My question is: how is this screwball path getting inserted into my > binary file? I am building the module from a DOS shell. A recursive > grep of the src tree shows that only the 2 pyd files match the string > /windows/system. If I capture the output of the setup.py build, > /windows/system is not listed in any of the gcc or dllwrap commands. > > If anyone has seen something like this before, or has any advice about > how to diagnose the src of the problem or proceed, I'm much obliged. >
Sorry it took me a while to get to this. What it sounds like is that your python22 import library has that funky path embedded in it. Did you make the import library yourself, using the common instructions of using pexports and dlltool? Realize that whatever path you pass to --dllname of dlltool is going to be embedded verbatim in your import library. Make sure that you pass only python22.dll to the --dllname of dlltool when you make your import library! --jkl _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
