I just tried to set those path with:
set PATH=E:\gdal111_32bit_msvc2010\bin;%PATH%
set PYTHONPATH=E:\gdalautotest-1.11.0\pymod
set GDAL_DATA=E:\gdal111_32bit_msvc2010\data
CMD shows me the same message as below.
-------- Original Message --------
Subject: Re: [gdal-dev] gdal autotest with gdal 1.11 (msvc2010)
From: Mateusz Łoskot <mate...@loskot.net>
To: David Tran <david.t...@hsr.ch>
Date: Saturday, 26. April 2014 21:45:53
On 26 April 2014 21:16, David Tran <david.t...@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#TestingonWindowsusingoldbindings
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@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
