Re: [HACKERS] SPI Headers -- RPM distribution

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>
Cc: pgsql-hackers(at)postgreSQL(dot)org, pgsql-ports(at)postgreSQL(dot)org
Subject: Re: [HACKERS] SPI Headers -- RPM distribution
Date: 1999-12-21 05:07:07
Message-ID: 6450.945752827@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-ports

Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
> So, I'm going to put these headers under /usr/include/pgsql/backend.

Some of these headers already are exported. The right thing is to
export the rest in parallel, not throw in an extra level of directory.
The path from /usr/include/pgsql should be the same as the path from
.../src/include in the source tree.

The only real problem with doing that is with fmgr.h, which for reasons
that I don't fathom isn't in src/include at all. Seems to me it would
be a good idea to have fmgr.h (and I guess parse.h too) put into
src/include, and then we could get rid of -I../backend from the switches
used for backend compilations.

A good longer-term project would be to reduce the number of headers that
we need to export. 80 include files to compile spi.h? Ugh.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-12-21 05:48:25 Re: [HACKERS] T-O-A-S-T meaning
Previous Message Tom Lane 1999-12-21 04:57:34 Re: [HACKERS] LONG vs. Toaster

Browse pgsql-ports by date

  From Date Subject
Next Message Kardos, Dr. Andreas 1999-12-21 07:37:21 Re: [PORTS] QNX4 port
Previous Message usayhello 1999-12-21 02:42:40 Save 50-80% on International Calls and Win $500 in Free phone calls!!!