On Tue, 20 Jan 2009, Howard Butler wrote:
I think the way forward is if you could document this misery on the wiki http://trac.osgeo.org/gdal It's a hard sell for us to complicate our already messy configure logic to work around their bug that they stubbornly won't fix.
It looks like someone (possibly you) already has part of the fix there, which is changing the order of the linking.
The most recent issue is similar as it relates to the order of the include path. I suspect it wouldn't harm anyone to have the internal gdal .h files included before any third party includes. That way the logic that switches to the internal zlib will always work, regardless of any other zlib related .h files which may be installed in other include directories.
My guess is the current include path order will cause other people problems who have multiple versions of zlib .h files, even those who aren't dealing with the libsde bug.
I will take your advise and add some documentation. In my case this is all stuff my customer wants to work, but that they may not want me spending their time to document it for others. Will verify, but will be willing to document off-hours otherwise.
I'm told I should have the 9.3 SDE SDK soon, so will be able to report on that.
-- Russell McOrmond, Internet Consultant: <http://www.flora.ca/> Please help us tell the Canadian Parliament to protect our property rights as owners of Information Technology. Sign the petition! http://digital-copyright.ca/petition/ict/ http://KillBillC61.ca "The government, lobbied by legacy copyright holders and hardware manufacturers, can pry control over my camcorder, computer, home theatre, or portable media player from my cold dead hands!" _______________________________________________ gdal-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/gdal-dev
