Hi Jeff, I don't feel I know enough about the process to start to update that page, as there is quite a lot of work to do!
In the end the recipe at https://github.com/osgeo-forge/libgdal-filegdb-feedstock worked for me, with a couple of minor tweaks to remove some warnings from the log. Updating it to v3.2.0 was also straightforward, only the version and md5 need to be updated. Once this is built, the libgdal-filegdb package can be installed to an environment containing conda-forge GDAL and you now have full FileGDB write support. Thanks, Jon -----Original Message----- From: gdal-dev <[email protected]> On Behalf Of Jeff McKenna Sent: 16 November 2020 12:54 To: [email protected] Subject: Re: [gdal-dev] GDAL conda build On 2020-11-11 9:00 a.m., Jon Morris wrote: > Hi Paul, > > Thanks for your reply. The only reason we're trying to build locally > is to add FileGDB support - if there is a better way to add FileGDB > write support to conda-forge GDAL, I'd love to hear it! The GDAL docs > are very out of date when it comes to building on Windows - the "GDAL > Windows Building example for Plugins" links to > https://trac.osgeo.org/gdal/wiki/BuildingOnWindows > <https://trac.osgeo.org/gdal/wiki/BuildingOnWindows>. > Hi Jon, For 10+ years we maintained the FileGDB build steps for Windows etc at https://trac.osgeo.org/gdal/wiki/FileGDB In general, as a person compiling GDAL, you should bookmark the priceless "BuildHints" wiki page, see the "External Library" section where various driver compile howtos are listed, at https://trac.osgeo.org/gdal/wiki/BuildHints (you can see how for users compiling drivers that a wiki is a lifeline, recording build steps that may be 5 years old and 'stale', yet containing valuable information to the user) Please consider recording your steps as well, for other users, as you travel down this path. Thanks! -jeff -- Jeff McKenna MapServer Consulting and Training Services co-founder of FOSS4G http://gatewaygeo.com/ _______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev [JBA COVID-19 statement]<https://www.jbagroup.co.uk/sites/www.jbagroup.co.uk/files/documents/15-030%20JBA%20Business%20Continuity%20Briefing%20-%20Latest.pdf> T +44 (0) 1756 799919 www.jbarisk.com<http://www.jbarisk.com> [Visit our website]<http://www.jbarisk.com> [http://www.jbagroup.co.uk/imgstore/JBA-Email-Sig-Icons-LINKEDIN.png] <https://www.linkedin.com/in/jon-morris-a2897b4/> [Follow us on Twitter] <https://twitter.com/jbarisk> Find out more about us here: www.jbarisk.com<http://www.jbarisk.com/> and follow us on Twitter @JBARisk<http://twitter.com/JBARisk> and LinkedIn<https://www.linkedin.com/company/2370847?trk=tyah&trkInfo=clickedVertical%3Acompany%2CclickedEntityId%3A2370847%2Cidx%3A2-1-2%2CtarId%3A1447414259786%2Ctas%3AJBA%20RISK%20MANAGEMENT> The JBA Group supports the JBA Trust. All JBA Risk Management's email messages contain confidential information and are intended only for the individual(s) named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. JBA Risk Management Limited is registered in England, company number 07732946, 1 Broughton Park, Old Lane North, Broughton, Skipton, North Yorkshire, BD23 3FD, Telephone: +441756799919 _______________________________________________ gdal-dev mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/gdal-dev
