Personal tools

Windows

From HaskellWiki

(Difference between revisions)
Jump to: navigation, search
(Added WinGhci)
(Quickstart on Windows 7)
(41 intermediate revisions by 8 users not shown)
Line 1: Line 1:
GHC is well supported on Windows.
+
== Quickstart on Windows 7 ==
   
* [http://haskell.org/ghc/download_ghc_6_10_1.html#binaries Download GHC for Windows]
+
This page describes what you need to know to ''use'' Haskell on a Windows machine.
  +
See [https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows the GHC Trac Wiki] for what you need to know to ''build'' GHC on Windows.
   
  +
For a minimal setup download the following :
  +
  +
* [http://sourceforge.net/projects/msys2/ MSYS2] binaries
  +
* [http://www.haskell.org/ghc/download ghc] binaries
  +
* [http://www.haskell.org/cabal/download.html cabal] binaries
  +
  +
Add the following to the path :
  +
  +
* <hask>ghc/bin</hask> (should contain <hask>ghc.exe</hask> etc)
  +
* <hask>ghc/mingw/bin</hask> (should contain <hask>gcc.exe</hask> etc)
  +
* <hask>cabal/</hask> (should contain the cabal binary)
  +
  +
If you launch <hask>msys2_shell.bat</hask> (as opposed to <hask>mingw32_shell.bat</hask> or <hask>mingw64_shell.bat</hask>) then make sure that the following environment variable is defined :
  +
  +
* <hask>MSYSTEM=MINGW32</hask> or <hask>MSYSTEM=MINGW64</hask>
  +
  +
Then test by firing up either <hask>msys2_shell.bat</hask>, <hask>mingw32_shell.bat</hask>, or <hask>mingw64_shell.bat</hask> and then executing the following sequence of commands :
  +
  +
* <hask>
  +
mkdir test
  +
cd test
  +
cabal sandbox init
  +
cabal install hoogle
  +
</hask>
  +
  +
Note that the absence of the environment variables above will result in linker errors when building hoogle.
   
 
== Editors ==
 
== Editors ==
Line 8: Line 34:
 
* [http://www.e-texteditor.com/ E-Text Editor (TextMate for Windows)]
 
* [http://www.e-texteditor.com/ E-Text Editor (TextMate for Windows)]
 
* [http://www.textpad.com/ TextPad]
 
* [http://www.textpad.com/ TextPad]
* Emacs, Vi(m), etc
+
* [http://ftp.gnu.org/gnu/emacs/windows/ Emacs], [http://www.vim.org/ Vi(m)], etc
* [http://www.haskell.org/visualhaskell/ Visual Haskell]
+
* [http://www.leksah.org/index.html Leksah]: Haskell IDE written in Haskell
 
* [http://eclipsefp.sourceforge.net/ Eclipse]
 
* [http://eclipsefp.sourceforge.net/ Eclipse]
* [http://notepad-plus.sourceforge.net Notepad++]
+
* [http://notepad-plus-plus.org/ Notepad++]
+
* [http://www.sublimetext.com/ Sublime Text]
  +
* [http://www.pnotepad.org/ Programmer's Notepad]
   
 
== Compilers/interpreters ==
 
== Compilers/interpreters ==
   
  +
* [http://www.haskell.org/platform/ The Haskell Platform] is a combination of GHC and a set of blessed libraries
 
* [[WinHugs]]
 
* [[WinHugs]]
 
* [[GHC]]: Special notes for Cygwin users - [http://www.haskell.org/ghc/docs/6.6/html/building/platforms.html] [http://www.haskell.org/ghc/docs/latest/html/users_guide/ghci-cygwin.html]
 
* [[GHC]]: Special notes for Cygwin users - [http://www.haskell.org/ghc/docs/6.6/html/building/platforms.html] [http://www.haskell.org/ghc/docs/latest/html/users_guide/ghci-cygwin.html]
* [http://code.google.com/p/winghci/ WinGhci] A GUI for GHCi
+
* [http://code.google.com/p/winghci/ WinGhci], a GUI for GHCi (included in the Haskell Platform)
   
 
== Tools for compilation ==
 
== Tools for compilation ==
   
* As some of the packages contain Unix/Linux specific scripts/commands, you need [http://www.mingw.org/ MingW] and [http://www.mingw.org/wiki/msys MSYS] to simulate a Unix environment. In some cases you need [http://www.cygwin.com/ Cygwin] instead.
+
* As some of the packages contain Unix/Linux specific scripts/commands, you need [http://www.mingw.org/ MinGW] and [http://www.mingw.org/wiki/msys MSYS] to simulate a Unix environment. In some cases you need [http://www.cygwin.com/ Cygwin] instead. If you use [http://code.google.com/p/msysgit/ msysgit] on Windows already, all you need to do is add MinGW to your path.
   
* If you need to link to C-software, define an environment variable C_INCLUDE_PATH that lists the directories where the header files can be found. For linking the libraries you need to define an environment variable LIBRARY_PATH as well, listing the directories where .a and .lib files can be found.
+
* If you need to link to C-software, [http://en.wikipedia.org/wiki/Environment_variable#DOS.2C_OS.2F2_and_Windows_.28Command_Prompt.29 define environment variable] C_INCLUDE_PATH that lists the directories where the header files can be found, for example:
  +
Set C_INCLUDE_PATH=C:\usr\local\include;C:\usr\local\include\SDL
  +
:(It is advisable to use paths without spaces, because some scripts in the MinGW/MSYS environment have problems with spaces in paths.)<br>
  +
:For linking the libraries, you need to define environment variable LIBRARY_PATH as well, listing the directories where .a and .lib files can be found. In case C++ software must be compiled, define CPLUS_INCLUDE_PATH to list the directories with C++ header files.
   
* Packages are often delivered as a .tar or .tar.gz file, see [[How to unpack a tar file in windows]]
+
* Packages are often delivered as a .tar or .tar.gz file, see [[How to unpack a tar file in Windows]]
 
* Source files from Unix(-like) systems have lines terminated with Line Feed only; to convert them to MS-DOS format (as needed by Windows), use the <code>unix2dos</code> command (included in MSYS). For more information, give command: <code>unix2dos --help</code>
 
 
* To convert a set of files to MS-DOS format (note: this might damage binary files):
 
::<code>C:\MSYS\1.0\bin\find . -type f -exec unix2dos {} ;</code>
 
:Note: the <code>find</code> command included in MSYS is different from the MS-DOS <code>find</code> command, therefore, you need to specify the entire path to this command.
 
   
  +
* To work with/produce DLL files with GHC < 7.0.1, you need dlltool.exe, from the [http://sourceforge.net/projects/mingw/files/ mingw-binutils] package and pexports.exe from the [http://sourceforge.net/projects/mingw/files/ mingw-utils] package. For more information see [http://www.cse.yorku.ca/tdb/_doc.php/userg/man/name/dlltool/section/1 the dlltool manual] and [http://www.willus.com/mingw/yongweiwu_stdcall.html Stdcall and DLL tools of MSVC and MinGW]
  +
: If you have GHC >= 7.0.1, see [http://www.haskell.org/ghc/docs/latest/html/users_guide/using-shared-libs.html Using shared libraries] or [http://www.haskell.org/ghc/docs/latest/html/users_guide/win32-dlls.html Building and using Win32 DLLs]
   
 
== Libraries ==
 
== Libraries ==
   
* GUI : [[wxHaskell]] - A binding of wxWidgets (formerly known as wxWindows) in Haskell. Note, see also [[wxHaskell/Building]]
+
* GUI : [[wxHaskell]] - A binding of wxWidgets (formerly known as wxWindows) in Haskell. Note: see also [[wxHaskell/Windows]]
   
* GUI : [[Gtk2Hs]] - A binding of GTK in Haskell. Note this requires installing [http://www.gtk.org GTK] on windows.
+
* GUI : [[Gtk2Hs]] - A binding of GTK+ in Haskell. Note: this requires installing [http://www.gtk.org GTK+] on windows.
   
* [http://hackage.haskell.org/cgi-bin/hackage-scripts/package/Win32 Win32] - low levelish bindings to Windows API. Comes with ghc and non-minimal hugs distribution. [http://darcs.haskell.org/ Win32 darcs repo]
+
* [http://hackage.haskell.org/cgi-bin/hackage-scripts/package/Win32 Win32] - low levelish bindings to Windows API. Comes with GHC and non-minimal Hugs distribution. [https://github.com/haskell/win32 Win32 git repo]
   
 
* [[HDBC-ODBC under Windows]] for database access.
 
* [[HDBC-ODBC under Windows]] for database access.
   
 
* [http://hackage.haskell.org/cgi-bin/hackage-scripts/package/winerror winerror]: Error handling for foreign calls to the Windows API
 
* [http://hackage.haskell.org/cgi-bin/hackage-scripts/package/winerror winerror]: Error handling for foreign calls to the Windows API
 
   
 
== Special tips and tricks for Windows ==
 
== Special tips and tricks for Windows ==
   
* darcs : http://wiki.darcs.net/index.html/WindowsConfiguration
+
* If there are DLLs missing from your environment, you can find out which, using [http://cygwin.com/cygwin-ug-net/using-utils.html cygcheck] from the [http://www.cygwin.com/ Cygwin project]. Note, that you will get problems if you have both MinGW and Cygwin in your search path; it is best to specify the full path to cygcheck.exe, or copy cygcheck.exe to some location in the search path.
  +
: Another option is [http://www.dependencywalker.com/ Dependency Walker]; this tool can also be used to find out, in which DLL a crash occurs.
  +
  +
* [http://www.haskell.org/pipermail/haskell-cafe/2013-February/106436.html Terminal Win32/Building Haskeline/8.3 file issue] (Haskell-cafe)
  +
  +
* darcs : http://wiki.darcs.net/WindowsConfiguration
   
 
* Make sure your Haskell compiler (e.g. GHC) and tools are on your system path: http://www.computerhope.com/issues/ch000549.htm
 
* Make sure your Haskell compiler (e.g. GHC) and tools are on your system path: http://www.computerhope.com/issues/ch000549.htm
   
* GHCi: Using GHCi from a DOS box sucks. Using it from withing shell mode in Emacs sucks a lot less - do 'M-x shell' in emacs, then type 'ghci'.
+
* Instead of using WinGHCi, one can also run GHCi in shell mode in Emacs &mdash; do 'M-x shell' in Emacs, then type 'ghci'.
   
* GHCi on Cygwin: When running GHC under a Cygwin shell on Windows, Ctrl-C sometimes doesn't work. A workaround is to use the rlwrap program to invoke ghci : In addition to proper Ctrl-C, you also get emacs (or vi) key bindings and command history across sessions, which saves you a load of typing.
+
* GHCi on Cygwin: When running GHC under a Cygwin shell on Windows, Ctrl-C sometimes doesn't work. A workaround is to use the rlwrap program to invoke GHCi : In addition to proper Ctrl-C, you also get Emacs (or vi) key bindings and command history across sessions, which saves you a load of typing.
   
* If a package depends (either directly or indirectly) on the <code>unix</code> package, you cannot compile it on Windows
+
* If a package depends (either directly or indirectly) on the <code>unix</code> package, you cannot compile it on Windows.
  +
:A simple way to see, if a package X depends on <code>unix</code>, is giving the command:
  +
cabal install X --dry-run
  +
:This will list all packages that would be installed
   
  +
* If you are missing or need to distribute libraries with an application, the correct place to put them is *NOT* in \WINDOWS\System32 as once was the practice in the early days of Windows. All sane applications/installers keep their own private dependencies in the application directory. E.g., if the user has chosen to install your application to C:\Program Files\Foo then it is best to install any DLLs in the same location.
   
== Direct downloads ==
+
* When compiling a program with GUI, use the compiler option -optl-mwindows to prevent a DOS-shell being displayed behind your GUI. (This passes the option -mwindows to the linker.)
   
=== Haskell ===
+
* Source files from Unix(-like) systems have lines terminated with Line Feed only; if your favorite editor cannot handle this, you can convert the files to MS-DOS format with the <code>unix2dos</code> command (from the [http://sourceforge.net/projects/mingw/files/ mingw-utils] package). For more information, give command: <code>unix2dos --help</code>
  +
:Note, that GHC can handle source files in Unix format.
   
Below a list of binary packages packages for Windows. To be sure you get the last version of each, it is best to download the source from [http://hackage.haskell.org/packages/archive/pkg-list.html Hackage] and compile.
+
* To convert a set of files to MS-DOS format (note: this might damage binary files):
  +
::<code>C:\MSYS\1.0\bin\find . -type f -exec unix2dos {} ;</code>
  +
:Note: the <code>find</code> command included in MSYS is different from the MS-DOS <code>find</code> command, therefore, you need to specify the entire path to this command.
  +
  +
== Binary downloads ==
  +
  +
=== Haskell ===
   
[http://www.haskell.org/alex/dist/alex-2.0.1-win32.zip Alex 2.0.1] (obsolete) [http://www.haskell.org/haskellwiki/Alex (website)] ;
+
Below a list of binary packages for Windows. To be sure you get the most recent version of each, it is best to download the source from [http://hackage.haskell.org/packages/archive/pkg-list.html Hackage] and compile (except for the Haskell Platform).
[http://www.cs.york.ac.uk/fp/cpphs-1.2-win32.zip Cpphs 1.2] (obsolete) [http://haskell.org/cpphs/ (website)] ;
 
[http://homepage.mac.com/kirby81_it/darcs/darcs-2.2.1-win1.zip Darcs 2.2.1 for Windows without Cygwin] ;
 
[http://testgrid.allmydata.org:3567/uri/URI:DIR2-RO:bminllzdrpadzvyt54cbhotnam:jqafknaedfksjjq3xmkfpe4g4ppklctw3xwpszufol7zddyx5agq/darcsdir-w32-2.2.0.zip Darcs 2.2.0 for Windows without Cygwin, with SSH support files] ;
 
[http://testgrid.allmydata.org:3567/uri/URI:DIR2-RO:bminllzdrpadzvyt54cbhotnam:jqafknaedfksjjq3xmkfpe4g4ppklctw3xwpszufol7zddyx5agq/darcsdir-cygwin-2.2.0.tar.bz2 Darcs 2.2.0 for Windows with Cygwin] [http://darcs.net/ (website)] ;
 
[http://repetae.net/computer/haskell/DrIFT/drop/ Drift] [http://repetae.net/john/computer/haskell/DrIFT/ (website)] ;
 
[http://haskell.org/ghc/dist/6.10.1/ghc-6.10.1-i386-windows.exe GHC 6.10.1]
 
[http://haskell.org/ghc/ (website)] ;
 
[http://haskell.org/haddock/haddock-0.7-Win32.zip Haddock 0.7] (obsolete) [http://haskell.org/haddock/ (website)] ;
 
[http://www.cs.york.ac.uk/fp/temp/hat-win32-05_jul_2006.zip Hat July 2006] [http://haskell.org/hat/ (website)] ;
 
[http://www.haskell.org/happy/dist/1.13/happy-1-13.msi Happy 1.13] (obsolete) [http://www.haskell.org/happy/ (website)] ;
 
[http://www.haskell.org/hoogle/other/hoogle-win32.zip Hoogle June 2006] (obsolete) [http://www.haskell.org/hoogle/ (website)] ;
 
[ftp://ftp.cs.york.ac.uk/pub/haskell/contrib/hscolour-1.9.zip HsColour 1.9] [http://www.cs.york.ac.uk/fp/darcs/hscolour/ (website)] ;
 
[http://haskell.org/hoogle/other/lambdashell-0.3.zip Lambda Shell 0.3] (obsolete) [http://www.cs.princeton.edu/~rdockins/lambda/home (website)] ;
 
[http://cvs.haskell.org/Hugs/downloads/2006-09/WinHugs-Sep2006.exe WinHugs September 2006] [http://www.haskell.org/hugs/ (website)] ;
 
[http://haskell.forkio.com/Home/curl-win32/curl-7.19.4-mingw32.zip?attredirects=0 cURL 7.19.4] [http://haskell.forkio.com/Home/curl-win32 (website)] ;
 
   
  +
* [http://www.haskell.org/platform/windows.html The Haskell Platform] [[Haskell Platform | (HaskellWiki page)]], contains GHC and a set of libraries and tools
  +
* [http://www.haskell.org/ghc/dist/7.6.3/ghc-7.6.3-i386-unknown-mingw32.tar.bz2 GHC 7.6.3 for Windows x86], [http://www.haskell.org/ghc/dist/7.6.3/ghc-7.6.3-x86_64-unknown-mingw32.tar.bz2 GHC 7.6.3 for Windows 64bit] [[GHC | (HaskellWiki page)]]
  +
* [http://leksah.org/download.html Leksah] [[Leksah | (HaskellWiki page)]]
  +
* [http://darcs.net/Binaries Darcs] [[Darcs | (HaskellWiki page)]]
  +
* [http://repetae.net/computer/haskell/DrIFT/drop/ Drift] [http://repetae.net/computer/haskell/DrIFT/ (website)]
  +
* [http://www.haskell.org/haddock/haddock-0.7-Win32.zip Haddock 0.7] (obsolete) [http://www.haskell.org/haddock/ (website)]
  +
* [http://www.haskell.org/happy/dist/1.13/happy-1-13.msi Happy 1.13] (obsolete) [http://www.haskell.org/happy/ (website)]
  +
* [ftp://ftp.cs.york.ac.uk/pub/haskell/contrib/hscolour-1.9.zip HsColour 1.9] [http://www.cs.york.ac.uk/fp/darcs/hscolour/ (website)]
  +
* [http://cvs.haskell.org/Hugs/pages/downloading.htm WinHugs September 2006] [http://www.haskell.org/hugs/ (website)]
  +
* [http://haskell.forkio.com/Home/curl-win32/curl-7.19.4-mingw32.zip?attredirects=0 cURL 7.19.4] [http://haskell.forkio.com/Home/curl-win32/ (website)]
   
 
=== Development ===
 
=== Development ===
   
[ftp://ftp.gnu.org/gnu/non-gnu/cvs/binary/stable/x86-woe/cvs-1-11-22.zip CVS 1.11.22] [http://www.nongnu.org/cvs/ (website)] ; [http://www.python.org/ftp/python/2.4.3/python-2.4.3.msi Python 2.4.3] [http://www.python.org/ (website)] ; [http://kent.dl.sourceforge.net/sourceforge/scons/scons-0.96.1.win32.exe Scons 0.96.1] [http://www.scons.org/ (website)] ; [http://subversion.tigris.org/files/documents/15/32856/svn-1.3.2-setup.exe SVN 1.3.2] [http://subversion.tigris.org/ (website)] ; [ftp://download.textpad.com/pub/textpad4.7/txpeng473.exe TextPad 4.7.3] [http://www.textpad.com/ (website)] ; [http://unxutils.sourceforge.net/UnxUtils.zip Unix Utils 14-04-03] [http://unxutils.sourceforge.net/ (website)] ;
+
[https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows Setting up a Windows system for building GHC]
   
 
== Shipping Installable Applications ==
 
== Shipping Installable Applications ==
   
* [http://hackage.haskell.org/cgi-bin/hackage-scripts/package/bamse bamse] let's you build windows installers for your Haskell app (MSI).
+
* [http://hackage.haskell.org/cgi-bin/hackage-scripts/package/bamse bamse] lets you build windows installers for your Haskell app (MSI).
  +
* [http://www.jrsoftware.org/isinfo.php Inno Setup] is another tool to create windows installers.
  +
* [http://wixtoolset.org/ WiX Toolset], builds Windows installation packages from XML source code
  +
* [http://zero-install.sourceforge.net/ Zero Install] creates packages for several platforms ("a decentralised cross-distribution software installation system")
   
 
[[Category:OS]]
 
[[Category:OS]]

Revision as of 09:17, 27 June 2014

Contents

1 Quickstart on Windows 7

This page describes what you need to know to use Haskell on a Windows machine. See the GHC Trac Wiki for what you need to know to build GHC on Windows.

For a minimal setup download the following :

Add the following to the path :

  • ghc/bin
    (should contain
    ghc.exe
    etc)
  • ghc/mingw/bin
    (should contain
    gcc.exe
    etc)
  • cabal/
    (should contain the cabal binary)
If you launch
msys2_shell.bat
(as opposed to
mingw32_shell.bat
or
mingw64_shell.bat
) then make sure that the following environment variable is defined :
  • MSYSTEM=MINGW32
    or
    MSYSTEM=MINGW64
Then test by firing up either
msys2_shell.bat
,
mingw32_shell.bat
, or
mingw64_shell.bat
and then executing the following sequence of commands :
  • mkdir test
    cd test
    cabal sandbox init
    cabal install hoogle

Note that the absence of the environment variables above will result in linker errors when building hoogle.

2 Editors

3 Compilers/interpreters

4 Tools for compilation

  • As some of the packages contain Unix/Linux specific scripts/commands, you need MinGW and MSYS to simulate a Unix environment. In some cases you need Cygwin instead. If you use msysgit on Windows already, all you need to do is add MinGW to your path.
  • If you need to link to C-software, define environment variable C_INCLUDE_PATH that lists the directories where the header files can be found, for example:
    Set C_INCLUDE_PATH=C:\usr\local\include;C:\usr\local\include\SDL
(It is advisable to use paths without spaces, because some scripts in the MinGW/MSYS environment have problems with spaces in paths.)
For linking the libraries, you need to define environment variable LIBRARY_PATH as well, listing the directories where .a and .lib files can be found. In case C++ software must be compiled, define CPLUS_INCLUDE_PATH to list the directories with C++ header files.
If you have GHC >= 7.0.1, see Using shared libraries or Building and using Win32 DLLs

5 Libraries

  • GUI : Gtk2Hs - A binding of GTK+ in Haskell. Note: this requires installing GTK+ on windows.
  • Win32 - low levelish bindings to Windows API. Comes with GHC and non-minimal Hugs distribution. Win32 git repo
  • winerror: Error handling for foreign calls to the Windows API

6 Special tips and tricks for Windows

  • If there are DLLs missing from your environment, you can find out which, using cygcheck from the Cygwin project. Note, that you will get problems if you have both MinGW and Cygwin in your search path; it is best to specify the full path to cygcheck.exe, or copy cygcheck.exe to some location in the search path.
Another option is Dependency Walker; this tool can also be used to find out, in which DLL a crash occurs.
  • Instead of using WinGHCi, one can also run GHCi in shell mode in Emacs — do 'M-x shell' in Emacs, then type 'ghci'.
  • GHCi on Cygwin: When running GHC under a Cygwin shell on Windows, Ctrl-C sometimes doesn't work. A workaround is to use the rlwrap program to invoke GHCi : In addition to proper Ctrl-C, you also get Emacs (or vi) key bindings and command history across sessions, which saves you a load of typing.
  • If a package depends (either directly or indirectly) on the unix package, you cannot compile it on Windows.
A simple way to see, if a package X depends on unix, is giving the command:
   cabal install X --dry-run
This will list all packages that would be installed
  • If you are missing or need to distribute libraries with an application, the correct place to put them is *NOT* in \WINDOWS\System32 as once was the practice in the early days of Windows. All sane applications/installers keep their own private dependencies in the application directory. E.g., if the user has chosen to install your application to C:\Program Files\Foo then it is best to install any DLLs in the same location.
  • When compiling a program with GUI, use the compiler option -optl-mwindows to prevent a DOS-shell being displayed behind your GUI. (This passes the option -mwindows to the linker.)
  • Source files from Unix(-like) systems have lines terminated with Line Feed only; if your favorite editor cannot handle this, you can convert the files to MS-DOS format with the unix2dos command (from the mingw-utils package). For more information, give command: unix2dos --help
Note, that GHC can handle source files in Unix format.
  • To convert a set of files to MS-DOS format (note: this might damage binary files):
C:\MSYS\1.0\bin\find . -type f -exec unix2dos {} ;
Note: the find command included in MSYS is different from the MS-DOS find command, therefore, you need to specify the entire path to this command.

7 Binary downloads

7.1 Haskell

Below a list of binary packages for Windows. To be sure you get the most recent version of each, it is best to download the source from Hackage and compile (except for the Haskell Platform).

7.2 Development

Setting up a Windows system for building GHC

8 Shipping Installable Applications

  • bamse lets you build windows installers for your Haskell app (MSI).
  • Inno Setup is another tool to create windows installers.
  • WiX Toolset, builds Windows installation packages from XML source code
  • Zero Install creates packages for several platforms ("a decentralised cross-distribution software installation system")