Tom Lane wrote:
> client-devel and server-devel are the right division IMHO. SPI is a
> subset of server-side development, but not all server-side code needs
> SPI. Consider user-written functions and datatypes. These guys do not
Ok, I can do that. Obsoletes:devel here we come!
> My thought
Lamar Owen <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> What would make more sense is for the standard install to install only
>> those headers needed for *client side* programming, and then to have
>> an optional install target that installs the whole darn src/include
>> tree.
> I can go for
> I agree with Karel on this --- it's difficult to visualize doing useful
> SPI work without a source tree at hand, and it also seems unlikely that
> SPI authors would get along for long with *only* those header files
> needed to pull in spi.h. So I think it's pretty pointless to add just
> those
Tom Lane wrote:
> I agree with Karel on this --- it's difficult to visualize doing useful
> SPI work without a source tree at hand, and it also seems unlikely that
> SPI authors would get along for long with *only* those header files
> needed to pull in spi.h. So I think it's pretty pointless to
Lamar Owen <[EMAIL PROTECTED]> writes:
> Karel Zak wrote:
>> I expect header files on /usr/include/pgsql for client programming not
>> for SPI.
> Why? I know of several people doing SPI work with no source tree
> installed.
I agree with Karel on this --- it's difficult to visualize doing usefu
On Tue, 6 Feb 2001, Lamar Owen wrote:
> Karel Zak wrote:
> > On Tue, 6 Feb 2001, Oliver Elphick wrote:
> > > Certain include files are installed by src/include/Makefile and by
> > > interfaces/libpq++/Makefile. However, they in turn include others that
> > > are not installed, thus obviating th
Karel Zak wrote:
> On Tue, 6 Feb 2001, Oliver Elphick wrote:
> > Certain include files are installed by src/include/Makefile and by
> > interfaces/libpq++/Makefile. However, they in turn include others that
> > are not installed, thus obviating the usefulness of the ones that are.
> In your mo
Oliver Elphick wrote:
> Certain include files are installed by src/include/Makefile and by
> interfaces/libpq++/Makefile. However, they in turn include others that
> are not installed, thus obviating the usefulness of the ones that are.
> The missing files are these:
[snip]
> The list can be r
On Tue, 6 Feb 2001, Oliver Elphick wrote:
> Certain include files are installed by src/include/Makefile and by
> interfaces/libpq++/Makefile. However, they in turn include others that
> are not installed, thus obviating the usefulness of the ones that are.
In your module you can use arbitrary
Certain include files are installed by src/include/Makefile and by
interfaces/libpq++/Makefile. However, they in turn include others that
are not installed, thus obviating the usefulness of the ones that are.
The missing files are these:
access/heapam.h
access/htup.h
access/relscan.h
access/rmg
10 matches
Mail list logo
