head	1.30;
access;
symbols
	REL9_0_0:1.30
	REL9_1_ALPHA1:1.30
	REL9_0_RC1:1.30
	REL9_0_BETA4:1.30
	REL9_0_STABLE:1.30.0.2
	REL9_0_BETA3:1.30
	REL9_0_BETA2:1.29
	REL7_4_29:1.16
	REL8_0_25:1.19
	REL8_1_21:1.23
	REL8_2_17:1.25
	REL8_3_11:1.27
	REL8_4_4:1.28
	REL9_0_BETA1:1.29
	REL9_0_ALPHA5_BRANCH:1.28.0.12
	REL9_0_ALPHA5:1.28
	REL7_4_28:1.16
	REL8_0_24:1.19
	REL8_1_20:1.23
	REL8_2_16:1.25
	REL8_3_10:1.27
	REL8_4_3:1.28
	REL9_0_ALPHA4:1.28
	REL9_0_ALPHA4_BRANCH:1.28.0.10
	REL8_5_ALPHA3:1.28
	REL8_5_ALPHA3_BRANCH:1.28.0.8
	REL7_4_27:1.16
	REL8_0_23:1.19
	REL8_1_19:1.23
	REL8_2_15:1.25
	REL8_3_9:1.27
	REL8_4_2:1.28
	REL8_5_ALPHA2:1.28
	REL8_5_ALPHA2_BRANCH:1.28.0.6
	REL7_4_26:1.16
	REL8_0_22:1.19
	REL8_1_18:1.23
	REL8_2_14:1.25
	REL8_3_8:1.27
	REL8_4_1:1.28
	REL8_5_ALPHA1:1.28
	REL8_5_ALPHA1_BRANCH:1.28.0.4
	REL8_4_STABLE:1.28.0.2
	REL8_4_0:1.28
	REL8_4_RC2:1.28
	REL8_4_RC1:1.28
	REL8_4_BETA2:1.28
	REL8_4_BETA1:1.28
	REL7_4_25:1.16
	REL8_0_21:1.19
	REL8_1_17:1.23
	REL8_2_13:1.25
	REL8_3_7:1.27
	REL7_4_24:1.16
	REL8_0_20:1.19
	REL8_1_16:1.23
	REL8_2_12:1.25
	REL8_3_6:1.27
	REL7_4_23:1.16
	REL8_0_19:1.19
	REL8_1_15:1.23
	REL8_2_11:1.25
	REL8_3_5:1.27
	REL7_4_22:1.16
	REL8_0_18:1.19
	REL8_1_14:1.23
	REL8_2_10:1.25
	REL8_3_4:1.27
	REL7_4_21:1.16
	REL8_0_17:1.19
	REL8_1_13:1.23
	REL8_2_9:1.25
	REL8_3_3:1.27
	REL7_4_20:1.16
	REL8_0_16:1.19
	REL8_1_12:1.23
	REL8_2_8:1.25
	REL8_3_2:1.27
	REL8_2_7:1.25
	REL8_3_1:1.27
	REL8_3_STABLE:1.27.0.2
	REL8_3_0:1.27
	REL8_3_RC2:1.27
	REL7_3_21:1.11
	REL7_4_19:1.16
	REL8_0_15:1.19
	REL8_1_11:1.23
	REL8_2_6:1.25
	REL8_3_RC1:1.27
	REL8_3_BETA4:1.27
	REL8_3_BETA3:1.27
	REL8_3_BETA2:1.27
	REL8_3_BETA1:1.27
	REL7_3_20:1.11
	REL7_4_18:1.16
	REL8_0_14:1.19
	REL8_1_10:1.23
	REL8_2_5:1.25
	REL7_3_19:1.11
	REL7_4_17:1.16
	REL8_0_13:1.19
	REL8_1_9:1.23
	REL8_2_4:1.25
	REL8_0_12:1.19
	REL8_1_8:1.23
	REL8_2_3:1.25
	REL7_3_18:1.11
	REL7_4_16:1.16
	REL8_0_11:1.19
	REL8_1_7:1.23
	REL8_2_2:1.25
	REL8_0_10:1.19
	REL8_1_6:1.23
	REL8_2_1:1.25
	REL7_4_15:1.16
	REL7_3_17:1.11
	REL8_2_STABLE:1.25.0.2
	REL8_2_0:1.25
	REL8_2_RC1:1.25
	REL8_2_BETA3:1.25
	REL8_2_BETA2:1.25
	REL8_1_5:1.23
	REL8_0_9:1.19
	REL7_4_14:1.16
	REL7_3_16:1.11
	REL8_2_BETA1:1.24
	REL7_3_15:1.11
	REL7_4_13:1.16
	REL8_0_8:1.19
	REL8_1_4:1.23
	REL7_3_14:1.11
	REL7_4_12:1.16
	REL8_0_7:1.19
	REL8_1_3:1.23
	REL7_3_13:1.11
	REL7_4_11:1.16
	REL8_0_6:1.19
	REL8_1_2:1.23
	REL7_3_12:1.11
	REL7_4_10:1.16
	REL8_0_5:1.19
	REL8_1_1:1.23
	REL8_1_STABLE:1.23.0.2
	REL8_1_0:1.23
	REL8_1_0RC1:1.22
	REL8_1_0BETA4:1.22
	REL8_1_0BETA3:1.22
	REL7_3_11:1.11
	REL7_4_9:1.16
	REL8_0_4:1.19
	REL8_1_0BETA2:1.21
	REL8_1_0BETA1:1.21
	REL7_2_8:1.9
	REL7_3_10:1.11
	REL7_4_8:1.16
	REL8_0_3:1.19
	REL8_0_2:1.19
	REL7_2_7:1.9
	REL7_3_9:1.11
	REL7_4_7:1.16
	REL8_0_1:1.19
	REL8_0_STABLE:1.19.0.4
	REL8_0_0:1.19.0.2
	REL8_0_0RC5:1.19
	REL8_0_0RC4:1.19
	REL8_0_0RC3:1.18
	REL8_0_0RC2:1.18
	REL8_0_0RC1:1.18
	REL8_0_0BETA5:1.18
	REL8_0_0BETA4:1.18
	REL7_4_6:1.16
	REL7_3_8:1.11
	REL7_2_6:1.9
	REL8_0_0BETA3:1.18
	REL8_0_0BETA2:1.18
	REL7_2_5:1.9
	REL7_4_5:1.16
	REL7_3_7:1.11
	REL7_4_4:1.16
	REL8_0_0BETA1:1.18
	REL7_4_3:1.16
	REL7_4_2:1.16
	REL7_3_6:1.11
	REL7_4_1:1.16
	REL7_3_5:1.11
	REL7_4:1.16
	REL7_4_RC2:1.16
	REL7_4_STABLE:1.16.0.2
	REL7_4_RC1:1.16
	REL7_4_BETA5:1.16
	REL7_4_BETA4:1.16
	REL7_4_BETA3:1.16
	REL7_4_BETA2:1.15
	WIN32_DEV:1.15.0.2
	REL7_4_BETA1:1.15
	REL7_3_4:1.11
	REL7_3_2:1.11
	REL7_2_4:1.9
	REL7_3_STABLE:1.11.0.2
	REL7_2_3:1.9
	REL7_2_STABLE:1.9.0.2
	REL7_2:1.9
	REL7_2_RC2:1.9
	REL7_2_RC1:1.9
	REL7_2_BETA5:1.8
	REL7_2_BETA4:1.8
	REL7_2_BETA3:1.8
	REL7_2_BETA2:1.8
	REL7_2_BETA1:1.8
	REL7_1_2:1.5
	REL7_1_STABLE:1.5.0.2
	REL7_1_BETA:1.4
	REL7_1_BETA3:1.4
	REL7_1_BETA2:1.4
	REL7_1:1.5;
locks; strict;
comment	@# @;


1.30
date	2010.07.05.18.54.37;	author tgl;	state Exp;
branches;
next	1.29;

1.29
date	2010.04.03.07.23.01;	author petere;	state Exp;
branches;
next	1.28;

1.28
date	2008.02.18.14.51.48;	author petere;	state Exp;
branches;
next	1.27;

1.27
date	2007.02.20.15.01.17;	author momjian;	state Exp;
branches;
next	1.26;

1.26
date	2007.01.31.23.26.04;	author momjian;	state Exp;
branches;
next	1.25;

1.25
date	2006.10.23.18.10.32;	author petere;	state Exp;
branches;
next	1.24;

1.24
date	2006.09.16.00.30.19;	author momjian;	state Exp;
branches;
next	1.23;

1.23
date	2005.11.01.21.09.50;	author tgl;	state Exp;
branches;
next	1.22;

1.22
date	2005.09.27.17.39.32;	author tgl;	state Exp;
branches;
next	1.21;

1.21
date	2005.08.09.22.47.03;	author tgl;	state Exp;
branches;
next	1.20;

1.20
date	2005.06.09.18.15.05;	author petere;	state Exp;
branches;
next	1.19;

1.19
date	2005.01.04.03.58.16;	author tgl;	state Exp;
branches;
next	1.18;

1.18
date	2004.08.02.12.34.14;	author momjian;	state Exp;
branches;
next	1.17;

1.17
date	2003.11.29.19.51.39;	author pgsql;	state Exp;
branches;
next	1.16;

1.16
date	2003.08.31.17.32.23;	author petere;	state Exp;
branches;
next	1.15;

1.15
date	2003.03.25.16.15.42;	author petere;	state Exp;
branches
	1.15.2.1;
next	1.14;

1.14
date	2003.03.24.14.32.51;	author petere;	state Exp;
branches;
next	1.13;

1.13
date	2003.01.19.00.13.29;	author momjian;	state Exp;
branches;
next	1.12;

1.12
date	2002.11.15.03.11.18;	author momjian;	state Exp;
branches;
next	1.11;

1.11
date	2002.10.11.23.03.48;	author petere;	state Exp;
branches;
next	1.10;

1.10
date	2002.04.21.19.02.39;	author thomas;	state Exp;
branches;
next	1.9;

1.9
date	2002.01.20.22.19.57;	author petere;	state Exp;
branches;
next	1.8;

1.8
date	2001.09.16.16.11.09;	author petere;	state Exp;
branches;
next	1.7;

1.7
date	2001.09.03.12.57.50;	author petere;	state Exp;
branches;
next	1.6;

1.6
date	2001.08.28.14.20.26;	author petere;	state Exp;
branches;
next	1.5;

1.5
date	2001.03.05.18.42.56;	author momjian;	state Exp;
branches;
next	1.4;

1.4
date	2000.11.11.23.01.45;	author petere;	state Exp;
branches;
next	1.3;

1.3
date	2000.10.20.13.44.39;	author thomas;	state Exp;
branches;
next	1.2;

1.2
date	2000.10.10.22.03.31;	author momjian;	state Exp;
branches;
next	1.1;

1.1
date	2000.10.10.22.01.51;	author momjian;	state Exp;
branches;
next	;

1.15.2.1
date	2003.09.07.04.36.45;	author momjian;	state Exp;
branches;
next	;


desc
@@


1.30
log
@Split the LDFLAGS make variable into two parts: LDFLAGS is now used for
linking both executables and shared libraries, and we add on LDFLAGS_EX when
linking executables or LDFLAGS_SL when linking shared libraries.  This
provides a significantly cleaner way of dealing with link-time switches than
the former behavior.  Also, make sure that the various platform-specific
%.so: %.o rules incorporate LDFLAGS and LDFLAGS_SL; most of them missed that
before.  (I did not add these variables for the platforms that invoke $(LD)
directly, however.  It's not clear if we can do that safely, since for the
most part we assume these variables use CC command-line syntax.)

Per gripe from Aaron Swenson and subsequent investigation.
@
text
@<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.29 2010/04/03 07:23:01 petere Exp $ -->

<refentry id="app-pgconfig">
 <refmeta>
  <refentrytitle>pg_config</refentrytitle>
  <manvolnum>1</manvolnum>
  <refmiscinfo>Application</refmiscinfo>
 </refmeta>

 <refnamediv>
  <refname>pg_config</refname>
  <refpurpose>retrieve information about the installed version of <productname>PostgreSQL</></refpurpose>
 </refnamediv>

 <indexterm zone="app-pgconfig">
  <primary>pg_config</primary>
 </indexterm>

 <refsynopsisdiv>
  <cmdsynopsis>
   <command>pg_config</command>
   <arg rep="repeat"><replaceable>option</replaceable></arg>
  </cmdsynopsis>
 </refsynopsisdiv>

 <refsect1>
  <title>Description</>
  <para>
   The <application>pg_config</> utility prints configuration parameters
   of the currently installed version of <productname>PostgreSQL</>. It is
   intended, for example, to be used by software packages that want to interface
   to <productname>PostgreSQL</> to facilitate finding the required header files
   and libraries.
  </para>
 </refsect1>


 <refsect1>
  <title>Options</title>

  <para>
   To use <application>pg_config</>, supply one or more of the following
   options:
   <variablelist>
    <varlistentry>
     <term><option>--bindir</option></>
     <listitem>
      <para>
       Print the location of user executables. Use this, for example, to find
       the <command>psql</> program. This is normally also the location
       where the <filename>pg_config</> program resides.       
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--docdir</option></>
     <listitem>
      <para>
       Print the location of documentation files.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--htmldir</option></>
     <listitem>
      <para>
       Print the location of HTML documentation files.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--includedir</option></>
     <listitem>
      <para>
       Print the location of C header files of the client interfaces.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--pkgincludedir</option></>
     <listitem>
      <para>
       Print the location of other C header files.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--includedir-server</option></>
     <listitem>
      <para>
       Print the location of C header files for server programming.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--libdir</option></>
     <listitem>
      <para>
       Print the location of object code libraries.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--pkglibdir</option></>
     <listitem>
      <para>
       Print the location of dynamically loadable modules, or where
       the server would search for them.  (Other
       architecture-dependent data files might also be installed in this
       directory.)
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--localedir</option></>
     <listitem>
      <para>
       Print the location of locale support files.  (This will be an empty
       string if locale support was not configured when
       <productname>PostgreSQL</> was built.)
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--mandir</option></>
     <listitem>
      <para>
       Print the location of manual pages.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--sharedir</option></>
     <listitem>
      <para>
       Print the location of architecture-independent support files.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--sysconfdir</option></>
     <listitem>
      <para>
       Print the location of system-wide configuration files.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--pgxs</option></>
     <listitem>
      <para>
       Print the location of extension makefiles.
     </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--configure</option></>
     <listitem>
      <para>
       Print the options that were given to the <filename>configure</>
       script when <productname>PostgreSQL</> was configured for building.
       This can be used to reproduce the identical configuration, or
       to find out with what options a binary package was built. (Note
       however that binary packages often contain vendor-specific custom
       patches.)  See also the examples below.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--cc</option></>
     <listitem>
      <para>
       Print the value of the <varname>CC</varname> variable that was used for building
       <productname>PostgreSQL</>.  This shows the C compiler used.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--cppflags</option></>
     <listitem>
      <para>
       Print the value of the <varname>CPPFLAGS</varname> variable that was used for building
       <productname>PostgreSQL</>.  This shows C compiler switches needed
       at preprocessing time (typically, <literal>-I</> switches).
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--cflags</option></>
     <listitem>
      <para>
       Print the value of the <varname>CFLAGS</varname> variable that was used for building
       <productname>PostgreSQL</>.  This shows C compiler switches.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--cflags_sl</option></>
     <listitem>
      <para>
       Print the value of the <varname>CFLAGS_SL</varname> variable that was used for building
       <productname>PostgreSQL</>.  This shows extra C compiler switches
       used for building shared libraries.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--ldflags</option></>
     <listitem>
      <para>
       Print the value of the <varname>LDFLAGS</varname> variable that was used for building
       <productname>PostgreSQL</>.  This shows linker switches.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--ldflags_ex</option></>
     <listitem>
      <para>
       Print the value of the <varname>LDFLAGS_EX</varname> variable that was used for building
       <productname>PostgreSQL</>.  This shows linker switches
       used for building executables only.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--ldflags_sl</option></>
     <listitem>
      <para>
       Print the value of the <varname>LDFLAGS_SL</varname> variable that was used for building
       <productname>PostgreSQL</>.  This shows linker switches
       used for building shared libraries only.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--libs</option></>
     <listitem>
      <para>
       Print the value of the <varname>LIBS</varname> variable that was used for building
       <productname>PostgreSQL</>.  This normally contains <literal>-l</>
       switches for external libraries linked into <productname>PostgreSQL</>.
      </para>
     </listitem>
    </varlistentry>

    <varlistentry>
     <term><option>--version</option></>
     <listitem>
      <para>
       Print the version of <productname>PostgreSQL</>.
      </para>
     </listitem>
    </varlistentry>
   </variablelist>

   If more than one option is given, the information is printed in that order,
   one item per line.  If no options are given, all available information
   is printed, with labels.
  </para>
 </refsect1>


 <refsect1>
  <title>Notes</title>

  <para>
   The option <option>--includedir-server</option> was added in
   <productname>PostgreSQL</> 7.2.  In prior releases, the server include files were
   installed in the same location as the client headers, which could
   be queried with the option <option>--includedir</option>.  To make your
   package handle both cases, try the newer option first and test the
   exit status to see whether it succeeded.
  </para>

  <para>
   The options <option>--docdir</option>, <option>--pkgincludedir</option>,
   <option>--localedir</option>, <option>--mandir</option>,
   <option>--sharedir</option>, <option>--sysconfdir</option>,
   <option>--cc</option>, <option>--cppflags</option>,
   <option>--cflags</option>, <option>--cflags_sl</option>,
   <option>--ldflags</option>, <option>--ldflags_sl</option>,
   and <option>--libs</option> were added in <productname>PostgreSQL</> 8.1.
   The option <option>--htmldir</option> was added in <productname>PostgreSQL</> 8.4.
   The option <option>--ldflags_ex</option> was added in <productname>PostgreSQL</> 9.0.
  </para>

  <para>
   In releases prior to <productname>PostgreSQL</> 7.1, before
   <command>pg_config</command> came to be, a method for finding the
   equivalent configuration information did not exist.
  </para>
 </refsect1>


 <refsect1>
  <title>Example</title>

  <para>
   To reproduce the build configuration of the current PostgreSQL
   installation, run the following command:
<programlisting>
eval ./configure `pg_config --configure`
</programlisting>
   The output of <literal>pg_config --configure</literal> contains
   shell quotation marks so arguments with spaces are represented
   correctly.  Therefore, using <literal>eval</literal> is required
   for proper results.
  </para>
 </refsect1>

</refentry>
@


1.29
log
@Remove unnecessary xref endterm attributes and title ids

The endterm attribute is mainly useful when the toolchain does not support
automatic link target text generation for a particular situation.  In  the
past, this was required by the man page tools for all reference page links,
but that is no longer the case, and it now actually gets in the way of
proper automatic link text generation.  The only remaining use cases are
currently xrefs to refsects.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.28 2008/02/18 14:51:48 petere Exp $ -->
d236 11
d252 1
a252 1
       used for building shared libraries.
d289 1
a289 1
   The option <option>--includedir-server</option> was new in
d304 3
a306 2
   and <option>--libs</option> are new in <productname>PostgreSQL</> 8.1.
   The option <option>--htmldir</option> is new in <productname>PostgreSQL</> 8.4.
@


1.28
log
@Added --htmldir option to pg_config, equivalent to the new configure option.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.27 2007/02/20 15:01:17 momjian Exp $ -->
d5 1
a5 1
  <refentrytitle id="app-pgconfig-title">pg_config</refentrytitle>
@


1.27
log
@Remove "History" sections for pg_dump and pg_restore.  I don't think
anyone cares because the last history change was for PostgreSQL 7.1.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.26 2007/01/31 23:26:04 momjian Exp $ -->
d60 10
a69 3
       Print the location of documentation files.  (This will be an empty
       string if <literal>--without-docdir</> was specified when
       <productname>PostgreSQL</> was built.)
d294 1
@


1.26
log
@Update reference documentation on may/can/might:

Standard English uses "may", "can", and "might" in different ways:

        may - permission, "You may borrow my rake."

        can - ability, "I can lift that log."

        might - possibility, "It might rain today."

Unfortunately, in conversational English, their use is often mixed, as
in, "You may use this variable to do X", when in fact, "can" is a better
choice.  Similarly, "It may crash" is better stated, "It might crash".
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.25 2006/10/23 18:10:32 petere Exp $ -->
a312 8
 <refsect1>
  <title>History</title>

  <para>
   The <command>pg_config</command> utility first appeared in
   <productname>PostgreSQL</> 7.1.
  </para>
 </refsect1>
@


1.25
log
@Spellchecking and such
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.24 2006/09/16 00:30:19 momjian Exp $ -->
d109 1
a109 1
       architecture-dependent data files may also be installed in this
@


1.24
log
@Remove emacs info from footer of SGML files.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.23 2005/11/01 21:09:50 tgl Exp $ -->
d180 1
a180 1
       Print the value of the CC macro that was used for building
d190 1
a190 1
       Print the value of the CPPFLAGS macro that was used for building
d201 1
a201 1
       Print the value of the CFLAGS macro that was used for building
d211 1
a211 1
       Print the value of the CFLAGS_SL macro that was used for building
d222 1
a222 1
       Print the value of the LDFLAGS macro that was used for building
d232 1
a232 1
       Print the value of the LDFLAGS_SL macro that was used for building
d243 1
a243 1
       Print the value of the LIBS macro that was used for building
@


1.23
log
@Make an editorial pass over the reference pages.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.22 2005/09/27 17:39:32 tgl Exp $ -->
a321 17

<!-- Keep this comment at the end of the file
Local variables:
mode: sgml
sgml-omittag:nil
sgml-shorttag:t
sgml-minimize-attributes:nil
sgml-always-quote-attributes:t
sgml-indent-step:1
sgml-indent-data:t
sgml-parent-document:nil
sgml-default-dtd-file:"../reference.ced"
sgml-exposed-tags:nil
sgml-local-catalogs:"/usr/lib/sgml/catalog"
sgml-local-ecat-files:nil
End:
-->
@


1.22
log
@Fix problems with PGXS builds against an installation tree that was
relocated after installation.  We can't trust the installation paths
inserted into Makefile.global by configure, so instead we must get the
paths from pg_config.  This requires extending pg_config to support all
the separately-configurable path names, but that was on TODO anyway.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.21 2005/08/09 22:47:03 tgl Exp $ -->
d280 4
a283 1
   The options <option>--cc</option>, <option>--cppflags</option>,
@


1.21
log
@Extend pg_config to be able to report the build-time values of CC,
CPPFLAGS, CFLAGS, CFLAGS_SL, LDFLAGS, LDFLAGS_SL, and LIBS.  Change it
so that invoking pg_config with no arguments reports all available
information, rather than just giving an error message.  Per discussion.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.20 2005/06/09 18:15:05 petere Exp $ -->
d57 11
d77 9
d89 1
a89 2
       Print the location of C header files for server
       programming.
d116 38
@


1.20
log
@Add example for pg_config --configure.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.19 2005/01/04 03:58:16 tgl Exp $ -->
d22 1
a22 10
   <group choice="req" rep="repeat">
    <arg>--bindir</arg>
    <arg>--includedir</arg>
    <arg>--includedir-server</arg>
    <arg>--libdir</arg>
    <arg>--pkglibdir</arg>
    <arg>--pgxs</arg>
    <arg>--configure</arg>
    <arg>--version</arg>
   </group>
d42 2
a43 1
   To use <application>pg_config</>, supply one or more of the following options:
d120 74
d197 1
a197 1
       Print the version of <productname>PostgreSQL</> and exit.
d203 3
a205 2
   If more than one option (except for <option>--version</>) is given, the
   information is printed in that order, one item per line.
d223 7
@


1.19
log
@More minor updates and copy-editing.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.18 2004/08/02 12:34:14 momjian Exp $ -->
d122 1
a122 1
       patches.)
d164 16
@


1.18
log
@Readd pg_config --pgxs code.
@
text
@d1 1
a1 1
<!-- $PostgreSQL: pgsql-server/doc/src/sgml/ref/pg_config-ref.sgml,v 1.17 2003/11/29 19:51:39 pgsql Exp $ -->
d156 1
a156 1
   In releases prior to <productname>PostgreSQL</> 7.1, before the
@


1.17
log
@
$Header: -> $PostgreSQL Changes ...
@
text
@d1 1
a1 1
<!-- $PostgreSQL: /cvsroot/pgsql-server/doc/src/sgml/ref/pg_config-ref.sgml,v 1.16 2003/08/31 17:32:23 petere Exp $ -->
d28 1
d105 9
@


1.16
log
@Add/edit index entries.
@
text
@d1 1
a1 1
<!-- $Header: /cvsroot/pgsql-server/doc/src/sgml/ref/pg_config-ref.sgml,v 1.15 2003/03/25 16:15:42 petere Exp $ -->
@


1.15
log
@Merge documentation into one book.  (Build with "make html".)  Replace
vague cross-references with real links.
@
text
@d1 1
a1 1
<!-- $Header: /cvsroot/pgsql-server/doc/src/sgml/ref/pg_config-ref.sgml,v 1.14 2003/03/24 14:32:51 petere Exp $ -->
d14 4
@


1.15.2.1
log
@Update this branch to match CVS head, includes WIN32 improvements.
@
text
@d1 1
a1 1
<!-- $Header: /cvsroot/pgsql-server/doc/src/sgml/ref/pg_config-ref.sgml,v 1.16 2003/08/31 17:32:23 petere Exp $ -->
a13 4

 <indexterm zone="app-pgconfig">
  <primary>pg_config</primary>
 </indexterm>
@


1.14
log
@Another big editing pass for consistent content and presentation.
@
text
@d1 1
a1 1
<!-- $Header: /cvsroot/pgsql-server/doc/src/sgml/ref/pg_config-ref.sgml,v 1.13 2003/01/19 00:13:29 momjian Exp $ -->
a154 9
  </para>
 </refsect1>


 <refsect1>
  <title>See Also</title>

  <para>
   &cite-programmer;
@


1.13
log
@This patch includes a lot of minor cleanups to the SGML documentation,
including:

- replacing all the appropriate usages of <citetitle>PostgreSQL
...</citetitle> with &cite-user;, &cite-admin;, and so on

- fix an omission in the EXECUTE documentation

- add some more text to the EXPLAIN documentation

- improve the PL/PgSQL RETURN NEXT documentation (more work to do here)

- minor markup fixes


Neil Conway
@
text
@d1 1
a1 1
<!-- $Header: /cvsroot/pgsql-server/doc/src/sgml/ref/pg_config-ref.sgml,v 1.12 2002/11/15 03:11:18 momjian Exp $ -->
d53 1
a53 1
       the <application>psql</> program. This is normally also the location
d133 1
a133 1
   The option <option>--includedir-server</option> is new in
d136 1
a136 1
   be queried with the <option>--includedir</option>.  To make your
@


1.12
log
@SGML improvements.

Neil Conway
@
text
@d1 1
a1 1
<!-- $Header: /cvsroot/pgsql-server/doc/src/sgml/ref/pg_config-ref.sgml,v 1.11 2002/10/11 23:03:48 petere Exp $ -->
d163 1
a163 1
   <citetitle>PostgreSQL Programmer's Guide</citetitle>
d167 17
@


1.11
log
@Assorted reference page updates
@
text
@d1 1
a1 1
<!-- $Header: /cvsroot/pgsql-server/doc/src/sgml/ref/pg_config-ref.sgml,v 1.10 2002/04/21 19:02:39 thomas Exp $ -->
d134 1
a134 1
   PostgreSQL 7.2.  In prior releases, the server include files were
d142 1
a142 1
   In releases prior to PostgreSQL 7.1, before the
d153 2
a154 1
   The <command>pg_config</command> utility first appeared in PostgreSQL 7.1.
@


1.10
log
@Augment the date/time examples in the User's Guide to reflect the newer
 capabilities of specifying time zones as intervals per SQL9x.
Put refentrytitle contents on the same line as the tag.
 Otherwise, leading whitespace is propagated into the product, which
 (at least) messes up the ToC layout.
Remove (some) docinfo tags containing dates. Best to omit if the dates
 are not accurate; maybe use CVS dates instead or leave them out.
@
text
@d1 1
a1 1
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.9 2002/01/20 22:19:57 petere Exp $ -->
d63 1
a63 1
       Print the location of C and C++ header files of the client interfaces.
d72 1
a72 1
       Print the location of C and C++ header files for server
@


1.9
log
@Spell-check and markup police
@
text
@d1 1
a1 1
<!-- $Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.8 2001/09/16 16:11:09 petere Exp $ -->
a3 4
 <docinfo>
  <date>2000-11-11</date>
 </docinfo>

@


1.8
log
@Install dynamically loadable modules into a private subdirectory
under libdir, for a cleaner separation in the installation layout
and compatibility with binary packaging standards.  Point backend's
default search location there.  The contrib modules are also
installed in the said location, giving them the benefit of the
default search path as well.  No changes in user interface
nevertheless.
@
text
@d1 1
a1 1
<!-- $Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.7 2001/09/03 12:57:50 petere Exp $ -->
d53 1
a53 1
     <term>--bindir</>
d64 1
a64 1
     <term>--includedir</>
d73 1
a73 1
     <term>--includedir-server</>
d83 1
a83 1
     <term>--libdir</>
d92 1
a92 1
     <term>--pkglibdir</>
d104 1
a104 1
     <term>--configure</>
d118 1
a118 1
     <term>--version</>
@


1.7
log
@Put some kind of grammatical uniformity in the <refpurpose> lines.
@
text
@d1 1
a1 1
<!-- $Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.6 2001/08/28 14:20:26 petere Exp $ -->
d27 1
d87 12
@


1.6
log
@Include directory rearrangement

Client headers are no longer in a subdirectory, since they have been made
namespace-clean.

Internal libpq headers are in a private subdirectory.

Server headers are in a private subdirectory.  pg_config has a new option
to point there.
@
text
@d1 1
a1 1
<!-- $Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.5 2001/03/05 18:42:56 momjian Exp $ -->
d16 1
a16 1
  <refpurpose>Provides information about the installed version of <productname>PostgreSQL</></refpurpose>
@


1.5
log
@I'm attaching those diffs for the Reference Guide in a tar file, as
not all of them attached properly in the post I made a few minutes
ago. Please disregard those earlier files. The diffs in the tar file
replace them.

Pierce Tyler
@
text
@d1 1
a1 1
<!-- $Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.4 2000/11/11 23:01:45 petere Exp $ -->
d25 1
d36 1
a36 1
   The <application>pg_config</> utility provides configuration parameters
d39 1
a39 1
   to <productname>PostgreSQL</> in order to find the respective header files
d42 5
d66 11
a76 1
       Print the location of C and C++ header files.
d116 38
@


1.4
log
@Markup enhancements, some factual corrections.
@
text
@d1 1
a1 1
<!-- $Header: /home/projects/pgsql/cvsroot/pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.3 2000/10/20 13:44:39 thomas Exp $ -->
d35 1
a35 1
   The <application>pg_config</> stores and provides configuration parameters
@


1.3
log
@Fix up id tag parameters to omit illegal underscores.
Remove lots of extraneous trailing ^Ms from pg_restore.sgml.
@
text
@d1 1
a1 1
<!-- $Header$ -->
d4 4
d9 3
a11 2
  <refentrytitle id="app-pgconfig-title">pg_config</>
  <refmiscinfo>Application</>
d15 2
a16 2
  <refname>pg_config</>
  <refpurpose>Provides information about the installed version of <productname>PostgreSQL</></>
d20 10
a29 3
<synopsis>
pg_config --bindir | --includedir | --libdir | --configure | --version
</synopsis>
@


1.2
log
@More pg_config updates.
@
text
@d1 1
a1 1
<!-- $Header -->
d3 1
a3 1
<refentry id="app-pg_config">
d5 1
a5 1
  <refentrytitle id="app-pg_config-title">pg_config</>
@


1.1
log
@Rename pg-config to pg_config to be consistent with other pg commands.
@
text
@d3 1
a3 1
<refentry id="app-pg-config">
d5 1
a5 1
  <refentrytitle id="app-pg-config-title">pg-config</>
d10 1
a10 1
  <refname>pg-config</>
d16 1
a16 1
pg-config --bindir | --includedir | --libdir | --configure | --version
d23 1
a23 1
   The <application>pg-config</> stores and provides configuration parameters
d31 1
a31 1
   To use <application>pg-config</>, supply one or more of the following options:
d39 1
a39 1
       where the <filename>pg-config</> program resides.       
@
