Re: Extensions vs PGXS' MODULE_PATHNAME handling

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Extensions vs PGXS' MODULE_PATHNAME handling
Дата
Msg-id 24601.1297547753@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Extensions vs PGXS' MODULE_PATHNAME handling  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Ответы Re: Extensions vs PGXS' MODULE_PATHNAME handling  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
Список pgsql-hackers
Dimitri Fontaine <dimitri@2ndQuadrant.fr> writes:
> Tom Lane <tgl@sss.pgh.pa.us> writes:
>> pgxs.mk will substitute for MODULE_PATHNAME in it is
>> "$libdir/hstore-1.0" ... not exactly what's wanted.  This is because the
>> transformation rule depends on $*, ie the base name of the input file.

> A though that is occurring to me here would be to add a shlib property
> in the control file and have the SQL script use $libdir/$shlib, or even
> $shlib maybe.  That would only work for extensions scripts, and even
> only for those containing a single .so.

Right, the basic difficulty here is exactly that in a Makefile that's
building multiple shlibs, there is no easy way to decide which shlibs go
with which sql scripts.  The existing implementation essentially relies
on the base name of the sql script matching the base name of the shlib.
Adding a single-valued shlib property wouldn't improve matters at all.
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Oleg Bartunov
Дата:
Сообщение: Re: btree_gist (was: CommitFest progress - or lack thereof)
Следующее
От: Magnus Hagander
Дата:
Сообщение: Re: Debian readline/libedit breakage