Thnx for explaining Frank ;)
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/gdal-dev-gdal-config-file-lists-different-directories-for-libodbc-and-libodbcinst-tp5965096p5965120.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
_
Antonio,
I don't know much about the pre-built binaries for win32 except for what's
talked about here http://trac.osgeo.org/gdal/wiki/DownloadingGdalBinaries.
However, you might want to see what version of GDAL FwTools2.4.7
(http://fwtools.maptools.org/) is using for win32 binaries.
Sorry, i do
Hey Hannes,
I think most of your questions can be answered here
http://trac.osgeo.org/gdal/wiki/GdalOgrInPython. Have you seen this? It
covers how to install the Python bindings for GDAL 1.7.x and Python 2.x. I'd
pay attention to the Dependencies subhead -- there's a few libraries and dev
headers
It seems like swq.h belongs in /usr/local/include folder to fix the easy
install problem.
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/gdal-dev-GDAL-easy-install-problem-tp5577829p5619701.html
Sent from the GDAL - Dev mailing list archive at Nabble.com.
___
Thanks for the help Chaitanya,
Sorry about the late response. I saw the temporary fix with swq.h. I'm
confused about one aspect of this workaround though. It says that I should
copy the swq.h file into the gdal installed tree. So this is the step after
compiling gdal-1.7.2 ? For some reason it se
