<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<STYLE>BODY {
FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial
}
</STYLE>
<META name=GENERATOR content="MSHTML 10.00.9200.17028"></HEAD>
<BODY
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space">
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT size=4>+1 (go
ahead and add new options and remove the old syntax). I should note: both
debbie and winnie I suspect will yell when you do this. So you might want to
change their scripts as well:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT
size=4></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT size=4><A
href="http://trac.osgeo.org/postgis/browser/buildbots/debian/scripts">http://trac.osgeo.org/postgis/browser/buildbots/debian/scripts</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT
size=4></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT size=4><A
href="http://trac.osgeo.org/postgis/browser/buildbots/windows/mingw64/scripts">http://trac.osgeo.org/postgis/browser/buildbots/windows/mingw64/scripts</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT
size=4></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT size=4>(I of course
will help out if you run into problems).</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT
size=4></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT size=4>Given that
I'm the one that is going to suffer most by this change, it is odd that I would
say don't bother keeping the old syntax.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT
size=4></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT size=4>I think too
many ways of doing the same thing will just make things difficult to debug in
the long run. So I'll go for more pain now with less trouble debugging
later.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT
size=4></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT
size=4>Thanks,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT
size=4>R</FONT></SPAN><SPAN class=663354303-02082014><FONT
size=4></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=663354303-02082014><FONT
size=4></FONT></SPAN> </DIV><BR>
<DIV lang=en-us class=OutlookMessageHeader dir=ltr align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> postgis-devel-bounces@lists.osgeo.org
[mailto:postgis-devel-bounces@lists.osgeo.org] <B>On Behalf Of </B>Paul
Ramsey<BR><B>Sent:</B> Friday, August 01, 2014 5:29 PM<BR><B>To:</B> PostGIS
Development Discussion<BR><B>Subject:</B> [postgis-devel]
--with-libfoo<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">Hey
devs,</DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">I
had to do a build for Solaris recently, and ended up having to patch
configure.ac to do it, because of the way we reference external libraries.</DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">Basically,
we assume that any external library will be installed in /some/prefix/lib and
/some/prefix/include. So we only expect to need /some/prefix in our
configuration in order to find the necessary parts.</DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">In
solaris 64 bit, the includes are are in /some/prefix/include but the libraries
are in /home/prefix/lib/64.</DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">I
noted that cmake has this general idea baked into their patterns for extension
libraries, the expectation that include and lib paths be declared
independently.</DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">In
the end, I changed</DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">—with-projdir </DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">to </DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">—with-proj-includedir</DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">and</DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">—with-proj-libdir</DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px"><BR></DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">I’d
like to do a similar thing to trunk. I could try and keep the old syntax around,
or just remove it in favor of the split syntax.</DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px"><BR></DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">Thoughts?</DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px"><BR></DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px">P</DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px"><BR></DIV>
<DIV id=bloop_customfont
style="FONT-SIZE: 13px; FONT-FAMILY: Helvetica,Arial; COLOR: ; MARGIN: 0px"><BR></DIV><BR>
<DIV id=bloop_sign_1406928296045690112 class=bloop_sign>
<DIV><BR></DIV>-- <BR><B>Paul Ramsey</B>
<DIV>VP Product Management | <A
href="http://boundlessgeo.com">Boundless</A>
<DIV>pramsey@boundlessgeo.com </DIV>
<DIV>250-885-0632 </DIV>
<DIV>@boundlessgeo </DIV>
<DIV><IMG
src="http://boundlessgeo.com/wp-content/uploads/files/boundless_sig.png"
NOSEND="1"></DIV></DIV></DIV></BODY></HTML>