Alain I think the solution that Tamas proposed for that problem is not to automatically set the environment variables, but instead to modify the GDAL core installer to store the installation location in the registry and then have the Python bindings read it and initialize GDAL by calling appropriate GDAL functions. This solution would eliminate the need to set the environment variables. For more information, review the long discussion on the gdal-dev list for this from a couple of weeks ago.
(Tamas, correct me if I'm wrong about your proposal. And sorry I have not had time to test it myself yet...) Jason -----Original Message----- From: gdal-dev-boun...@lists.osgeo.org [mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Alain Cembro Sent: Tuesday, January 25, 2011 11:31 AM To: firstname.lastname@example.org Subject: Re: [gdal-dev] Problem with GDAL Python bindings and ECW format under Windows --- On Tue, 1/25/11, Ivan Lucena <ivan.luc...@pmldnet.com> wrote: > Do you have the GDAL_DRIVER_PATH environment variable set > on your Windows system? > > C:\>echo %GDAL_DRIVER_PATH% > C:\Apps\GDAL\bin\gdalplugins Ivan, You are right, I forgot to set that variable. Now it is working. Thank you very much ! Tamas, Could you improve the Windows GDAL installer, so that it automatically sets the environment variables (GDAL_DATA and GDAL_DRIVER_PATH), and adds the GDAL binaries path to the PATH environment variable ? Thanks ! _______________________________________________ gdal-dev mailing list email@example.com http://lists.osgeo.org/mailman/listinfo/gdal-dev _______________________________________________ gdal-dev mailing list firstname.lastname@example.org http://lists.osgeo.org/mailman/listinfo/gdal-dev