Re: pgxs: build infrastructure for extensions v4

From: Joe Conway <mail(at)joeconway(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgxs: build infrastructure for extensions v4
Date: 2004-08-06 05:14:47
Message-ID: 411313C7.10102@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>
>>FYI, I couldn't find anything in the shell pg_config with this path:
>> strncat(otherpath, "/pgxs/src/makefiles/pgxs.mk", MAXPGPATH-1);
>>Did you find a mention of this? I looked in pg_config.sh and
>>Makefile.global.in.
>
>
> The original coding concatenated "src/makefiles/pgxs.mk" to a path value
> derived elsewhere (pgxsdir). I was planning to bug Peter about just how
> correct this patch is --- it's essentially hardwiring an assumption
> about the construction of pgxsdir.
>

I just added "src/makefiles/pgxs.mk" to the already hardwired path to
pgxs in pg_config.c. But in any case, it looks like pgxsdir is set in
src/Makefile.global.in like like this:
pgxsdir = $(pkglibdir)/pgxs
So it is sort of hardwired already at the moment at least.

Joe

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan M. Gardner 2004-08-06 05:27:06 PostgreSQL as an application server
Previous Message fastpgs 2004-08-06 05:14:13 Proposal for Disable Triggers