This commit is contained in:
Peter Eisentraut 2000-12-21 22:30:39 +00:00
parent d7b161031d
commit 8f89113d4b
1 changed files with 97 additions and 86 deletions

View File

@ -1,101 +1,112 @@
<chapter id="install-win32"> <chapter id="install-win32">
<title>Installation on Win32</title> <title>Installation on <productname>Windows</productname></title>
<abstract> <abstract>
<para> <para>
Build and installation instructions for <productname>Postgres</productname> Build, installation, and use instructions for
v6.4 client libraries on Win32. <productname>PostgreSQL</productname> client libraries on
</para> <productname>Windows</productname>
</abstract> </para>
</abstract>
<sect1 id="win32-install-build"> <para>
<title>Building the libraries</title> Although <productname>PostgreSQL</productname> is written for
Unix-like operating systems, the C client library
(<application>libpq</application>) and the interactive terminal
(<application>psql</application>) can be compiled natively under
Windows. The makefiles included in the source distribution are
written for <productname>Microsoft Visual C++</productname> and will
probably not work with other systems. It should be possible to
compile the libaries manually in other cases.
</para>
<para> <tip>
The makefiles included in <productname>Postgres</productname> are written <para>
for <productname>Microsoft Visual C++</productname>, and will probably If you are using Windows NT/2000 you can build and use all of
not work with other systems. It should be possible to compile the libaries <productname>PostgreSQL</productname> <quote>the Unix way</quote>
manually in other cases. if you install the <productname>Cygwin</productname> toolkit first.
</para> In that case see <xref linkend="installation">.
</para>
</tip>
<para> <para>
To build the libraries, change directory into the <filename>src</filename> To build everything that you can on
directory, and type the commands <productname>Windows</productname>, change into the
<programlisting> <filename>src</filename> directory and type the command
copy include\config.h.win32 include\config.h <screen>
nmake /f win32.mak <userinput>nmake /f win32.mak</userinput>
</programlisting> </screen>
This assumes that you have <productname>Visual C++</productname> in your This assumes that you have <productname>Visual C++</productname> in
path. your path.
</para> </para>
<para> <para>
The following files will be built: The following files will be built:
<itemizedlist spacing="compact" mark="bullet"> <variablelist>
<listitem> <varlistentry>
<para> <term><filename>interfaces\libpq\Release\libpq.dll</filename></term>
<filename>interfaces\libpq\Release\libpq.dll</filename> <listitem>
- The dynamically linkable frontend library <para>
</para> The dynamically linkable frontend library
</listitem> </para>
</listitem>
</varlistentry>
<varlistentry>
<term><filename>interfaces\libpq\Release\libpqdll.lib</filename></term>
<listitem>
<para>
Import library to link your program to <filename>libpq.dll</filename>
</para>
</listitem>
</varlistentry>
<listitem> <varlistentry>
<para> <term><filename>interfaces\libpq\Release\libpq.lib</filename></term>
<filename>interfaces\libpq\Release\libpqdll.lib</filename> <listitem>
- Import library to link your program to libpq.dll <para>
</para> Static library version of the frontend library
</listitem> </para>
</listitem>
</varlistentry>
<listitem> <varlistentry>
<para> <term><filename>bin\psql\Release\psql.exe</filename></term>
<filename>interfaces\libpq\Release\libpq.lib</filename> - Static library version of the frontend library <listitem>
</para> <para>
</listitem> The <productname>PostgreSQL</productname> interactive terminal
</para>
</listitem>
</varlistentry>
</variablelist>
</para>
<listitem> <para>
<para> The only file that really needs to be installed is the
<filename>bin\psql\Release\psql.exe</filename> - The <productname>Postgresql</productname> interactive SQL monitor <filename>libpq.dll</filename> library. This file should in most
</para> cases be placed in the <filename>WINNT\SYSTEM32</filename> directory
</listitem> (or in <filename>WINDOWS\SYSTEM</filename> on a Windows 95/98/ME
system). If this file is installed using a setup program, it should
be installed with version checking using the
<symbol>VERSIONINFO</symbol> resource included in the file, to
ensure that a newer version of the library is not overwritten.
</para>
</itemizedlist> <para>
</para> If you plan to do development using libpq on this machine, you will
have to add the <filename>src\include</filename> and
<filename>src\interfaces\libpq</filename> subdirectories of the
source tree to the include path in your compilers settings.
</para>
</sect1> <para>
To use the libraries, you must add the
<filename>libpqdll.lib</filename> file to your project. (In Visual
C++, just right-click on the project and chose to add it.)
</para>
<sect1 id="win32-install-install"> </chapter>
<title>Installing the libraries</title>
<para>
The only part of the library to really be installed is the
<filename>libpq.dll</filename> library. This file should in most cases
be placed in the <filename>WINNT\SYSTEM32</filename> directory (or in
<filename>WINDOWS\SYSTEM</filename> on a Windows 95/98 system). If this
file is installed using a setup program, it should be installed with
version checking using the VERSIONINFO resource included in the file,
to ensure that a newer version of the library is not overwritten.
</para>
<para>
If you plan to do development using libpq on this machine, you will have
to add the <filename>src\include</filename> and
<filename>src\interfaces\libpq</filename> directories to the include
path in your compilers settings.
</para>
</sect1>
<sect1 id="win32-install-use">
<title>Using the libraries</title>
<para>
To use the libraries, you must add the <filename>libpqdll.lib</filename>
file to your project (in Visual C++, just right-click on the project and
chose to add it).
</para>
<para>
Once this is done, it should be possible to use the library just as you
would on a Unix platform.
</para>
</sect1>
</chapter>
<!-- Keep this comment at the end of the file <!-- Keep this comment at the end of the file
Local variables: Local variables: