Ah, yes - a Typical mistake on my part. All good, thanks a lot! Cheers, Mike.
On Mon, Jan 10, 2011 at 1:03 AM, Tamas Szekeres <[email protected]> wrote: > Michael, > > You probably did a full install which is not recommended if the Oracle > environment is not in place. Try removing the OCI plugin by the add/remove > option. > > Best regards, > > Tamas > > > > 2011/1/9 Michael Sumner <[email protected]> >> >> Awesome, thanks for this - I've really enjoyed the discussion too, a >> great deal of good information there. >> >> I downloaded and ran >> >> http://vbkto.dyndns.org/sdk/Download.aspx?file=release-1600-x64-gdal-mapserver\gdal-18dev-1600-x64-core.msi >> on Windows 7 64-bit. I removed an existing path reference to a build >> from your site, then started the installed "GDAL 18dev (MSVC 2010 >> Win64) Command Prompt" shortcut. On running "gdalinfo" I get two >> repeated popup errors: >> >> --------------------------- >> gdalinfo.exe - System Error >> --------------------------- >> The program can't start because OCI.dll is missing from your computer. >> Try reinstalling the program to fix this problem. >> --------------------------- >> OK >> --------------------------- >> >> and this in the command window: >> >> >> C:\Program Files\GDAL>gdalinfo >> ERROR 1: Can't load requested DLL: C:\Program >> Files\GDAL\gdalplugins\gdal_GEOR.dll >> 126: The specified module could not be found. >> >> ERROR 1: Can't load requested DLL: C:\Program >> Files\GDAL\gdalplugins\gdal_GEOR.dll >> 126: The specified module could not be found. >> >> Usage: gdalinfo [--help-general] [-mm] [-stats] [-hist] [-nogcp] [-nomd] >> [-norat] [-noct] [-checksum] [-mdd domain]* datasetname >> >> Otherwise it reports fine on a basic GeoTIFF. >> >> Thanks again, and I hope that small detail is of some use. >> >> Cheers, Mike. >> >> On Sun, Jan 9, 2011 at 11:51 PM, Tamas Szekeres <[email protected]> >> wrote: >> > Folks, >> > >> > Upon the inspiration on the recent conversation in this topic I've put >> > some >> > efforts to automate the creation of a generic GDAL installer derived >> > from >> > the distributions available at http://vbkto.dyndns.org/sdk/. >> > >> > Currently the following options are available from this site to install >> > and >> > use GDAL: >> > >> > 1. Download the .zip package extract it in some location and run >> > SDKShell.bat to run the commandline tools (this is the former approach) >> > 2. Use the core msi installer to install GDAL and use the installed >> > shortcut >> > to run the command line tools. Python users should install the python >> > bindings installer as well. >> > >> > In order to have the bindings work the location of the core files should >> > be >> > added to the PATH manually (this requirement will probably be removed in >> > the >> > future when the automatic loader approach is implemented at the >> > bindings) >> > >> > The core installer places an entry in the registry (currently in HKCU) >> > containing the install location which will allow the loader to find the >> > required components. >> > >> > This task is not yet complete, the following issues are to be handled or >> > reviewed in some way. >> > >> > 1. Side by side installation of the multiple versions is not yet >> > supported. >> > 2. Must review the license agreement (currently taken from the GDAL >> > site) >> > 3. Must review the product name >> > 4. Must review the installer design >> > 5. Must review the selectable features >> > 6. Loader approach to be implemented for the bindings >> > 7. Versioning rules should be clarified (should synchronize the registry >> > entries among the versions) >> > 8. Further fixes >> > >> > >> > The core installer is provided as a single wix project file the build >> > process is executed by the command line apps (candle.exe and light.exe). >> > I >> > will make the whole approach public as part to the -dev packages at >> > http://vbkto.dyndns.org/sdk/. By using this addition one can easily >> > rebuild >> > the installer after creating a customized GDAL build. >> > >> > The wix project file could also be included in GDAL source tree and a >> > new >> > target could be added in the gdal makefile for creating the installer >> > (the >> > CRT redistributable merge modules and the dependent dlls must be >> > available >> > during the build). Having the locations of the OSGeo4w files in place, >> > this >> > approach could easily generate the same installer for the OSGeo4w >> > bundle. >> > >> > >> > Any testing efforts / comments / wishes are graciously accepted. >> > >> > Best regards, >> > >> > Tamas >> > >> > >> > _______________________________________________ >> > gdal-dev mailing list >> > [email protected] >> > http://lists.osgeo.org/mailman/listinfo/gdal-dev >> > >> >> >> >> -- >> Michael Sumner >> Institute for Marine and Antarctic Studies, University of Tasmania >> Hobart, Australia >> e-mail: [email protected] > > -- Michael Sumner Institute for Marine and Antarctic Studies, University of Tasmania Hobart, Australia e-mail: [email protected] _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
