Rather than introduce a DLL into the system directory, why not statically link the code into the bindings themselves, when possible? Or document the appropriate logic for doing it with win32 functions (registry functions, LoadLibrary, GetProcAddress) and allow the bindings to make those calls themselves? Most languages have a way to access win32 functions. It just seems unnecessarily risky and complicated to create a new DLL and put it in the system directory, IMHO.
Jason From: Tamas Szekeres [mailto:szeker...@gmail.com] Sent: Tuesday, January 25, 2011 5:30 PM To: Jason Roberts Cc: gdal-dev@lists.osgeo.org Subject: Re: [gdal-dev] Problem with GDAL Python bindings and ECW format under Windows 2011/1/25 Jason Roberts <jason.robe...@duke.edu> Tamas, Are you still planning to implement the registry-based approach? I ask because you seemed in favor of avoiding modifying PATH, if at all possible (a position I agree with), and the registry approach would eliminate that need while still making GDAL + bindings “just work”. Jason, As the time permits, I'll do some tests in this regard. Since not only the PATH, but other environment settings should also be applied, I consider a bootstrap dll to be implemented for all bindings. The only issue is that where to place this dll file to make it available for all for all bindings to load. May be into the system directory (?) Best regards, Tamas
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
