Great! :)
It might also clean up something that I've been fighting against for
awhile: when I include files needed for SPI, it drags also a lot of other
garbage in, which conflicts with other things (namely, trying to get a
file to simultaneously include SPI and perl headers is impossible).
I r
I have committed changes implementing the plan I sketched yesterday.
A basic install now installs just the include files needed for
client-side programming; to get all the include files, also say
make install-all-headers
I have verified that the header files installed by default are enoug
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> This is only part of a larger problem, namely that over time it gets more
> likely that some public header file will depend on config.h. For example,
> the libpq++ one's already do. The SSL support in libpq currently requires
> the user to define US
Tom Lane writes:
> where the include files have these roles:
This plan looks good in general. It's the same I've been pondering for a
while. But maybe this should receive more extensive thought than what
would be appropriate to implement now.
> postgres_ext.h: definitions needed in frontend,
On Thu, 8 Feb 2001, Tom Lane wrote:
> Alex Pilosov <[EMAIL PROTECTED]> writes:
> > when I include files needed for SPI, it drags also a lot of other
> > garbage in, which conflicts with other things (namely, trying to get a
> > file to simultaneously include SPI and perl headers is impossible).
Alex Pilosov <[EMAIL PROTECTED]> writes:
> when I include files needed for SPI, it drags also a lot of other
> garbage in, which conflicts with other things (namely, trying to get a
> file to simultaneously include SPI and perl headers is impossible).
> I realise it might be a lot of pain to clea
On Thu, 8 Feb 2001, Alex Pilosov wrote:
> Great! :)
>
> It might also clean up something that I've been fighting against for
> awhile: when I include files needed for SPI, it drags also a lot of other
> garbage in, which conflicts with other things (namely, trying to get a
> file to simultaneous
I have been looking at making a split between client-side and server-side
include files as we discussed earlier this week (pghackers thread
"Include files for SPI are not installed", if you missed it). It turns
out that the major issue here is not just divvying up the files; the
problem is that w
