[HACKERS] windows build docs
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 productnameCygwin/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. ! productnameCygwin/productname is not recommended and should ! only be used for older versions of productnameWindows/productname where the native build does not work, such as ! productnameWindows 98/productname. productnameMinGW/productname is ! only recommended if you are building other modules using it. The official binaries are built using productnameVisual Studio/productname. /para sect1 id=install-windows-full titleBuilding with productnameVisual C++/productname or the productnamePlatform SDK/productname/title --- 47,72 productnameCygwin/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 ! productnameMingw64/productname. These tools can also be used to ! cross-compile for 32 bit and 64 bit productnameWindows/productname ! targets on other hosts, such as productnameLinux/productname and ! productnameDarwin/productname. ! productnameCygwin/productname is not recommended for running a ! production server, and it should only be used for running on ! older versions of productnameWindows/productname where the native build does not work, such as ! productnameWindows 98/productname. The official binaries are built using productnameVisual Studio/productname. /para + para + Native builds of applicationpsql/application don't support command + line editing. The productnameCygwin/productname build does support + command line editing, so it should be used where psql is needed for + interactive use on productnameWindows/productname. + /para + sect1 id=install-windows-full titleBuilding with productnameVisual C++/productname or the productnamePlatform 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 envarPATH/envar, and run + commandconfigure/command with the + command--host=x86_64-w64-mingw/command option. +/para + +para After you have everything installed, it is suggested that you run applicationpsql/application under commandCMD.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
Re: [HACKERS] windows build docs
On Mon, Jan 31, 2011 at 18:14, Andrew Dunstan and...@dunslane.net wrote: 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. Agreed, and looks good to me. Do you know if cygwin psql works in non-US locales these days? It used to be that it didn't, and if we recommend it we should probably include a notice if it doesn't. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] windows build docs
On 01/31/2011 12:17 PM, Magnus Hagander wrote: On Mon, Jan 31, 2011 at 18:14, Andrew Dunstanand...@dunslane.net wrote: 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. Agreed, and looks good to me. Do you know if cygwin psql works in non-US locales these days? It used to be that it didn't, and if we recommend it we should probably include a notice if it doesn't. I just tested by setting my machine to fr_FR, and also setting LANG=fr_FR.utf8 under Cygwin. The build failed. The I set Cygwin back to LANG=C.utf8 and the build/install succeeded. After that, I switched back to LANG=fr_FR.utf8, and initdb, pg_ctl start and psql all behaved as expected. I'm adding a note accordingly. Some day I'll try to work out why the build went boom, but now I need to move on to other things. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] windows build docs
On Mon, Jan 31, 2011 at 19:34, Andrew Dunstan and...@dunslane.net wrote: On 01/31/2011 12:17 PM, Magnus Hagander wrote: On Mon, Jan 31, 2011 at 18:14, Andrew Dunstanand...@dunslane.net wrote: 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. Agreed, and looks good to me. Do you know if cygwin psql works in non-US locales these days? It used to be that it didn't, and if we recommend it we should probably include a notice if it doesn't. I just tested by setting my machine to fr_FR, and also setting LANG=fr_FR.utf8 under Cygwin. The build failed. The I set Cygwin back to LANG=C.utf8 and the build/install succeeded. After that, I switched back to LANG=fr_FR.utf8, and initdb, pg_ctl start and psql all behaved as expected. I'm adding a note accordingly. Some day I'll try to work out why the build went boom, but now I need to move on to other things. The thing that *didn't* work for me previously was running it with *windows* in a different locale. Meaning setting regional settings in the control panel to something like, say, Swedish :-) Or for that matter, french. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] windows build docs
On 01/31/2011 01:51 PM, Magnus Hagander wrote: I just tested by setting my machine to fr_FR, and also setting LANG=fr_FR.utf8 under Cygwin. The build failed. The I set Cygwin back to LANG=C.utf8 and the build/install succeeded. After that, I switched back to LANG=fr_FR.utf8, and initdb, pg_ctl start and psql all behaved as expected. I'm adding a note accordingly. Some day I'll try to work out why the build went boom, but now I need to move on to other things. The thing that *didn't* work for me previously was running it with *windows* in a different locale. Meaning setting regional settings in the control panel to something like, say, Swedish :-) Or for that matter, french. Oh. Well, that worked fine for me just now. Maybe it's been fixed. cheers andrew -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] windows build docs
I just tested by setting my machine to fr_FR, and also setting LANG=fr_FR.utf8 under Cygwin. The build failed. The I set Cygwin back to LANG=C.utf8 and the build/install succeeded. After that, I switched back to LANG=fr_FR.utf8, and initdb, pg_ctl start and psql all behaved as expected. I'm adding a note accordingly. Some day I'll try to work out why the build went boom, but now I need to move on to other things. The thing that *didn't* work for me previously was running it with *windows* in a different locale. Meaning setting regional settings in the control panel to something like, say, Swedish :-) Or for that matter, french. Oh. Well, that worked fine for me just now. Maybe it's been fixed. Great. Doesn't surprise me if it is, it was years ago... -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
