Commit 8c0f8917 authored by rrt's avatar rrt
Browse files

[project @ 2001-06-06 10:44:26 by rrt]

Update with more instructions on getting the IS setup working and notes on
why some of the less obvious binaries are included in the Windows dist.
parent a103f9f3
......@@ -3,9 +3,28 @@ IS setups.
Notes:
1. This IS setup is for the full version of IS, *not* the one that comes
with MS Visual Studio.
1. This IS setup is for the full version of IS, *not* the one that
comes with MS Visual Studio.
2. This directory is liable to change/expansion/removal as we get IS
projects for all the major fptools bits together and add them to the
repository.
2. Merely checking out this tree will not give you a functioning IS
setup, unfortunately. This is because there are various empty
directories (which CVS doesn't like). I've not done the usual trick
of putting spurious files in them in case InstallShield takes
exception to that.
3. The InstallShield script generates some files entirely by
itself. These are:
a. the specs file for gcc
b. the "front-end" to autoconf (so that it can find its library
files).
It might be useful to record for posterity why some of the less
obvious binaries are in ghc/extra-bin:
uname: for config.guess (used in gmp's configure script)
basename: to find the basename of binaries such as gzip in the main
configure script
uniq: somewhere...
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment