Re: [HACKERS] SPI Headers -- RPM distribution - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] SPI Headers -- RPM distribution
Date
Msg-id 6450.945752827@sss.pgh.pa.us
Whole thread Raw
In response to SPI Headers -- RPM distribution  (Lamar Owen <lamar.owen@wgcr.org>)
List pgsql-hackers
Lamar Owen <lamar.owen@wgcr.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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] LONG vs. Toaster
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Tuple toaster (was: Re: LONG varsize - how to go on)