ee85595d46
> > The patch adds missing the "libpgport.a" file to the installation under > "install-all-headers". It is needed by some contribs. I install the > library in "pkglibdir", but I was wondering whether it should be "libdir"? > I was wondering also whether it would make sense to have a "libpgport.so"? > > It fixes various macros which are used by contrib makefiles, especially > libpq_*dir and LDFLAGS when used under PGXS. It seems to me that they are > needed to > > It adds the ability to test and use PGXS with contribs, with "make > USE_PGXS=1". Without the macro, this is exactly as before, there should be > no difference, esp. wrt the vpath feature that seemed broken by previous > submission. So it should not harm anybody, and it is useful at least to me. > > It fixes some inconsistencies in various contrib makefiles > (useless override, ":=" instead of "="). Fabien COELHO |
||
|---|---|---|
| .. | ||
| Makefile | ||
| README.string_io | ||
| string_io.c | ||
| string_io.h | ||
| string_io.sql.in | ||
README.string_io
String io module for postgresql. Copyright (C) 1999, Massimo Dal Zotto <dz@cs.unitn.it> This software is distributed under the GNU General Public License either version 2, or (at your option) any later version. These output functions can be used as substitution of the standard text output functions to get the value of text fields printed in the format used for C strings. This allows the output of queries or the exported files to be processed more easily using standard unix filter programs like perl or awk. If you use the standard functions instead you could find a single tuple splitted into many lines and the tabs embedded in the values could be confused with those used as field delimters. My function translates all non-printing characters into corresponding esacape sequences as defined by the C syntax. All you need to reconstruct the exact value in your application is a corresponding unescape function like the string_input defined in the source code. Massimo Dal Zotto <dz@cs.unitn.it>