[postgis-devel] Using pkg-config for PROJ
lr at pcorp.us
Fri Feb 8 15:01:27 PST 2019
The only annoying thing about relying on pkg-config is that since I install things in non-standard paths so I can swap in and out different versions of things, I have to fiddle with the PKG_CONFIG_PATH env variable or insure that all my pkg-config files are in my path variable.
I think I end up doing that anyway for most things since something is always complaining like CUnit tests if I entirely rely on just passing in the paths in my configure call.
> -----Original Message-----
> From: postgis-devel [mailto:postgis-devel-bounces at lists.osgeo.org] On
> Behalf Of Paul Ramsey
> Sent: Friday, February 08, 2019 4:41 PM
> To: PostGIS Development Discussion <postgis-devel at lists.osgeo.org>
> Subject: Re: [postgis-devel] Using pkg-config for PROJ
> 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
> On Fri, Feb 8, 2019 at 12:48 PM Ra l Mar n Rodr guez
> <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
> > _______________________________________________
> > postgis-devel mailing list
> > postgis-devel at lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/postgis-devel
> postgis-devel mailing list
> postgis-devel at lists.osgeo.org
More information about the postgis-devel