<html><head><style type="text/css">.style1 {font-family: "Times New Roman";}</style></head><body><div dir="ltr"><div>Greg,</div><div><br></div><div>Thank you for your fast response. </div><div><br></div>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.<div><br></div><div>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.</div><div><br></div><div>Q: You didn't publish a link to the scripts you are using.</div><div><br></div><div>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.</div><div><br></div><div>Q: You didn't explain the problems you are having, just that it's hard.</div><div><br></div><div>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.</div><div><br></div><div>Q: I hope you are contributing funds to GDAL! I know that can be hard in a corporate environment....</div><div><br></div><div>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,</div><div><br></div><div>P.S. You mention the following:</div><div><br></div><div>"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."</div><div><br></div><div>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?</div><div><br></div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, Jan 6, 2025 at 6:09 PM Greg Troxel via gdal-dev <<a href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">David Klaus via gdal-dev <<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a>> writes:<br>
<br>
> I am reaching out for advice on streamlining the process my company uses to<br>
> produce new versions of GDAL for our releases. Currently, we maintain a<br>
> batch file that handles some preliminary setup tasks and then initiates a<br>
> custom GDAL build using CMake. Unfortunately, this process has become<br>
> overly complex and challenging to maintain. Developers find it cumbersome<br>
> and even when the process is followed correctly, it often requires<br>
> additional work for each release. <br>
<br>
You didn't explain whether you are doing import/merge and carrying diffs<br>
to the sources, and if so, you didn't give a link where others can look<br>
at them.<br>
<br>
You didn't publish a link to the scripts you are using.<br>
<br>
You didn't explain the problems you are having, just that it's hard.<br>
<br>
I, and probably others, have scripts that basically set up -I/-L/-R for<br>
prereqs and run cmake, to be able to build/install-to-destdir/test<br>
various things. These are often only 100 lines, 2/3 comments, and<br>
don't cause me trouble.<br>
<br>
> This eats up valuable development time and isn't very fun for our<br>
> developers.<br>
<br>
I hope you are contributing funds to GDAL! I know that can be hard in a<br>
corporate environment....<br>
<br>
_______________________________________________<br>
gdal-dev mailing list<br>
<a href="mailto:gdal-dev@lists.osgeo.org" target="_blank">gdal-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/gdal-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/gdal-dev</a><br>
<br>
</blockquote></div><div><br clear="all"></div><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr">David Klaus<div>Carlson Software</div></div></div>
<br><br><p style="font-family: Verdana; font-size:10pt; color:#777777;"><b>Disclaimer</b></p><p style="font-family: Verdana; font-size:8pt; color:#777777;">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.</p></body></html>