This is the InstallShield setup for GHC; it can be used as a model for other
-IS setups. I've put it in a zip file because CVS doesn't like file names and
-directory names with spaces in.
+IS setups.
Notes:
-1. This IS setup is for the free (ha!) version of IS, such as the one that
-comes with MS Visual Studio. The GHC team is hoping to get hold of the full
-version, so we might well update this setup in the future to be simpler and
-better, but also not usable with the cut-down IS any more.
+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
projects / ghc-hetmet.git / blobdiff