| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Eddie Stanley <eddiewould(at)paradise(dot)net(dot)nz>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>, mux(at)elvis(dot)mu(dot)org |
| Subject: | Re: Frustrating issue with PGXS |
| Date: | 2007-06-25 18:03:06 |
| Message-ID: | 1887.1182794586@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> writes:
>> ifdef USE_PGXS
>> PGXS := $(shell pg_config --pgxs)
>> include $(PGXS)
>>
>> but something like
>>
>> ifdef USE_PGXS
>> PG_CONFIG := pg_config
>> PGXS := $(shell $(PG_CONFIG) --pgxs)
>> include $(PGXS)
> That would break existing Makefiles that use the "please take the first
> pg_config in the path" feature, which rather make sense (it just means
> that you want the extension for your current postgresql).
How would it break them? The default definition is still PG_CONFIG =
pg_config, this just moves where that definition appears.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2007-06-25 18:35:17 | Re: Frustrating issue with PGXS |
| Previous Message | Fabien COELHO | 2007-06-25 17:56:56 | Re: Frustrating issue with PGXS |