[gdal-dev] RE: GDAL trunk compilation broken by r19335 / minizip / libkml

2010-04-07 Thread Harsh Govind
My first commit and build failure. :( Sorry team. I have reverted my changes to GDALmake.opt.in so the build should be fixed. Is there a way to sign up for these build results so as to get an email if your commit breaks the build? I am going to setup an automated build system on windows to cont.

[gdal-dev] Re: GDAL trunk compilation broken by r19335 / minizip / libkml

2010-04-07 Thread Even Rouault
No problem. That happens quite regularly when adding substantial contributions like new drivers that require changes in the build system on the various targets. To check if things go well, you can look at the waterfall http://buildbot.osgeo.org:8500/waterfall which has different slavebots (Linux

[gdal-dev] Re: GDAL trunk compilation broken by r19335 / minizip / libkml

2010-04-08 Thread Francesco P. Lovergine
On Wed, Apr 07, 2010 at 09:36:31PM +0200, Even Rouault wrote: > For the long term solution, I'm not sure what the best option is. In the > past, > I had 'imported' the unzip part of minizip in GDAL port subdirectory to add > support for a /vsizip virtual file system. To avoid issues for applicat