<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br><div><br><blockquote type="cite"><div>On Nov 10, 2023, at 3:46 PM, Regina Obe <lr@pcorp.us> wrote:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: HelveticaNeue; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">This isn’t an issue with other projects besides PostGIS that use GEOS?<o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">Perhaps related, how much trouble would it be to get PostGIS to use pkgconfig for GEOS. I see that GEOS does ship pkgconfig files.</div></div></div></blockquote><div><br></div><div>We could probably do it on a going-forward basis, but per usual we’d end up with all the old code *plus* the pkgconfig code, so it wouldn’t really “clean up” anything. There are autoconf macros already in configure.ac doing pkgconfig stuff on other deps, so not too too hard of an add.</div><br><blockquote type="cite"><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: HelveticaNeue; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p><span style="font-size: 11pt;">It’s always annoying when I try to do it that I have to explicitly specify the geos-config file in PostGIS when in other cases, we can read the pkg-config and have in fact standardized on that for other dependencies we use.</span></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">I’ve added PostGIS dev to this since well we seem to be talking about PostGIS now.</div></div></blockquote><div><br></div><div>I’m honestly at a bit of a loss as to whether installing with an rpath and expecting linking software to set an appropriate search path is the right thing, or locking in a fixed installation location is the right thing. Certainly the latter results in less nonsense in the postgis build. But it broke proj, which had some tests that expected to be able to manually move an installation post-install.</div><div><br></div><div>P</div><br><blockquote type="cite"><div><div class="WordSection1" style="page: WordSection1; caret-color: rgb(0, 0, 0); font-family: HelveticaNeue; font-size: 13px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p></o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="border-width: medium medium medium 1.5pt; border-style: none none none solid; border-color: currentcolor currentcolor currentcolor blue; border-image: none; padding: 0in 0in 0in 4pt;"><div><div style="border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(225, 225, 225) currentcolor currentcolor; border-image: none; padding: 3pt 0in 0in;"><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><b>From:</b><span class="Apple-converted-space"> </span>Paul Ramsey <<a href="mailto:pramsey@cleverelephant.ca" style="color: blue; text-decoration: underline;">pramsey@cleverelephant.ca</a>><span class="Apple-converted-space"> </span><br><b>Sent:</b><span class="Apple-converted-space"> </span>Friday, November 10, 2023 12:58 PM<br><b>To:</b><span class="Apple-converted-space"> </span>Regina Obe <<a href="mailto:lr@pcorp.us" style="color: blue; text-decoration: underline;">lr@pcorp.us</a>><br><b>Cc:</b><span class="Apple-converted-space"> </span>GEOS Development List <<a href="mailto:geos-devel@lists.osgeo.org" style="color: blue; text-decoration: underline;">geos-devel@lists.osgeo.org</a>><br><b>Subject:</b><span class="Apple-converted-space"> </span>Re: [geos-devel] MacOS DYLD Fix<o:p></o:p></div></div></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">I’m on both sides of the argument now. The best/better practice might be to leave the install behaviour as-is and try to coerce PostGIS into ensuring the LD_RPATH on postgis.so, and other targets is set to the discovered locations of the dylib files in the ./configure.<o:p></o:p></div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div></div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">P.<o:p></o:p></div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><br><br><o:p></o:p></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" type="cite"><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">On Nov 9, 2023, at 6:38 PM, Regina Obe <<a href="mailto:lr@pcorp.us" style="color: blue; text-decoration: underline;">lr@pcorp.us</a>> wrote:<o:p></o:p></div></div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><o:p> </o:p></div><div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">I’ll hold off on releasing until there is consensus on this issue.<o:p></o:p></div></div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></div></div><div style="border-width: medium medium medium 1.5pt; border-style: none none none solid; padding: 0in 0in 0in 4pt; border-color: currentcolor currentcolor currentcolor blue; border-image: none;"><div><div style="border-width: 1pt medium medium; border-style: solid none none; padding: 3pt 0in 0in; border-color: currentcolor; border-image: none;"><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><b>From:</b><span class="apple-converted-space"> </span>geos-devel <<a href="mailto:geos-devel-bounces@lists.osgeo.org" style="color: blue; text-decoration: underline;">geos-devel-bounces@lists.osgeo.org</a>><span class="apple-converted-space"> </span><b>On Behalf Of<span class="apple-converted-space"> </span></b>Paul Ramsey via geos-devel<br><b>Sent:</b><span class="apple-converted-space"> </span>Thursday, November 9, 2023 4:47 PM<br><b>To:</b><span class="apple-converted-space"> </span>GEOS Development List <<a href="mailto:geos-devel@lists.osgeo.org" style="color: blue; text-decoration: underline;">geos-devel@lists.osgeo.org</a>><br><b>Cc:</b><span class="apple-converted-space"> </span>Paul Ramsey <<a href="mailto:pramsey@cleverelephant.ca" style="color: blue; text-decoration: underline;">pramsey@cleverelephant.ca</a>><br><b>Subject:</b><span class="apple-converted-space"> </span>[geos-devel] MacOS DYLD Fix<o:p></o:p></div></div></div></div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></div></div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">From XCode 15, the dyld linker no longer falls back to /usr/local/lib when resolving an @rpath, so installing libraries in /usr/local/lib and hoping that the linker finds them there is no longer workable. They need to be installed with LC_ID_DYLIB set to the install location, which in cmake world means installing them after setting the INSTALL_NAME_DIR property on the target.<o:p></o:p></div></div><div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></div></div></div><div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"><a href="https://github.com/libgeos/geos/commit/8cf761b4d77b1261e0f6673c6716adb2daee7eb1" style="color: blue; text-decoration: underline;">https://github.com/libgeos/geos/commit/8cf761b4d77b1261e0f6673c6716adb2daee7eb1</a><o:p></o:p></div></div></div><div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></div></div></div><div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">I have committed this into main, and would like to pull it back a few stable braches too, since I need it to effectively work on postgis/geos on my Macbook, but I am going to hold off on the stable branches for a while, if anyone working on main finds that this change has broken something in *their* environment, please let me know.<o:p></o:p></div></div></div><div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"> <o:p></o:p></div></div></div><div><div><div style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;">P.</div></div></div></div></div></blockquote></div></div></div></div></div></blockquote></div><br></body></html>