<para>
<screen>
% cd /your/scratch/space
-% bunnzip2 < ghc-<replaceable>version</replaceable>-<replaceable>platform</replaceable>.tar.bz2 | tar xvf -</screen>
+% bunzip2 < ghc-<replaceable>version</replaceable>-<replaceable>platform</replaceable>.tar.bz2 | tar xvf -</screen>
</para>
<para>
<listitem><para>Run the installer.
On Windows, all of GHC's files are installed in a single directory.
You can override it, but by default this directory is
-<filename>c:/ghc/<replaceable>ghc-version</replaceable></filename>.
+<filename>c:/ghc/ghc-<replaceable>version</replaceable></filename>.
The executable binary for GHC will be installed in the
<filename>bin/</filename> sub-directory of the installation directory.
If you want to invoke GHC from a command line, add this
<para>
When installation is complete, you should find GHCi and the GHC
documentation are available in your Start menu under
-"Start/All Programs/GHC/<replaceable>ghc-version</replaceable>".
+"Start/All Programs/GHC/ghc-<replaceable>version</replaceable>".
</para>
</listitem>
It uses the standard Windows procedure <literal>GetTempPath()</literal> to
find a suitable directory. This procedure returns:
<itemizedlist>
-<listitem><para>The path in environment variable TMP,
+<listitem><para>The path in the environment variable TMP,
if TMP is set.</para></listitem>
-<listitem><para>Otherwise, the path in environment variable TEMP,
+<listitem><para>Otherwise, the path in the environment variable TEMP,
if TEMP is set.</para></listitem>
<listitem><para>Otherwise, there is a per-user default which varies
between versions of Windows. On NT and XP-ish versions, it might
be:
-<filename>c:\Documents and Settings\<username>\Local Settings\Temp</filename>
+<filename>c:\Documents and Settings\<username>\Local Settings\Temp</filename>.
</para></listitem>
</itemizedlist>
-The main point is that if you don't do anything GHC will work fine;
+The main point is that if you don't do anything GHC will work fine,
but if you want to control where the directory is, you can do so by
setting TMP or TEMP.
</para></listitem>
else, to install and run GHC.
</para>
<para>
-An installation of GHC requires about 340M of disk space.
+An installation of GHC requires about 365M of disk space.
To run GHC comfortably, your machine should have at least
64M of memory.
</para>
<sect2><title>Moving GHC around</title>
<para>
Once GHC is installed, you can freely move the entire GHC tree just by copying
-the <filename>c:/ghc/<replaceable>ghc-version</replaceable></filename>
+the <filename>c:/ghc/ghc-<replaceable>version</replaceable></filename>
directory. (You will need to fix up
-the links in "Start/All Programs/GHC/<replaceable>ghc-version</replaceable>"
+the links in "Start/All Programs/GHC/ghc-<replaceable>version</replaceable>"
if you do this.)
</para>
<para>
It is OK to put GHC tree in a directory whose path involves spaces. However,
don't do this if you use want to use GHC with the Cygwin tools,
because Cygwin can get confused when this happens.
-We havn't quite got to the bottom of this, but so far as we know it's not
+We haven't quite got to the bottom of this, but so far as we know it's not
a problem with GHC itself. Nevertheless, just to keep life simple we usually
put GHC in a place with a space-free path.
</para>
<para>The layout of the library directory, <filename>$(libdir)</filename>,
is almost identical on
Windows and Unix, as follows. Differences between Windows and Unix
-are annoted <literal>[Win32 only]</literal> and are commented below.</para>
+are annotated <literal>[Win32 only]</literal> and are commented below.</para>
<programlisting>
$(libdir)/
package.conf GHC package configuration
ghc-usage.txt Message displayed by ghc ––help
+ ghci-usage.txt Message displayed by ghci ––help
bin/ [Win32 only] User-visible binaries
- ghc.exe
- ghci.exe
+ ghc.exe
+ ghci.exe
unlit Remove literate markup
ghc-x.xx GHC executable [Unix only]
ghc-split Asm code splitter
- ghc-asm Asm code mangler
+ ghc-asm Asm code mangler
gcc-lib/ [Win32 only] Support files for gcc
specs gcc configuration
ld.exe
crt0.o Standard
- ..etc.. binaries
+ ..etc.. binaries
libmingw32.a Standard
- ..etc.. libraries
+ ..etc.. libraries
*.h Include files
- imports/ GHC interface files
- std/*.hi 'std' library
- lang/*.hi 'lang' library
- ..etc..
+ hslibs-imports/ GHC interface files for the...
+ ghc/*.hi ...'ghc' library
include/ C header files
StgMacros.h GHC-specific
- ..etc... header files
+ ..etc.. header files
mingw/*.h [Win32 only] Mingwin header files
- libHSrts.a GHC library archives
- libHSstd.a
- libHSlang.a
- ..etc..
+ lib/ GHC's library
+ base-2.1
+ ..etc..
+
+ libHSrts*.a GHC RTS archive
+ libHSghc.a GHC package archive
- HSstd1.o GHC library linkables
- HSstd2.o (used by ghci, which does
- HSlang.o not grok .a files yet)
+ HSrts.o GHC RTS linkable, used by ghci
+ HSghc.o GHC package linkable, used by ghci
</programlisting>
<para>Note that:
<listitem>
<para><filename>$(libdir)</filename> also contains support
binaries. These are <emphasis>not</emphasis> expected to be
- on the user's <filename>PATH</filename>, but and are invoked
+ on the user's <filename>PATH</filename>, but are invoked
directly by GHC. In the Makefile system, this directory is
also called <filename>$(libexecdir)</filename>, but
<emphasis>you are not free to change it</emphasis>. It must
<listitem>
<para>The support programs <filename>ghc-split</filename>
and <filename>ghc-asm</filename> are Perl scripts. The
- first line says <literal>#!/bin/perl</literal>; on Unix, the
+ first line says <literal>#!/usr/bin/perl</literal>; on Unix, the
script is indeed invoked as a shell script, which invokes
Perl; on Windows, GHC invokes
<filename>$(libdir)/perl.exe</filename> directly, which
- treats the <literal>#!/bin/perl</literal> as a comment.
+ treats the <literal>#!/usr/bin/perl</literal> as a comment.
Reason: on Windows we want to invoke the Perl distributed
with GHC, rather than assume some installed one. </para>
</listitem>
projects / ghc-hetmet.git / blobdiff