[postgis-devel] Using pkg-config for PROJ

[Regina Obe]

I thought we already required it for building MVT no?

I'm fine with having pkg-config dependency. I'm pretty sure I'm already using it for building shp2pgsql-gui and MVT for the windows packages.

Since the only windows compilation supported for Windows is under MingW/mingW-w64 as far as windows, goes, I don't think you need to worry about MS VS which I don't think supports pkg-config.

 

I don't think anyone has really picked up the ball on CMake.  Not sure what CMake does (is pkg-config an autoconf only thing?)

 

Thanks,

Regina

 

 

 

From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On Behalf Of Raúl Marín Rodríguez
Sent: Friday, February 08, 2019 5:20 PM
To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
Subject: Re: [postgis-devel] Using pkg-config for PROJ

 

> but I'm not convinced my

from-source builds will be detectable.

 

Mine are. Also Docker is building several dependencies from source and it doesn't seem to have issues. OTOH, Postgis' defaults are pretty much?tailored just for Linux.

 

There is an easy way to check:

pkg-config --libs proj (or whatever other project)

pkg-config --cflags proj

 

With pkg-config there is a way to pass the flags (env variables PROJ_CFLAGS and PROJ_LDFLAGS) and in that case the default will be ignored. This is both why I don't get why Postgis has its own way to do it and why, if we want to keep having manual as default, it's not worth it to force pkg-config being mandatory ( and simply check pkg-config if it's installed).

 


On Friday, February 8, 2019, Paul Ramsey <pramsey at cleverelephant.ca <mailto:pramsey at cleverelephant.ca> > wrote:

Completely requiring pkg-config is not something I'm super
enthusiastic about. I'm sure many of my packaged dependencies have
pkg-config entries under MacPorts, but I'm not convinced my
from-source builds will be detectable.

P

On Fri, Feb 8, 2019 at 12:48 PM Raúl Marín Rodríguez
<rmrodriguez at carto.com <mailto:rmrodriguez at carto.com> > wrote:
>
> Hi,
>
> I started doing it in https://github.com/postgis/postgis/pull/372.
> Then I noticed that `json-c` had the same option (and we weren't
> including its files correctly) and, after that, that the same happens
> with `libpcre` and `cunit`.
>
> Wouldn't it make more sense to drop those 4 options (`--with-projdir`,
> `--with-jsondir`, etc) and make pkg-config mandatory instead? My only
> concern is Windows, which I don't really know if it can use it.
>
> --
> Raúl Marín Rodríguez
> carto.com <http://carto.com> 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
> https://lists.osgeo.org/mailman/listinfo/postgis-devel
_______________________________________________
postgis-devel mailing list
postgis-devel at lists.osgeo.org <mailto:postgis-devel at lists.osgeo.org> 
https://lists.osgeo.org/mailman/listinfo/postgis-devel



-- 

Raúl Marín Rodríguez 
 <http://carto.com/> carto.com

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20190208/a8a36394/attachment.html>