[gdal-dev] Improving GDAL production in our release

[David Klaus]

Greg,

Thank you for your fast response.

Q: 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.

A: I apologize if I misunderstand your questions. I think you are asking
whether or not anyone at our company has modified any of the source GDAL
source files or if we are maintaining our own distribution of the source
code. If this is the question, the answer is no.

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

A: Personally, I have no problem with sharing the scripts we currently use.
I will speak with my boss on whether it would be acceptable to share those
here.

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

A: My apologies. The problem is that modifying our current scripts in order
to produce a new build of GDAL takes a significant amount of development
time. For example, I am currently working on building Proj-9.5.1 as part of
our new GDAL build and I'm running into trouble linking "tiff" libraries.
This is not likely irreconcilable but it takes time. I see how this can be
difficult to understand without looking at our current build process. I
will discuss this with my boss.

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

A: Of course I have no problem contributing my corporation's money to GDAL.
Unfortunately, that's why I don't get to make those decisions. However, I
will discuss this with my boss. Hopefully, I can persuade him,

P.S. You mention the following:

"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."

It sounds like your solution for generating up-to-date GDAL builds is
rather streamlined. Currently we are working on updating our current build
to GDAL 3.10.0. Were you to do the same how long would you estimate this
update would take? Also, is there any chance you could share any of your
scripts so I could compare them to ours?



On Mon, Jan 6, 2025 at 6:09 PM Greg Troxel via gdal-dev <
gdal-dev at lists.osgeo.org> wrote:

> 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....
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
>
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
>
>

-- 
David Klaus
Carlson Software

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20250106/2c9cb93e/attachment-0001.htm>