Even Rouault <even.roua...@spatialys.com> writes: >> But, I'm worried about something different. As a packager, I'd like to >> know that unless I take the affirmative step of passing --enable-foo, >> for any GPLish or proprietary foo, I won't end up with a gdal build >> linked with foo just because it happened to be present in my build >> environment. > > This should normally be the case. One of the few GPL dependencies is > Poppler and must be explicitly enabled with --with-poppler . Similarly > with MySQL. All proprietary dependencies need also to be explicitly > enabled AFAIK (you actually need to point to their SDK).
Thanks. I'll report if I find any otherwise. > GEOS (LGPL) is enabled by default is found. That seems entirely reasonable to me.
signature.asc
Description: PGP signature
_______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/gdal-dev
