[gdal-dev] Building GDAL from VCPKG fails with FreeXL

[mchapman at hyperacktive.com]

Thanks for the information Kai.  I will look into it next week after the holiday weekend.  It must be something on my system.  Sorry to bother you with it but thank you so much for all your feedback.  I really love using GDAL and all the great work you people have done throughout the years!

 

Best regards,

Martin Chapman

 

From: Kai Pastor, DG0YT <dg0yt at darc.de> 
Sent: Tuesday, July 1, 2025 1:43 PM
To: mchapman at hyperacktive.com; 'Even Rouault' <even.rouault at spatialys.com>; gdal-dev at lists.osgeo.org
Subject: Re: [gdal-dev] Building GDAL from VCPKG fails with FreeXL

 

- The freexl port builds in vcpkg CI, and there are no open issues for Windows.

- Either there are log files for the actual error, reported on the console, or it fails early for example because of mixing different msys2/cygwin runtimes.

- freexl is an optional feature of port gdal. If nothing asks for it, it is not enabled in port gdal.

- However, libspatialite is a default feature of port gdal, and freexl is a default feature of port libspatialite. ATM it is not possible to opt-out from libspatialite[freexl], but this will be fixed with port gdal 3.11.1.

- To opt-out from all default features of a port, you must declare this in the top-level manifest (manifest mode) or by using the pseudo feaure "core" (classic mode).  The reason why you can't do this now with libspatialite[core] is that gdal[libspatialite] implicitly depends on the default features of port libspatialite.

 

Kai Pastor

 

Am 29.06.25 um 19:11 schrieb Martin Chapman via gdal-dev:

Even,

 

I didn’t save the exact message but it was fairly non descriptive.  It was something like BUILD_FAILED.  Sorry, my bad for not saving the exact message.  It sounds like it may have just been my environment and if it’s not critical then I can live without it.  If no one else is complaining then I wouldn’t waste time looking into it.  If I have time later I will try to rebuild and reproduce the error, it just takes an hour to build so can’t do it right now.  Thanks for your help though!

  

Best regards,

Martin Chapman

 

From: Even Rouault  <mailto:even.rouault at spatialys.com> <even.rouault at spatialys.com> 
Sent: Sunday, June 29, 2025 3:33 AM
To: mchapman at hyperacktive.com <mailto:mchapman at hyperacktive.com> ; gdal-dev at lists.osgeo.org <mailto:gdal-dev at lists.osgeo.org> 
Subject: Re: [gdal-dev] Building GDAL from VCPKG fails with FreeXL

 

Martin,

what error messages did you get when trying with FreeXL ?

Removing the FreeXL dependency removes support for the old prior-to-Excel-2007 binary XLS format. So usually not a big deal

Even

Le 29/06/2025 à 02:45, Martin Chapman via gdal-dev a écrit :

All,

 

I tried to build GDAL 3.11.0 from https://vcpkg.io/en/package/gdal and FreeXL kept failing on my Windows 11 box using Microsoft Visual Studio Professional 2022 (64-bit) – Current Version 17.14.7.  To resolve the issue I built a custom-overlay port and removed FreeXL from the build and then everything built great.  I tried to just build FreeXL using VCPKG and that failed so I was wondering if it’s just my machine that is messed up or are others having issues as well?  By removing FreeXL will I be crippling any other drivers that may depend on it?  I looked at the docs and it didn’t seem that important?  Also, is there a way to specify what drivers not to build without doing a custom-overlay port?

 

Best regards,

Martin Chapman

 

 

_______________________________________________
gdal-dev mailing list
gdal-dev at lists.osgeo.org <mailto:gdal-dev at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/gdal-dev

-- 
http://www.spatialys.com
My software is free, but my time generally not.





_______________________________________________
gdal-dev mailing list
gdal-dev at lists.osgeo.org <mailto:gdal-dev at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/gdal-dev

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20250701/66d3edec/attachment.htm>