[gdal-dev] Building only OGR

Kurt Schwehr schwehr at gmail.com
Sun Mar 17 06:55:23 PDT 2019


You can start by disabling drivers.  You can get down to just a couple
raster drivers pretty easily, but you won't be able to remove all of the
raster code.  I did exactly this with a bagel based build.  I got it down
to 21 raster drivers.  I think I am down under 300K active LOC.

On Sun, Mar 17, 2019, 6:42 AM FA <finn at arildsen.com> wrote:

> Hi
>
> Does anyone know if it is possible to build a "small" subset of GDAL?
>
> In my Win32 application need to use the OGR functions to translate between
> coordinate systems.  However, when I take the full package, there are
> clashes between 3rd party libraries imported by GDAL and those I already
> have in my application.
>
> So I wanted to explore the possibility of building a self-contained subset
> of GDAL, only providing OGR functions, and only dependent on a minimal set
> of run-time-libraries.
>
> I suspect that if I try the brute-force method of simply adding files to
> the
> build as needed, I will eventually end up with the full GDAL package.
>
>
>
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/GDAL-Dev-f3742093.html
> _______________________________________________
> gdal-dev mailing list
> 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/20190317/cfdd13a0/attachment.html>


More information about the gdal-dev mailing list