This is the mail archive of the
mailing list for the Cygwin project.
Re: pre-ITP: New category Gis?
Charles Wilson schrieb:
Reini Urban wrote:
I plan to ITP the following GIS packages in the next days.
Have to wait for some postgresql decisions upstream.
proj (but maybe Charles wants to keep his ITP)
gdal (includes libgeotiff, ogr and a python lib)
Wait. Does gdal include libgeotiff internally, or does it install the
actual libgeotiff DLL?
If the former, then you'd also need a separate geotiff ITP (and then
your gdal build could have the choice of using the external geotiff, or
its own compiled-in geotiff). If the latter...ick. I don't like that
Well, there's no conflict. libgeotiff is linked statically.
The gdal package is just is one really huge cyggdal-1.dll (3.3 MB).
And some gdal and ogr exe's, and the python module.
But libgeotiff, libtiff and so on is builtin.
gdal-devel will contain the static lib, import lib and headers.
or should gdal-python be seperated?
But I'll check if the included libtiff should be merged statically.
and how about dealing with:
* cygsqlite3.dll (jaari providing a shared lib?),
* cygpg.dll or pg.dll (rename upstream at postgresql?)
* your /usr/bin/cygproj-0.dll (dlopen'ed at run-time)
* using the jasper hack (GeoJP2)
and some more 6 external libs....
my current snapshot is at
http://xarch.tu-graz.ac.at/publ/cygwin/gis/gdal/ but this is not ready yet.
I think I'd prefer to keep my ITP for proj (and libgeotiff; if there's
no conflict between gdal using its own internal version, even with a
separate libgeotiff package installed on the same machine), but I've
been waiting for the hubbub to die down. (FYI: I work in a related
field, although not primarily focused on the open standards surrounding
Yes please. libgeotiff causes no problem. Good to have all.
FYI: I used to work in mapping also some time ago.
But I only worked with commercial packages, which was a pain.
Didn't even notice the announcement of a FreeGIS CD for linux.