Changes between Version 12 and Version 13 of Building/Preparation/Windows/MSYS2


Ignore:
Timestamp:
Dec 9, 2013 1:07:56 PM (21 months ago)
Author:
thoughtpolice
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Building/Preparation/Windows/MSYS2

    v12 v13  
    11This page documents the instructions for setting up a Windows build using [http://sourceforge.net/projects/msys2/files/Alpha-versions/ msys2], which is a fairly complete build of MinGW + the msys tools. It is pretty self contained and fixes several pesky bugs with the traditional implementation. It's also smaller and has a convenient package manager, `pacman`.
     2
     3It should get you running in ~5 minutes, modulo download speeds.
    24
    35''NB'': You can extract `.tar.xz` files with 7Zip: http://www.7-zip.org/
     
    5961{{{
    6062$ pacman -Syu
    61 $ pacman -S git wget tar gzip binutils gcc autoconf make libtool automake xz
     63$ pacman -S git wget tar gzip binutils autoconf make libtool automake xz
    6264}}}
    6365
    64 **Do not install python!
     66**Do not install python, python2 or gcc!
     67
     68We'll use the natively-built python and our own specific version of GCC on windows.
    6569
    6670Now install a `cabal.exe` prebuilt binary, and install `alex` and `happy`:
     
    8993''Yes! Parallel make works!
    9094
    91 == Running the testsuite ==
    92 
    93 To run the testsuite, a gross hack is currently needed in order to set the proper `gcc` for building an executable.
    94 
    95 First, with a built tree, go to the root of the tree. Then say:
    96 
    97 {{{
    98 $ export PATH=/path/to/ghc/source/inplace/mingw/bin:$PATH
    99 }}}
    100 
    101 This puts the inplace-mingw in your `$PATH` ahead of the msys2 tools. Now you can just say:
    102 
    103 {{{
    104 $ cd testsuite
    105 $ make
    106 }}}
    107 
    108 to run the tests.
     95Or just `CPUS=4 sh ./validate` works too. The testsuite works as you expect.