[gdal-dev] Preventing symbol export in custom GDAL build

[Kai Pastor, DG0YT]

The vcpkg change was merged. The libspatialite and readosm ports no 
longer apply dllexport for static triplets.

Kai

Am 12.12.25 um 14:35 schrieb David Klaus:
> Kai,
>
> Thank you for that information. In regards to your fix for this issue. 
> Are these changes coming to libspatialite in vcpkg in the future?
>
> On Fri, Dec 12, 2025 at 3:03 AM Kai Pastor, DG0YT <dg0yt at darc.de> wrote:
>
>     Thanks for confirming that libcurl is not causing problems here.
>
>     libspatialite does have minor issues.
>     - It always builds with dllexport but never applies dllimport.
>     - The controlling macro is named DLL_EXPORT which is not specific
>     to the package. Reverse dependencies following the same idea will
>     turn on dllexport when they include libspatialite headers.
>
>     I am testing libspatialite modifications now in
>     https://github.com/microsoft/vcpkg/pull/48834. MSVC isn't a local
>     platform for me, and I rarely deal with nmake since GDAL moved to
>     CMake. So vcpkg CI building reverse dependencies is my only
>     indicator of success. External testing welcome.
>
>     Kai
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20251226/9895efcb/attachment.htm>