From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Paul Ramsey <pramsey(at)refractions(dot)net> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: PostGIS spatial extensions |
Date: | 2001-08-15 21:46:47 |
Message-ID: | 555.997912007@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Paul Ramsey <pramsey(at)refractions(dot)net> writes:
> However, if I have an RPM-based installation, I *will* have
> the server headers I need. Why do we discriminate against people who
> compile from the tarball?
We don't. We do, however, assume that they read the installation
instructions:
The standard install installs only the header files needed for client application development. If you plan to do any
server-side program development (such as custom functions or datatypes written in C), then you may want to install
the entire PostgreSQL include tree into your target include directory. To do that, enter
gmake install-all-headers
This adds a megabyte or two to the install footprint, and is only useful if you don't plan to keep the whole source tree
around for reference. (If you do, you can just use the source's include directory when building server-side software.)
If Peter's notion of installing server-side headers into a separate
subdirectory pans out, it might be worth thinking about installing all
headers all the time. Right now I'd vote against it, on the grounds
that it adds too much include-file clutter for something that very few
people need.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Joseph Castille | 2001-08-15 21:51:04 | Problems Converting Triggers From Oracle PLSQL to PLPGSQL |
Previous Message | Tom Lane | 2001-08-15 21:23:22 | Re: Re: To be 7.1.3 or not to be 7.1.3? |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-08-15 21:50:16 | Re: Re: Proposal for encrypting pg_shadow passwords |
Previous Message | Bruce Momjian | 2001-08-15 21:46:03 | Re: Fix for fetchone() and fetchmany() in Python interface |