[gdal-dev] Improving GDAL production in our release

[Greg Troxel]

David Klaus via gdal-dev <gdal-dev at lists.osgeo.org> writes:

> I am reaching out for advice on streamlining the process my company uses to
> produce new versions of GDAL for our releases. Currently, we maintain a
> batch file that handles some preliminary setup tasks and then initiates a
> custom GDAL build using CMake. Unfortunately, this process has become
> overly complex and challenging to maintain. Developers find it cumbersome
> and even when the process is followed correctly, it often requires
> additional work for each release. 

You didn't explain whether you are doing import/merge and carrying diffs
to the sources, and if so, you didn't give a link where others can look
at them.

You didn't publish a link to the scripts you are using.

You didn't explain the problems you are having, just that it's hard.

I, and probably others, have scripts that basically set up -I/-L/-R for
prereqs and run cmake, to be able to build/install-to-destdir/test
various things.   These are often only 100 lines, 2/3 comments, and
don't cause me trouble.

> This eats up valuable development time and isn't very fun for our
> developers.

I hope you are contributing funds to GDAL!  I know that can be hard in a
corporate environment....