From 0f11ab8eb8a711c1ad158b1eec7f02d23b8ed68f Mon Sep 17 00:00:00 2001 From: rrt Date: Fri, 19 Oct 2001 11:16:16 +0000 Subject: [PATCH] [project @ 2001-10-19 11:16:16 by rrt] Say a bit about the way InstallShield should work. It doesn't yet, as I have to finish fixing make install for Windows. --- docs/building/building.sgml | 43 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) diff --git a/docs/building/building.sgml b/docs/building/building.sgml index cdca92c..8905478 100644 --- a/docs/building/building.sgml +++ b/docs/building/building.sgml @@ -2920,6 +2920,49 @@ when you install it. + + Building the Windows InstallShield® Installer + + + This section is intended for GHC developers only; no-one else + should need to build an InstallShield. + + + + Having built a second-stage tree and done make + install on it, open the InstallShield + (.ism) file. Open the Project screen, and + then the Project subfolder of the Path variables folder, and + set SourceFiles to the top of your + tree. You might also need to set GHCBITS to + point to the tree of various external bits that are added into + the IS mix. You should then be able to build an InstallShield. + + + + External add-ins + + + The external add-ins consist of Mingwin gcc and Mingwin + Perl. The layout of the add-ins tree is as follows: + + +extra-bin/ + gcc.exe + perl.exe (Mingwin perl) + perl56.dll +gcc-lib/ + Mingwin gcc binaries, libraries and headers +imports/ + com/ + imports for HDirect's com library +include/ + Mingwin includes + + + + + -- 1.7.10.4