hi list, I had asked how to build new-generation Python binding on Windows for gdal, but got no answer. (I know that on Linux, "configure --with-python" does it. Couldn't find similar thing on nmake.opt)
I did "nmake /f makefile.vc" and "nmake /f makefile.vc install" It created gdal16.dll in \local_install\bin and _gdal.dll in \local_install\pymod. gdal.py (dated 2005-08-04) is copied in \local_install\pymod. I downloaded the GDAL Python Bindings executable installer for Python 2.4 from http://pypi.python.org/pypi/GDAL/ (but I cannot use GDAL Windows Binaries, I need to build customized drivers) After installation, it created C:\Python24\Lib\site-packages\osgeo\ that contains: _gdal.pyd, _gdal_array.pyd, _gdalconst.pyd, gdal.py Its gdal.py is different than that in \local_install\pymod\ My question is: is there a conflict on two versions of gdal.py and _gdal.dll vs _gdal.pyd? When I call gdal.SerializeXMLTree() or gdal.Open(), python.exe crashes. It can be tracked to gdal16.dll, which probably attributes to the above. Appreciate help on how to build GDAL Python binding on Windows. thanks, Shawn _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
