pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andrew Dunstan <andrew@dunslane.net>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: cedric@2ndquadrant.com, pgsql-hackers@postgresql.org, Craig Ringer <craig@2ndquadrant.com>
Subject: Re: Bugfix and new feature for PGXS
Date: Wed, 19 Jun 2013 10:19:37 -0400
Message-ID: <51C1BDF9.5010004@dunslane.net> (raw)
In-Reply-To: <51C1BB02.8050908@gmx.net>
References: <201306181552.36673.cedric@2ndquadrant.com>
	<1371610091.13762.20.camel@vanquo.pezone.net>
	<201306191155.13232.cedric@2ndquadrant.com>
	<51C1BB02.8050908@gmx.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers



view thread (68+ messages)  latest in thread

Message-ID: <51C1BDF9.5010004@dunslane.net>
Permalink:  ../51C1BDF9.5010004@dunslane.net/
Also on:    postgresql.org/message-id/51C1BDF9.5010004@dunslane.net

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: andrew@dunslane.net, peter_e@gmx.net, craig@2ndquadrant.com
  Subject: Re: Bugfix and new feature for PGXS
  In-Reply-To: <51C1BDF9.5010004@dunslane.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox