Baoding-FenShuaJiang
/
Green_GoodERP18_FSJ_Standard
Следить 1
В избранное 0
Вики 捐赠
gooderp18绿色标准版
Вы не можете выбрать более 25 тем Темы должны начинаться с буквы или цифры, могут содержать дефисы(-) и должны содержать не более 35 символов.
Дерево: 0f75e31513
Ветки Теги
${ item.name }
Создать ветку ${ searchTerm }
из '0f75e31513'
${ noResults }
Green_GoodERP18_FSJ_Standard/PostgreSQL/doc/postgresql/html/install-windows-full.html

294 lines
22KB
Исходник Blame История 

  1. <?xml version="1.0" encoding="UTF-8" standalone="no"?>

  2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.1. Building with Visual C++ or the Microsoft Windows SDK</title><link rel="stylesheet" type="text/css" href="stylesheet.css" /><link rev="made" href="pgsql-docs@lists.postgresql.org" /><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /><link rel="prev" href="install-windows.html" title="Chapter 17. Installation from Source Code on Windows" /><link rel="next" href="runtime.html" title="Chapter 18. Server Setup and Operation" /></head><body><div xmlns="http://www.w3.org/TR/xhtml1/transitional" class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="5" align="center">17.1. Building with <span xmlns="http://www.w3.org/1999/xhtml" class="productname">Visual C++</span> or the

  3.   <span xmlns="http://www.w3.org/1999/xhtml" class="productname">Microsoft Windows SDK</span></th></tr><tr><td width="10%" align="left"><a accesskey="p" href="install-windows.html" title="Chapter 17. Installation from Source Code on Windows">Prev</a> </td><td width="10%" align="left"><a accesskey="u" href="install-windows.html" title="Chapter 17. Installation from Source Code on Windows">Up</a></td><th width="60%" align="center">Chapter 17. Installation from Source Code on <span xmlns="http://www.w3.org/1999/xhtml" class="productname">Windows</span></th><td width="10%" align="right"><a accesskey="h" href="index.html" title="PostgreSQL 12.4 Documentation">Home</a></td><td width="10%" align="right"> <a accesskey="n" href="runtime.html" title="Chapter 18. Server Setup and Operation">Next</a></td></tr></table><hr></hr></div><div class="sect1" id="INSTALL-WINDOWS-FULL"><div class="titlepage"><div><div><h2 class="title" style="clear: both">17.1. Building with <span class="productname">Visual C++</span> or the

  4.   <span class="productname">Microsoft Windows SDK</span></h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="sect2"><a href="install-windows-full.html#id-1.6.4.8.8">17.1.1. Requirements</a></span></dt><dt><span class="sect2"><a href="install-windows-full.html#id-1.6.4.8.9">17.1.2. Special Considerations for 64-Bit Windows</a></span></dt><dt><span class="sect2"><a href="install-windows-full.html#id-1.6.4.8.10">17.1.3. Building</a></span></dt><dt><span class="sect2"><a href="install-windows-full.html#id-1.6.4.8.11">17.1.4. Cleaning and Installing</a></span></dt><dt><span class="sect2"><a href="install-windows-full.html#id-1.6.4.8.12">17.1.5. Running the Regression Tests</a></span></dt></dl></div><p>

  5.   PostgreSQL can be built using the Visual C++ compiler suite from Microsoft.

  6.   These compilers can be either from <span class="productname">Visual Studio</span>,

  7.   <span class="productname">Visual Studio Express</span> or some versions of the

  8.   <span class="productname">Microsoft Windows SDK</span>. If you do not already have a

  9.   <span class="productname">Visual Studio</span> environment set up, the easiest

  10.   ways are to use the compilers from

  11.   <span class="productname">Visual Studio 2019</span> or those in the

  12.   <span class="productname">Windows SDK 10</span>, which are both free downloads

  13.   from Microsoft.

  14.  </p><p>

  15.   Both 32-bit and 64-bit builds are possible with the Microsoft Compiler suite.

  16.   32-bit PostgreSQL builds are possible with

  17.   <span class="productname">Visual Studio 2013</span> to

  18.   <span class="productname">Visual Studio 2019</span>,

  19.   as well as standalone Windows SDK releases 8.1a to 10.

  20.   64-bit PostgreSQL builds are supported with

  21.   <span class="productname">Microsoft Windows SDK</span> version 8.1a to 10 or

  22.   <span class="productname">Visual Studio 2013</span> and above. Compilation

  23.   is supported down to <span class="productname">Windows 7</span> and

  24.   <span class="productname">Windows Server 2008 R2 SP1</span> when building with

  25.   <span class="productname">Visual Studio 2013</span> to

  26.   <span class="productname">Visual Studio 2019</span>.

  27.    

  28.  </p><p>

  29.   The tools for building using <span class="productname">Visual C++</span> or

  30.   <span class="productname">Platform SDK</span> are in the

  31.   <code class="filename">src/tools/msvc</code> directory. When building, make sure

  32.   there are no tools from <span class="productname">MinGW</span> or

  33.   <span class="productname">Cygwin</span> present in your system PATH. Also, make

  34.   sure you have all the required Visual C++ tools available in the PATH. In

  35.   <span class="productname">Visual Studio</span>, start the

  36.   <span class="application">Visual Studio Command Prompt</span>.

  37.   If you wish to build a 64-bit version, you must use the 64-bit version of

  38.   the command, and vice versa.

  39.   Starting with <span class="productname">Visual Studio 2017</span> this can be

  40.   done from the command line using <code class="command">VsDevCmd.bat</code>, see

  41.   <code class="command">-help</code> for the available options and their default values.

  42.   <code class="command">vsvars32.bat</code> is available in

  43.   <span class="productname">Visual Studio 2015</span> and earlier versions for the

  44.   same purpose.

  45.   From the <span class="application">Visual Studio Command Prompt</span>, you can

  46.   change the targeted CPU architecture, build type, and target OS by using the

  47.   <code class="command">vcvarsall.bat</code> command, e.g.

  48.   <code class="command">vcvarsall.bat x64 10.0.10240.0</code> to target Windows 10

  49.   with a 64-bit release build. See <code class="command">-help</code> for the other

  50.   options of <code class="command">vcvarsall.bat</code>. All commands should be run from

  51.   the <code class="filename">src\tools\msvc</code> directory.

  52.  </p><p>

  53.   Before you build, you may need to edit the file <code class="filename">config.pl</code>

  54.   to reflect any configuration options you want to change, or the paths to

  55.   any third party libraries to use. The complete configuration is determined

  56.   by first reading and parsing the file <code class="filename">config_default.pl</code>,

  57.   and then apply any changes from <code class="filename">config.pl</code>. For example,

  58.   to specify the location of your <span class="productname">Python</span> installation,

  59.   put the following in <code class="filename">config.pl</code>:

  60. </p><pre class="programlisting">

  61. $config-&gt;{python} = 'c:\python26';

  62. </pre><p>

  63.   You only need to specify those parameters that are different from what's in

  64.   <code class="filename">config_default.pl</code>.

  65.  </p><p>

  66.   If you need to set any other environment variables, create a file called

  67.   <code class="filename">buildenv.pl</code> and put the required commands there. For

  68.   example, to add the path for bison when it's not in the PATH, create a file

  69.   containing:

  70. </p><pre class="programlisting">

  71. $ENV{PATH}=$ENV{PATH} . ';c:\some\where\bison\bin';

  72. </pre><p>

  73.  </p><p>

  74.   To pass additional command line arguments to the Visual Studio build

  75.   command (msbuild or vcbuild):

  76. </p><pre class="programlisting">

  77. $ENV{MSBFLAGS}="/m";

  78. </pre><p>

  79.  </p><div class="sect2" id="id-1.6.4.8.8"><div class="titlepage"><div><div><h3 class="title">17.1.1. Requirements</h3></div></div></div><p>

  80.    The following additional products are required to build

  81.    <span class="productname">PostgreSQL</span>. Use the

  82.    <code class="filename">config.pl</code> file to specify which directories the libraries

  83.    are available in.

  84. 

  85.    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><span class="productname">Microsoft Windows SDK</span></span></dt><dd><p>

  86.       If your build environment doesn't ship with a supported version of the

  87.       <span class="productname">Microsoft Windows SDK</span> it

  88.       is recommended that you upgrade to the latest version (currently

  89.       version 10), available for download from

  90.       <a class="ulink" href="https://www.microsoft.com/download" target="_top">https://www.microsoft.com/download</a>.

  91.      </p><p>

  92.       You must always include the

  93.       <span class="application">Windows Headers and Libraries</span> part of the SDK.

  94.       If you install a <span class="productname">Windows SDK</span>

  95.       including the <span class="application">Visual C++ Compilers</span>,

  96.       you don't need <span class="productname">Visual Studio</span> to build.

  97.       Note that as of Version 8.0a the Windows SDK no longer ships with a

  98.       complete command-line build environment.

  99.      </p></dd><dt><span class="term"><span class="productname">ActiveState Perl</span></span></dt><dd><p>

  100.       ActiveState Perl is required to run the build generation scripts. MinGW

  101.       or Cygwin Perl will not work. It must also be present in the PATH.

  102.       Binaries can be downloaded from

  103.       <a class="ulink" href="https://www.activestate.com" target="_top">https://www.activestate.com</a>

  104.       (Note: version 5.8.3 or later is required,

  105.       the free Standard Distribution is sufficient).

  106.      </p></dd></dl></div><p>

  107.   </p><p>

  108.    The following additional products are not required to get started,

  109.    but are required to build the complete package. Use the

  110.    <code class="filename">config.pl</code> file to specify which directories the libraries

  111.    are available in.

  112. 

  113.    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><span class="productname">ActiveState TCL</span></span></dt><dd><p>

  114.       Required for building <span class="application">PL/Tcl</span> (Note: version

  115.       8.4 is required, the free Standard Distribution is sufficient).

  116.      </p></dd><dt><span class="term"><span class="productname">Bison</span> and

  117.       <span class="productname">Flex</span></span></dt><dd><p>

  118.       <span class="productname">Bison</span> and <span class="productname">Flex</span> are

  119.       required to build from Git, but not required when building from a release

  120.       file. Only <span class="productname">Bison</span> 1.875 or versions 2.2 and later

  121.       will work. <span class="productname">Flex</span> must be version 2.5.31 or later.

  122.      </p><p>

  123.       Both <span class="productname">Bison</span> and <span class="productname">Flex</span>

  124.       are included in the <span class="productname">msys</span> tool suite, available

  125.       from <a class="ulink" href="http://www.mingw.org/wiki/MSYS" target="_top">http://www.mingw.org/wiki/MSYS</a> as part of the

  126.       <span class="productname">MinGW</span> compiler suite.

  127.      </p><p>

  128.       You will need to add the directory containing

  129.       <code class="filename">flex.exe</code> and <code class="filename">bison.exe</code> to the

  130.       PATH environment variable in <code class="filename">buildenv.pl</code> unless

  131.       they are already in PATH. In the case of MinGW, the directory is the

  132.       <code class="filename">\msys\1.0\bin</code> subdirectory of your MinGW

  133.       installation directory.

  134.      </p><div class="note"><h3 class="title">Note</h3><p>

  135.         The Bison distribution from GnuWin32 appears to have a bug that

  136.         causes Bison to malfunction when installed in a directory with

  137.         spaces in the name, such as the default location on English

  138.         installations <code class="filename">C:\Program Files\GnuWin32</code>.

  139.         Consider installing into <code class="filename">C:\GnuWin32</code> or use the

  140.         NTFS short name path to GnuWin32 in your PATH environment setting

  141.         (e.g. <code class="filename">C:\PROGRA~1\GnuWin32</code>).

  142.        </p></div><div class="note"><h3 class="title">Note</h3><p>

  143.        The obsolete <code class="literal">winflex</code> binaries distributed on the PostgreSQL FTP site

  144.        and referenced in older documentation will fail with <span class="quote">“<span class="quote">flex: fatal

  145.        internal error, exec failed</span>”</span> on 64-bit Windows hosts. Use Flex from

  146.        MSYS instead.

  147.        </p></div></dd><dt><span class="term"><span class="productname">Diff</span></span></dt><dd><p>

  148.       Diff is required to run the regression tests, and can be downloaded

  149.       from <a class="ulink" href="http://gnuwin32.sourceforge.net" target="_top">http://gnuwin32.sourceforge.net</a>.

  150.      </p></dd><dt><span class="term"><span class="productname">Gettext</span></span></dt><dd><p>

  151.       Gettext is required to build with NLS support, and can be downloaded

  152.       from <a class="ulink" href="http://gnuwin32.sourceforge.net" target="_top">http://gnuwin32.sourceforge.net</a>. Note that binaries,

  153.       dependencies and developer files are all needed.

  154.      </p></dd><dt><span class="term"><span class="productname">MIT Kerberos</span></span></dt><dd><p>

  155.       Required for GSSAPI authentication support. MIT Kerberos can be

  156.       downloaded from

  157.       <a class="ulink" href="https://web.mit.edu/Kerberos/dist/index.html" target="_top">https://web.mit.edu/Kerberos/dist/index.html</a>.

  158.      </p></dd><dt><span class="term"><span class="productname">libxml2</span> and

  159.       <span class="productname">libxslt</span></span></dt><dd><p>

  160.       Required for XML support. Binaries can be downloaded from

  161.       <a class="ulink" href="https://zlatkovic.com/pub/libxml" target="_top">https://zlatkovic.com/pub/libxml</a> or source from

  162.       <a class="ulink" href="http://xmlsoft.org" target="_top">http://xmlsoft.org</a>. Note that libxml2 requires iconv,

  163.       which is available from the same download location.

  164.      </p></dd><dt><span class="term"><span class="productname">OpenSSL</span></span></dt><dd><p>

  165.       Required for SSL support. Binaries can be downloaded from

  166.       <a class="ulink" href="https://slproweb.com/products/Win32OpenSSL.html" target="_top">https://slproweb.com/products/Win32OpenSSL.html</a>

  167.       or source from <a class="ulink" href="https://www.openssl.org" target="_top">https://www.openssl.org</a>.

  168.      </p></dd><dt><span class="term"><span class="productname">ossp-uuid</span></span></dt><dd><p>

  169.       Required for UUID-OSSP support (contrib only). Source can be

  170.       downloaded from

  171.       <a class="ulink" href="http://www.ossp.org/pkg/lib/uuid/" target="_top">http://www.ossp.org/pkg/lib/uuid/</a>.

  172.      </p></dd><dt><span class="term"><span class="productname">Python</span></span></dt><dd><p>

  173.       Required for building <span class="application">PL/Python</span>. Binaries can

  174.       be downloaded from <a class="ulink" href="https://www.python.org" target="_top">https://www.python.org</a>.

  175.      </p></dd><dt><span class="term"><span class="productname">zlib</span></span></dt><dd><p>

  176.       Required for compression support in <span class="application">pg_dump</span>

  177.       and <span class="application">pg_restore</span>. Binaries can be downloaded

  178.       from <a class="ulink" href="https://www.zlib.net" target="_top">https://www.zlib.net</a>.

  179.      </p></dd></dl></div><p>

  180.   </p></div><div class="sect2" id="id-1.6.4.8.9"><div class="titlepage"><div><div><h3 class="title">17.1.2. Special Considerations for 64-Bit Windows</h3></div></div></div><p>

  181.    PostgreSQL will only build for the x64 architecture on 64-bit Windows, there

  182.    is no support for Itanium processors.

  183.   </p><p>

  184.    Mixing 32- and 64-bit versions in the same build tree is not supported.

  185.    The build system will automatically detect if it's running in a 32- or

  186.    64-bit environment, and build PostgreSQL accordingly. For this reason, it

  187.    is important to start the correct command prompt before building.

  188.   </p><p>

  189.    To use a server-side third party library such as <span class="productname">python</span> or

  190.    <span class="productname">OpenSSL</span>, this library <span class="emphasis"><em>must</em></span> also be

  191.    64-bit. There is no support for loading a 32-bit library in a 64-bit

  192.    server. Several of the third party libraries that PostgreSQL supports may

  193.    only be available in 32-bit versions, in which case they cannot be used with

  194.    64-bit PostgreSQL.

  195.   </p></div><div class="sect2" id="id-1.6.4.8.10"><div class="titlepage"><div><div><h3 class="title">17.1.3. Building</h3></div></div></div><p>

  196.    To build all of PostgreSQL in release configuration (the default), run the

  197.    command:

  198. </p><pre class="screen">

  199. <strong class="userinput"><code>build</code></strong>

  200. </pre><p>

  201.    To build all of PostgreSQL in debug configuration, run the command:

  202. </p><pre class="screen">

  203. <strong class="userinput"><code>build DEBUG</code></strong>

  204. </pre><p>

  205.    To build just a single project, for example psql, run the commands:

  206. </p><pre class="screen">

  207. <strong class="userinput"><code>build psql</code></strong>

  208. <strong class="userinput"><code>build DEBUG psql</code></strong>

  209. </pre><p>

  210.    To change the default build configuration to debug, put the following

  211.    in the <code class="filename">buildenv.pl</code> file:

  212. </p><pre class="programlisting">

  213. $ENV{CONFIG}="Debug";

  214. </pre><p>

  215.   </p><p>

  216.    It is also possible to build from inside the Visual Studio GUI. In this

  217.    case, you need to run:

  218. </p><pre class="screen">

  219. <strong class="userinput"><code>perl mkvcbuild.pl</code></strong>

  220. </pre><p>

  221.    from the command prompt, and then open the generated

  222.    <code class="filename">pgsql.sln</code> (in the root directory of the source tree)

  223.    in Visual Studio.

  224.   </p></div><div class="sect2" id="id-1.6.4.8.11"><div class="titlepage"><div><div><h3 class="title">17.1.4. Cleaning and Installing</h3></div></div></div><p>

  225.    Most of the time, the automatic dependency tracking in Visual Studio will

  226.    handle changed files. But if there have been large changes, you may need

  227.    to clean the installation. To do this, simply run the

  228.    <code class="filename">clean.bat</code> command, which will automatically clean out

  229.    all generated files. You can also run it with the

  230.    <em class="parameter"><code>dist</code></em> parameter, in which case it will behave like

  231.    <strong class="userinput"><code>make distclean</code></strong> and remove the flex/bison output files

  232.    as well.

  233.   </p><p>

  234.    By default, all files are written into a subdirectory of the

  235.    <code class="filename">debug</code> or <code class="filename">release</code> directories. To

  236.    install these files using the standard layout, and also generate the files

  237.    required to initialize and use the database, run the command:

  238. </p><pre class="screen">

  239. <strong class="userinput"><code>install c:\destination\directory</code></strong>

  240. </pre><p>

  241.   </p><p>

  242.    If you want to install only the client applications and

  243.    interface libraries, then you can use these commands:

  244. </p><pre class="screen">

  245. <strong class="userinput"><code>install c:\destination\directory client</code></strong>

  246. </pre><p>

  247.   </p></div><div class="sect2" id="id-1.6.4.8.12"><div class="titlepage"><div><div><h3 class="title">17.1.5. Running the Regression Tests</h3></div></div></div><p>

  248.    To run the regression tests, make sure you have completed the build of all

  249.    required parts first. Also, make sure that the DLLs required to load all

  250.    parts of the system (such as the Perl and Python DLLs for the procedural

  251.    languages) are present in the system path. If they are not, set it through

  252.    the <code class="filename">buildenv.pl</code> file. To run the tests, run one of

  253.    the following commands from the <code class="filename">src\tools\msvc</code>

  254.    directory:

  255. </p><pre class="screen">

  256. <strong class="userinput"><code>vcregress check</code></strong>

  257. <strong class="userinput"><code>vcregress installcheck</code></strong>

  258. <strong class="userinput"><code>vcregress plcheck</code></strong>

  259. <strong class="userinput"><code>vcregress contribcheck</code></strong>

  260. <strong class="userinput"><code>vcregress modulescheck</code></strong>

  261. <strong class="userinput"><code>vcregress ecpgcheck</code></strong>

  262. <strong class="userinput"><code>vcregress isolationcheck</code></strong>

  263. <strong class="userinput"><code>vcregress bincheck</code></strong>

  264. <strong class="userinput"><code>vcregress recoverycheck</code></strong>

  265. <strong class="userinput"><code>vcregress upgradecheck</code></strong>

  266. </pre><p>

  267. 

  268.    To change the schedule used (default is parallel), append it to the

  269.    command line like:

  270. </p><pre class="screen">

  271. <strong class="userinput"><code>vcregress check serial</code></strong>

  272. </pre><p>

  273. 

  274.    For more information about the regression tests, see

  275.    <a class="xref" href="regress.html" title="Chapter 32. Regression Tests">Chapter 32</a>.

  276.   </p><p>

  277.    Running the regression tests on client programs, with

  278.    <code class="command">vcregress bincheck</code>, or on recovery tests, with

  279.    <code class="command">vcregress recoverycheck</code>, requires an additional Perl module

  280.    to be installed:

  281.    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><span class="productname">IPC::Run</span></span></dt><dd><p>

  282.       As of this writing, <code class="literal">IPC::Run</code> is not included in the

  283.       ActiveState Perl installation, nor in the ActiveState Perl Package

  284.       Manager (PPM) library. To install, download the

  285.       <code class="filename">IPC-Run-&lt;version&gt;.tar.gz</code> source archive from CPAN,

  286.       at <a class="ulink" href="https://metacpan.org/release/IPC-Run" target="_top">https://metacpan.org/release/IPC-Run</a>, and

  287.       uncompress. Edit the <code class="filename">buildenv.pl</code> file, and add a PERL5LIB

  288.       variable to point to the <code class="filename">lib</code> subdirectory from the

  289.       extracted archive. For example:

  290. </p><pre class="programlisting">

  291. $ENV{PERL5LIB}=$ENV{PERL5LIB} . ';c:\IPC-Run-0.94\lib';

  292. </pre><p>

  293.      </p></dd></dl></div><p>

  294.   </p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="install-windows.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="install-windows.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="runtime.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 17. Installation from Source Code on <span class="productname">Windows</span> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 18. Server Setup and Operation</td></tr></table></div></body></html>
上海开阖软件有限公司 沪ICP备12045867号-1