know
        their target operating system well.  The main advantage of using this
        option is that the PostgreSQL package won't need to be upgraded
        whenever any of the many local daylight-saving time rules change.
        Another advantage is that PostgreSQL can be cross-compiled more
        straightforwardly if the time zone database files do not need to be
        built during the installation.
       </para>
      </listitem>
     </varlistentry>

     <varlistentry id="configure-extra-version-meson">
      <term><option>-Dextra_version=<replaceable>STRING</replaceable></option></term>
      <listitem>
       <para>
        Append <replaceable>STRING</replaceable> to the PostgreSQL version
        number.  You can use this, for example, to mark binaries built from
        unreleased <productname>Git</productname> snapshots or containing
        custom patches with an extra version string, such as a <command>git
        describe</command> identifier or a distribution package release
        number.
       </para>
      </listitem>
     </varlistentry>

     <varlistentry id="configure-rpath-meson">
      <term><option>-Drpath={ true | false }</option></term>
      <listitem>
       <para>
        This option is set to true by default.  If set to false,
        do not mark <productname>PostgreSQL</productname>'s executables
        to indicate that they should search for shared libraries in the
        installation's library directory (see <option>--libdir</option>).
        On most platforms, this marking uses an absolute path to the
        library directory, so that it will be unhelpful if you relocate
        the installation later.  However, you will then need to provide
        some other way for the executables to find the shared libraries.
        Typically this requires configuring the operating system's
        dynamic linker to search the library directory; see
        <xref linkend="install-post-shlibs"/> for more detail.
       </para>
      </listitem>
     </varlistentry>

     <varlistentry id="configure-binary-name-meson">
      <term><option>-D<replaceable>BINARY_NAME</replaceable>=<replaceable>PATH</replaceable></option></term>
      <listitem>
       <para>
        If a program required to build PostgreSQL (with or without optional
        flags) is stored at a non-standard path, you can specify it manually
        to <literal>meson configure</literal>.  The complete list of programs
        for which this is supported can be found by running <literal>meson
        configure</literal>.  Example:
<programlisting>meson configure -DBISON=PATH_TO_BISON</programlisting>
       </para>
      </listitem>
     </varlistentry>
    </variablelist>
   </sect3>

   <sect3 id="meson-options-docs">
    <title>Documentation</title>

    <para>
     See <xref linkend="docguide-toolsets"/> for the tools needed for building
     the documentation.
    </para>

    <variablelist>

     <varlistentry id="configure-docs-meson">
      <term><option>-Ddocs={ auto | enabled | disabled }</option></term>
      <listitem>
       <para>
        Enables building the documentation in <acronym>HTML</acronym> and
        <acronym>man</acronym> format. It defaults to auto.
       </para>
      </listitem>
     </varlistentry>

     <varlistentry id="configure-docs-pdf-meson">
      <term><option>-Ddocs_pdf={ auto | enabled | disabled }</option></term>
      <listitem>
       <para>
        Enables building the documentation in <acronym>PDF</acronym>
        format. It defaults to auto.
       </para>
      </listitem>
     </varlistentry>

     <varlistentry id="configure-docs-html-style">
      <term><option>-Ddocs_html_style={ simple | website }</option></term>
      <listitem>
       <para>
        Controls which <acronym>CSS</acronym> stylesheet is used.  The default
        is <literal>simple</literal>.  If set to <literal>website</literal>,
        the HTML documentation will reference the stylesheet for <ulink