[gdal-dev] gdal autotest with gdal 1.11 (msvc2010)

[Even Rouault]

> set PYTHONPATH=E:\gdalautotest-1.11.0\pymod

This is wrong. It should rather point to something like (don't copy that 
blindly. The end is certainly wrong)

e:\gdal111_32bit_msvc2010\swig\python\build\lib.win32-3.3

But actually, just running "python setup.py install" in swig/python should be 
enough to install the bindings, and avoid setting PYTHONPATH at all.

> 
> -------- Original Message  --------
> Subject: Re: [gdal-dev] gdal autotest with gdal 1.11 (msvc2010)
> From: Mateusz Łoskot <mateusz at loskot.net>
> To: David Tran <david.tran at hsr.ch>
> Date: Saturday, 26. April 2014 21:45:53
> 
> > On 26 April 2014 21:16, David Tran <david.tran at hsr.ch> wrote:
> >> hi
> >> 
> >> how does gdal autotest work? i compiled gdal 1.11 with vc10 and
> >> installed
> >> 
> >> python 3.4 and run_all.py:
> >>> Traceback (most recent call last):
> >>>    File "E:\gdalautotest-1.11.0\run_all.py", line 30, in <module>
> >>>    
> >>>      import gdaltest
> >>>    
> >>>    File "pymod\gdaltest.py", line 37, in <module>
> >>>    
> >>>      from osgeo import gdal
> >>> 
> >>> ImportError: No module named 'osgeo'
> > 
> > You need toset PATH, PYTHONPATH and GDAL_DATA.
> > See these notes:
> > http://trac.osgeo.org/gdal/wiki/TestingNotes#TestingonWindowsusingoldbind
> > ings and use your paths to tell Python where to find GDAL bindings inside
> > your build tree.
> > (Ignore it says old-gen bindings).
> > 
> > Best regards,
> 
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev

-- 
Geospatial professional services
http://even.rouault.free.fr/services.html