Hi,

As for me - 2.0 works fine. Also QGIS build with 1.10.1 works on 2.0 very stable. Sorry screenshot on Russian, but I highlight the GDAL versions line

Best regards,
    Dmitry

16.12.2014 13:27, Even Rouault пишет:
Le mardi 16 décembre 2014 11:06:14, Vincent Schut a écrit :
Folks,

I'd like to use gdal-trunk (e.g. 2.0) for all the new features and
improvements, but I wonder about its compatibility with other software.
Is gdal 2.0 supposed to work transparently with libraries/programs that
used to link against gdal 1.11, e.g. qgis, postgis, etc.?
Vincent,

They mostly work unmodified, although you could run into a few problems if
opening a dataset with curve geometries in QGIS for example (but there be some
work to use OGR curve geometries in QGIS soon)


Reason I ask is I get a configure error with postgis trying to find gdal:

RASTER: Raster support requested
checking for gdal-config... /usr/local/bin/gdal-config
checking GDAL version... 2.0.0
checking for OGR enabled... yes
checking gdal.h usability... yes
checking gdal.h presence... yes
checking for gdal.h... yes
checking ogr_api.h usability... yes
checking ogr_api.h presence... yes
checking for ogr_api.h... yes
checking cpl_conv.h usability... yes
checking cpl_conv.h presence... yes
checking for cpl_conv.h... yes
checking for library containing GDALAllRegister... no
configure: error: could not find GDAL

the last line ("checking for library containing GDALAllRegister...")
takes a long time and then fails...
I know PostGIS has a continuous testing system tracking GDAL trunk, so I'd say
the issue is more on your side. GDALAllRegister is definitely a symbol that
still exists in GDAL 2.0dev

http://debbie.postgis.net:8080/job/GDAL_PostGIS_Regress/2074/consoleFull

Even

Thanks,
Vincent.
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev

_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Reply via email to