Following recent discussions and the enabling of 64 bit Mingw builds, I
propose to make the attached changes to the docs. I don't see any great
reason for us to advise against building with Mingw, especially now that
we have 64 bit support for it, so I removed that, amd also clarified
where Cygwin is useful and where it's not, as well as adding some detail
about how to make 64 bit builds.
cheers
andrew
*** a/doc/src/sgml/install-windows.sgml
--- b/doc/src/sgml/install-windows.sgml
***************
*** 47,61 ****
<productname>Cygwin</productname> uses the normal build system, see
<xref linkend="installation"> and the specific notes in
<xref linkend="installation-notes-mingw"> and <xref linkend="installation-notes-cygwin">.
! These builds cannot generate 64-bit binaries.
! <productname>Cygwin</productname> is not recommended and should
! only be used for older versions of <productname>Windows</productname> where
the native build does not work, such as
! <productname>Windows 98</productname>. <productname>MinGW</productname> is
! only recommended if you are building other modules using it. The official
binaries are built using <productname>Visual Studio</productname>.
</para>
<sect1 id="install-windows-full">
<title>Building with <productname>Visual C++</productname> or the
<productname>Platform SDK</productname></title>
--- 47,72 ----
<productname>Cygwin</productname> uses the normal build system, see
<xref linkend="installation"> and the specific notes in
<xref linkend="installation-notes-mingw"> and <xref linkend="installation-notes-cygwin">.
! To produce native 64 bit binaries in these environments, use the tools from
! <productname>Mingw64</productname>. These tools can also be used to
! cross-compile for 32 bit and 64 bit <productname>Windows</productname>
! targets on other hosts, such as <productname>Linux</productname> and
! <productname>Darwin</productname>.
! <productname>Cygwin</productname> is not recommended for running a
! production server, and it should only be used for running on
! older versions of <productname>Windows</productname> where
the native build does not work, such as
! <productname>Windows 98</productname>. The official
binaries are built using <productname>Visual Studio</productname>.
</para>
+ <para>
+ Native builds of <application>psql</application> don't support command
+ line editing. The <productname>Cygwin</productname> build does support
+ command line editing, so it should be used where psql is needed for
+ interactive use on <productname>Windows</productname>.
+ </para>
+
<sect1 id="install-windows-full">
<title>Building with <productname>Visual C++</productname> or the
<productname>Platform SDK</productname></title>
*** a/doc/src/sgml/installation.sgml
--- b/doc/src/sgml/installation.sgml
***************
*** 2733,2738 **** cc-1020 cc: ERROR File = pqcomm.c, Line = 427
--- 2733,2746 ----
</para>
<para>
+ To build 64 bit binaries using MinGW, install the 64 bit tool set
+ from <ulink url="http://www.mingw64.org/";></ulink>, put its bin
+ directory in the <envar>PATH</envar>, and run
+ <command>configure</command> with the
+ <command>--host=x86_64-w64-mingw</command> option.
+ </para>
+
+ <para>
After you have everything installed, it is suggested that you
run <application>psql</application>
under <command>CMD.EXE</command>, as the MSYS console has
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
