On Sun, Aug 2, 2015 at 8:12 PM, Even Rouault <even.roua...@spatialys.com> wrote:
> Rashad, > > > Hello all, > > > > We have been working on a new fork of libkml library on github. The > primary > > interest to detach from google/libkml was that various modification in > the > > library are fragmented in the github forks and nothing gets merged. There > > is no activity or interest by original authors and all efforts to contact > > them failed. You can find more details on why it forked here - > > https://github.com/google/libkml/issues/4 . We had clearly explained > this > > also in the readme of the fork. As the library is used in many open > source > > gis tools, we thought it might be worth to unify the efforts in one > place. > > Fix bugs, submit patches, publish new releases and so on. > > It would be great to have a lively libkml indeed, especially since the GDAL > libkml driver depends on a unreleased version of the libkml code. > > Any plan/timeline to produce an "official" release of your fork ? > I had tagged 1.3.0-rc0 on github. https://github.com/libkml/libkml/releases > > > > > Would it be possible to have gdal kml driver to use this version? If so > > what will be the preferred way, submit a patch on trac will be > > sufficient?. > > Does the GDAL libkml driver actually need changes ? Are there been API > changes > ? > No API changes. it make building and configuring libkml easier! Correct me If I am wrong, I guess with a pkg-config would be easier to find and configure libkml libs. > > There are lot of enhancements and bug fixes in the fork. Most > > of them are towards build system. > > > > https://github.com/libkml/libkml > > Even > > -- > Spatialys - Geospatial professional services > http://www.spatialys.com > -- Regards, Rashad
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev