Personal tools

Windows

From HaskellWiki

(Difference between revisions)
Jump to: navigation, search
m
(Added a tip about -optl-mwindows; moved the Unix to DOS conversion to the tips and tricks section)
Line 15: Line 15:
 
* [[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
   
 
== Tools for compilation ==
 
== Tools for compilation ==
Line 24: Line 24:
   
 
* 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]]
 
The following two items are somewhat spurious, this is not strictly necessary, it only causes issue if file IO is done in textmode rather than binary, since the whole business of line endings stems from this.
 
 
* Source files from Unix(-like) systems have lines terminated with Line Feed only; to convert them to MS-DOS format, use 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>
 
 
* 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, 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.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/gnu-binutils/dlltool.html the dlltool manual] and [http://www.willus.com/mingw/yongweiwu_stdcall.html Stdcall and DLL tools of MSVC and MinGW]
 
* To work with/produce DLL files, 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.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/gnu-binutils/dlltool.html the dlltool manual] and [http://www.willus.com/mingw/yongweiwu_stdcall.html Stdcall and DLL tools of MSVC and MinGW]
Line 61: Line 53:
   
 
* 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. Eg, 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.
 
* 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. Eg, 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 <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.
  +
  +
* 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.
  +
  +
   
 
== Direct downloads ==
 
== Direct downloads ==

Revision as of 17:05, 5 December 2010

Contents

1 Editors

2 Compilers/interpreters

3 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 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. In case C++ software must be compiled, define CPLUS_INCLUDE_PATH to list the directories with C++ header files.

4 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 darcs repo
  • winerror: Error handling for foreign calls to the Windows API


5 Special tips and tricks for Windows

  • GHCi: Using GHCi from a Win32 console is not everyones cup of tea. Using it from within shell mode in Emacs sucks a lot less - 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; see the reversed dependencies list. However, sometimes, the dependency changes per platform; see for example the cabal file of the directory package
  • 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. Eg, 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.


6 Direct downloads

6.1 Haskell

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 Hackage and compile.

Alex 2.0.1 (obsolete) (website) ; Cpphs 1.2 (obsolete) (website) ; Darcs 2.2.1 for Windows without Cygwin ; Darcs 2.2.0 for Windows without Cygwin, with SSH support files ; Darcs 2.2.0 for Windows with Cygwin (website) ; Drift (website) ; GHC 6.10.1 (website) ; Haddock 0.7 (obsolete) (website) ; Hat July 2006 (website) ; Happy 1.13 (obsolete) (website) ; Hoogle June 2006 (obsolete) (website) ; HsColour 1.9 (website) ; Lambda Shell 0.3 (obsolete) (website) ; WinHugs September 2006 (website) ; cURL 7.19.4 (website) ;


6.2 Development

CVS 1.11.22 (website)  ; Python 2.4.3 (website)  ; Scons (website)  ; SVN 1.3.2 (website)  ; TextPad 4.7.3 (website)

7 Shipping Installable Applications

* bamse lets you build windows installers for your Haskell app (MSI).