Changes between Version 4 and Version 5 of TestingNotes

Timestamp:

Nov 25, 2007, 8:44:58 PM (16 years ago)

Author:

Mateusz Łoskot

Comment:

Added notes about running gdalautotest on Windows, also with GDAL builds made using Visual C++ 8.0

TestingNotes

@@ -32 +32 @@
 
 The [wiki:Buildbot] runs will run the gdalautotest suite as well.
+
+=== Testing on Windows using old bindings ===
+
+After you have downloaded the gdalautotest package, you need to check following things:
+
+ * You have GDAL build using Microsoft Visual C++ compiler
+ * GDAL DLL is available in one of [http://msdn2.microsoft.com/en-us/library/ms682586.aspx searched location]. Simple solution is to add path to directory with GDAL DLL to the PATH environment:
+{{{
+set PATH=C:\software\gdal;%PATH%
+}}}
+ * Set PYTHONPATH environment variable, so old-gen bindings can be found:
+{{{
+set PYTHONPATH=C:\software\gdal\pymod
+}}}
+ * Set GDAL_DATA location:
+{{{
+set GDAL_DATA=C:\software\gdal\data
+}}}
+
+It's a good idea to run tests using full path to Python executable:
+{{{
+C:\software\gdal
+svn checkout https://svn.osgeo.org/gdal/trunk/autotest
+cd autotest
+C:\Python24\python.exe run_all.py
+...
+}}}
+
+==== Visual C++ 8.0 Notes ====
+
+If you use Microsoft Visual C++ in version 8.0 (from Microsoft Visual Studio 2005), there are a few additional steps required. Python 2.4 and 2.5 is built using Visual C++ 7.0 and 7.1. The Visual C++ 8.0 generates manifest that describes all runtime dependencies of GDAL on Visual C++ libraries. From MSDN article [http://msdn2.microsoft.com/en-us/library/ms235624(VS.80).aspx  Visual C++ Libraries as Shared Side-by-Side Assemblies]:
+
+ Visual C++ libraries cannot be used by a C/C++ application without a manifest binding the application to these libraries. If a C/C++ application that depends on a Visual C++ library does not use a manifest, then an attempt to load the Visual C++ library as a dependent DLL from the application-local folder will result in an error message indicating that this is an unsupported way of loading a Visual C++ library.
+
+Because Python binaries were built using older Visual C++, they do not support manifests. In order to run GDAL Autotest package against GDAL DLL and Python bindings built using Visual C++ 8.0, you need to take following additional steps:
+
+ * Prepare manifest for Python:
+   * Create file python.exe.manifest
+   * If you've built GDAL in release (non-debug) mode, paste following definition to the manifest file:
+{{{
+<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
+<assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
+  <dependency>
+    <dependentAssembly>
+      <assemblyIdentity type='win32' name='Microsoft.VC80.CRT' version='8.0.50727.762' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' />
+    </dependentAssembly>
+  </dependency>
+</assembly>
+}}}
+   * If you've built GDAL in debug mode, paste this:
+{{{
+<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
+<assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
+  <dependency>
+    <dependentAssembly>
+      <assemblyIdentity type='win32' name='Microsoft.VC80.DebugCRT' version='8.0.50727.762' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' />
+    </dependentAssembly>
+  </dependency>
+</assembly>
+}}}
+
+ * Add location of runtime libraries files to PATH environment variable. It's important to set proper path depending on GDAL build configuration:
+   * Release mode:
+{{{
+set PATH=C:\Program Files\Microsoft Visual Studio 8\VC\redist\x86\Microsoft.VC80.CRT;%PATH%
+}}}
+   * Debug mode:
+{{{
+set PATH=C:\Program Files\Microsoft Visual Studio 8\VC\redist\Debug_NonRedist\x86\Microsoft.VC80.DebugCRT;%PATH%
+}}}
+
+Note, the paths used above are based on default installation of Visual C++.
+
+If you combine these additional steps with steps explained in the bullet above, you should be ready to run GDAL Autotest.
 
 == Locale Testing ==