From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | cedric(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org, Craig Ringer <craig(at)2ndquadrant(dot)com> |
Subject: | Re: Bugfix and new feature for PGXS |
Date: | 2013-06-19 14:19:37 |
Message-ID: | 51C1BDF9.5010004@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 06/19/2013 10:06 AM, Peter Eisentraut wrote:
> On 6/19/13 5:55 AM, Cédric Villemain wrote:
>> Le mercredi 19 juin 2013 04:48:11, Peter Eisentraut a écrit :
>>> On Tue, 2013-06-18 at 15:52 +0200, Cédric Villemain wrote:
>>>> This allows for example to install hstore header and be able to
>>>> include them
>>>>
>>>> in another extension like that:
>>>> # include "contrib/hstore/hstore.h"
>>> That's not going to work. hstore's header file is included as #include
>>> "hstore.h" (cf. hstore source code). Having it included under different
>>> paths in different contexts will be a mess.
>> OK.
>> At the beginning I though of putting headers in include/contrib but feared
>> that some header may have the same name.
>> If you think that it is suitable, I can do that ? (and include the clean:
>> recipe that I missed on the first shot)
> I don't think there is any value in moving the contrib header files around.
>
>
>
What are they going to be used for anyway? I rubbed up against this not
too long ago. Things will blow up if you use stuff from the module and
the module isn't already loaded.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2013-06-19 14:22:01 | Re: how to find out whether a view is updatable |
Previous Message | Peter Eisentraut | 2013-06-19 14:06:58 | Re: Bugfix and new feature for PGXS |