What tool versions (MinGW, MSYS, automake,
etc.) do I need to build GHC on Windows?
simonpj at microsoft.com
Fri Sep 8 03:35:31 EDT 2006
I think that’d be a great idea, thank you!
I do recommend using MSYS as the environment, though. I find that GHC builds much, much faster using MSYS than using Cygwin.
From: cvs-all-bounces at haskell.org [mailto:cvs-all-bounces at haskell.org] On Behalf Of Brian Smith
Sent: 07 September 2006 23:29
To: cvs-ghc at haskell.org
Subject: What tool versions (MinGW, MSYS, automake,etc.) do I need to build GHC on Windows?
Is there some documentation available that lists the versions of tools that are used to build the official Windows distributions of GHC? In particular, what versions of MinGW, MSYSDTK, automake, autoconf, and binutils are used?
I would like to put together a package that Windows users can download to jump into GHC development easier. I am motivated to do so because I spent hours last year to configure my system to build GHC/Windows, and now I am about to repeat that tiresome process.
My goal is to produce a ZIP file that contains all the correct versions of all the tools needed, plus a script that sets up the build environment (unsets CYGWIN, sets the path, etc.) and leaves the user in the MSYS bash shell.
Basically, I want the process for building on GHC to become:
(1) Download ghc-build-tools.zip
(2) Extract ghc-build-tools.zip to C:\ghc-build-tools\
(3) Execute C:\ghc-build-tools\ghc-build-shell.bat
Inside the resultant shell, we would then do:
darcs get --partial http://darcs.haskell.org/ghc
chmod +x darcs-all
Furthermore, I would like to create a VMWare image that Windows users can use to test their changes on Linux.
Besides GHC, I would like to do the same thing for Darcs as well. Hopefully, Darcs and GHC can use the same versions of the same tools so that seperate packages aren't necessary.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cvs-ghc