@@ -12,6 +12,8 @@ foundation on which to base production software.
12
12
While end-users _can_ build the platform themselves, it is generally recommended,
13
13
if possible, to use the prebuilt binaries available from https://www.haskell.org/platform/
14
14
15
+ The platform distribution and tooling are more intended instead for those wishing to package a platform installer for use by others.
16
+
15
17
DISTRIBUTION
16
18
------------
17
19
The platform comes in several forms:
@@ -29,7 +31,8 @@ Development usually happens in other branches.
29
31
includes the sources of the packages that make up the platform, and excludes
30
32
some of the ancillary things in the source repo. You can use this to build
31
33
the platform without access to hackage or even an internet connection. You still
32
- need a GHC bindist.
34
+ need a GHC bindist, as well as cabal and stack binaries, either built from source or
35
+ available from their respective websites.
33
36
34
37
*installer* - For Windows and OS X, the platform is distributed as a standard
35
38
installer for the operating system. It contains a fully built version of the
@@ -55,14 +58,19 @@ You need the platform build files, either from the *source repo* or the
55
58
*source tarball*. Build instructions are the same for either.
56
59
57
60
You need a GHC bindist that matches the OS you are compiling on. It must also
58
- match the GHC version used by the platform, currently 7.10.3. You can get this
59
- from:
60
- https://www.haskell.org/ghc/download_ghc_7_10_3
61
+ match the GHC version used by the platform, which you can find by looking in the Releases*.hs files.
62
+
63
+ You can get the bindists from
64
+
65
+ https://www.haskell.org/ghc/download
61
66
62
67
The machine doing the build needs to have a working Haskell setup: Usually,
63
- GHC (7.4 or later), Cabal (1.16 or later), and haddock and HsColour must be on
68
+ GHC (7.4 or later), Cabal (1.24 or later), and haddock and HsColour must be on
64
69
the $PATH.
65
70
71
+ You also need a proper version of the cabal and stack binaries to be bundled.
72
+
73
+ You can build a cabal directly from hackage and get a stack from http://docs.haskellstack.org
66
74
67
75
BUILDING
68
76
--------
@@ -73,20 +81,24 @@ installer packages.
73
81
74
82
In either the source repo or unpacked source tarball, simply run this:
75
83
76
- ./platform.sh $PATH_TO_GHC_BINDIST_TARBALL
84
+ ./platform.sh $PATH_TO_GHC_BINDIST_TARBALL $PATH_TO_CABAL_EXECUTABLE $PATH_TO_STACK_EXECUTABLE
77
85
78
86
This will build the hptool itself, and then use that tool to build first the
79
87
platform source tarball, and finally the hermetic build of all the platform
80
88
packages.
81
89
90
+ By default this now builds a "minimal" installer that does not install libraries beyond core. To
91
+ build a "full" installer with a broader range of libraries pre-installed in the global store, pass
92
+ a "-f" option.
93
+
82
94
If you are building for a Posix like system (Linux, or BSD), then you can add
83
95
the command line option --prefix to specify where, on the target system the
84
96
tree of built things will be placed. It defaults to "/usr/local/haskell". The
85
97
build will include another directory under that named "ghc-x.y.z-arch" and
86
98
everything will be installed under there.
87
99
88
- Adding -j<n> (no space between the j and the number of cores) to the build invocation will enable building on multiple cores at
89
- once.
100
+ Adding -j<n> (no space between the j and the number of cores) to the build invocation
101
+ will enable building on multiple cores at once.
90
102
91
103
92
104
INSTALLATION
0 commit comments