Received: from golem.jpl.nasa.gov (IDENT:root@hectic-2.jpl.nasa.gov
	[128.149.68.204]) by hub.org (8.9.1/8.9.1) with ESMTP id MAA17117
	for <docs@postgresql.org>; Wed, 6 Jan 1999 12:20:39 -0500 (EST)
	(envelope-from lockhart@alumni.caltech.edu)
Received: from alumni.caltech.edu (localhost [127.0.0.1])
	by golem.jpl.nasa.gov (8.8.5/8.8.5) with ESMTP id RAA00969;
	Wed, 6 Jan 1999 17:20:29 GMT
Sender: tgl@mythos.jpl.nasa.gov
Message-ID: <36939B5C.535B0672@alumni.caltech.edu>
Date: Wed, 06 Jan 1999 17:20:28 +0000
From: "Thomas G. Lockhart" <lockhart@alumni.caltech.edu>
Organization: Caltech/JPL
X-Mailer: Mozilla 4.07 [en] (X11; I; Linux 2.0.30 i686)
MIME-Version: 1.0
To: Magnus Hagander <mha@sollentuna.net>
CC: Postgres Documentation List <docs@postgresql.org>
Subject: Re: Postgresql INSTALL-file & Windows
References: 
 <215896B6B5E1CF11BC5600805FFEA821012A2FFC@sirius.edu.sollentuna.se>
Content-Type: multipart/mixed; boundary="------------C831A728C21585D3CD8B8CB0"

This is a multi-part message in MIME format.
--------------C831A728C21585D3CD8B8CB0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

(back on-list)

> Here is a first try.
> So, please take a look at it and see if it'll do.

It'll do :) I made very minor typo changes (things which are caught
immediately by the html generator so it was really easy).

For markup, there are one or two places where fancier markup would work,
but what you have is just fine. For example, in one place you have an
aside in parens about something specific to VC++, and that could be
marked up as a <tip> or <note>. But that's _really_ not a problem.

> I'm going to try to whip up some precompiled binaries for it too, 
> tomorrow. Perhaps we should put a blurb in about that?

Yes. Here is the modified file back (note the minor name change) if you
want to mention it in there. Byron has some compiled binaries for Win32
ODBC, and I might post compiled binaries for Linux ODBC, so we should
figure out where to put these kinds of binaries. There probably should
be a win32 directory of some sort on the ftp site.

I'll commit to the cvs tree in a day or two, or after you have more
changes if those are coming earlier.

Thanks for the work!

                  - Tom
--------------C831A728C21585D3CD8B8CB0
Content-Type: text/html; charset=us-ascii; name="install-win32.sgml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="install-win32.sgml"
Content-Base: "file:/opt/postgres/current/doc/src/sgm
	l/install-win32.sgml"

<Chapter Id="install-win32">
<Title>Installation on Win32</Title>

<Abstract>
<Para>
Build and installation instructions for <ProductName>Postgres</ProductName>
v6.4 client libraries on Win32.
</Para>
</Abstract>

<Sect1>
<Title>Building the libraries</Title>

<Para>
The makefiles included in <ProductName>Postgres</ProductName> 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>
To build the libraries, change directory into the <filename>src</filename>
directory, and type the command
<programlisting>
nmake /f win32.mak
</programlisting>
This assumes that you have <ProductName>Visual C++</ProductName> in your
path.
</Para>

<Para>
The following files will be built:

<ItemizedList Mark="bullet" Spacing="compact">
<ListItem>
<Para>
<filename>interfaces\libpq\Release\libpq.dll</filename>
 - The dynamically linkable frontend library
</Para>
</ListItem>

<ListItem>
<Para>
<filename>interfaces\libpq\Release\libpqdll.lib</filename>
 - Import library to link your program to libpq.dll
</Para>
</ListItem>

<ListItem>
<Para>
<filename>interfaces\libpq\Release\libpq.lib</filename> - Static library version of the frontend library
</Para>
</ListItem>

<ListItem>
<Para>
<filename>bin\psql\Release\psql.exe</filename> - The <ProductName>Postgresql</ProductName> interactive SQL monitor
</Para>
</ListItem>

</ItemizedList>
</Para>

</Sect1>

<Sect1>
<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>
<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
Local variables:
mode: sgml
sgml-omittag:t
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:
-->

--------------C831A728C21585D3CD8B8CB0--