Parent Directory
|
Revision Log
Sticky Revision: |
pyshapelib: rewritten dbflib to use hand-crafted Python bindings instead of SWIG generated ones.
rewritten shapelib to use hand-crafted Python bindings instead of SWIG generated ones.
made a copy
* setup.py: Determine shp_dir correctly when run with bdist_rpm (dbf_macros): Remove a debug print
Update to newest shapelib and get rid of Thuban specific extensions, i.e. use the new DBFUpdateHeader instead of our DBFCommit kludge * libraries/shapelib/shpopen.c: Update to version from current shapelib CVS. * libraries/shapelib/shapefil.h: Update to version from current shapelib CVS. * libraries/shapelib/dbfopen.c: Update to version from current shapelib CVS. (DBFCommit): Effectively removed since shapelib itself has DBFUpdateHeader now which is better for what DBFCommit wanted to achieve. We're now using an unmodified version of dbfopen. * libraries/pyshapelib/dbflib_wrap.c, libraries/pyshapelib/dbflib.py: Update from dbflib.i * libraries/pyshapelib/dbflib.i (DBFInfo_commit): New. Implementation of the commit method. This new indirection is necessary because we use the DBFUpdateHeader function now which is not available in shapelib <= 1.2.10 (DBFFile::commit): Use DBFInfo_commit as implementation (pragma __class__): New. Kludge to remove the commit method when the DBFUpdateHeader function isn't available (_have_commit): New. Helper for the pragma kludge. * libraries/pyshapelib/setup.py (dbf_macros): New. Return the preprocessor macros needed to compile the dbflib wrapper. Determine whether DBFUpdateHeader is available and define the right value of HAVE_UPDATE_HEADER (extensions): Use dbf_macros for the dbflibc extension * setup.py (extensions): Add the HAVE_UPDATE_HEADER macro with value '1' to the Lib.dbflibc extension. This simply reflects the shapelib and pyshapelib updates
These files have been moved here from thuban/extensions/pyshapelib/ See there in the Attic for the older history.
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
[email protected] | ViewVC Help |
Powered by ViewVC 1.1.26 |