>
> This is confuing. Perhaps changing the name of the macro would be
> helpful. I could do this if nobody minds.
>
Feel free to do so
> In this case, since you're providing a SPECIFIC library path at
> configuration, it would seem reasonable to store that information in the
> created GDAL li
On Fri, Nov 2, 2018 at 4:45 PM Even Rouault
wrote:
> On vendredi 2 novembre 2018 16:32:29 CET Andrew Bell wrote:
> > Hi,
> >
> > I'm trying to figure out what might be going on with setting things up
> for
> > proj with GDAL. If I set
> > --with-proj=/directory/to/where/proj/is/installed, I end
On vendredi 2 novembre 2018 16:32:29 CET Andrew Bell wrote:
> Hi,
>
> I'm trying to figure out what might be going on with setting things up for
> proj with GDAL. If I set
> --with-proj=/directory/to/where/proj/is/installed, I end up with
> PROJ_STATIC set to true, even though I have no static pr
Hi,
I'm trying to figure out what might be going on with setting things up for
proj with GDAL. If I set
--with-proj=/directory/to/where/proj/is/installed, I end up with
PROJ_STATIC set to true, even though I have no static proj library built (I
only have libproj.so, no libproj.a in the install di
