Commit b8f54bae authored by Ian Lynagh's avatar Ian Lynagh
Browse files

Remove outdated bundle-contents description

parent ef2c1a66
......@@ -67,138 +67,8 @@ Binary distributions come in “bundles,” called
</para>
<para>
Then you should find a single directory,
<literal>ghc-<replaceable>version</replaceable></literal>, with the
following structure:
</para>
<para>
<indexterm><primary>binary distribution, layout</primary></indexterm>
<indexterm><primary>directory layout (binary distributions)</primary></indexterm>
<variablelist>
<varlistentry>
<term><literal>Makefile.in</literal></term>
<listitem>
<para>
the raw material from which the <literal>Makefile</literal>
will be made (<xref linkend="install"/>).
</para>
</listitem></varlistentry>
<varlistentry>
<term><literal>configure</literal></term>
<listitem>
<para>
the configuration script (<xref linkend="install"/>).
</para>
</listitem></varlistentry>
<varlistentry>
<term><literal>README</literal></term>
<listitem>
<para>
Contains this file summary.
</para>
</listitem></varlistentry>
<varlistentry>
<term><literal>INSTALL</literal></term>
<listitem>
<para>
Contains this description of how to install
the bundle.
</para>
</listitem></varlistentry>
<varlistentry>
<term><literal>ANNOUNCE</literal></term>
<listitem>
<para>
The announcement message for the bundle.
</para>
</listitem></varlistentry>
<varlistentry>
<term><literal>NEWS</literal></term>
<listitem>
<para>
release notes for the bundle&mdash;a longer version
of <literal>ANNOUNCE</literal>. For GHC, the release notes are contained in the User
Guide and this file isn't present.
</para>
</listitem></varlistentry>
<varlistentry>
<term><literal>bin/<replaceable>platform</replaceable></literal></term>
<listitem>
<para>
contains platform-specific executable
files to be invoked directly by the user. These are the files that
must end up in your path.
</para>
</listitem></varlistentry>
<varlistentry>
<term><literal>lib/<replaceable>platform</replaceable>/</literal></term>
<listitem>
<para>
contains platform-specific support
files for the installation. Typically there is a subdirectory for
each <literal>fptools</literal> project, whose name is the name of the project with its
version number. For example, for GHC there would be a sub-directory
<literal>ghc-x.xx</literal>/ where <literal>x.xx</literal> is the version number of GHC in the bundle.
</para>
<para>
These sub-directories have the following general structure:
</para>
<para>
<variablelist>
<varlistentry>
<term><literal>libHSstd.a</literal> etc:</term>
<listitem>
<para>
supporting library archives.
</para>
</listitem></varlistentry>
<varlistentry>
<term><literal>ghc-iface.prl</literal> etc:</term>
<listitem>
<para>
support scripts.
</para>
</listitem></varlistentry>
<varlistentry>
<term><literal>import/</literal></term>
<listitem>
<para>
<indexterm><primary>Interface files</primary></indexterm> (<literal>.hi</literal>) for the prelude.
</para>
</listitem></varlistentry>
<varlistentry>
<term><literal>include/</literal></term>
<listitem>
<para>
A few C <literal>&num;include</literal> files.
</para>
</listitem></varlistentry>
</variablelist>
</para>
</listitem></varlistentry>
<varlistentry>
<term><literal>share/</literal></term>
<listitem>
<para>
contains platform-independent support files
for the installation. Again, there is a sub-directory for each
<literal>fptools</literal> project.
</para>
</listitem></varlistentry>
<varlistentry>
<term><literal>html/</literal></term>
<listitem>
<para>
contains HTML documentation files (one
sub-directory per project).
</para>
</listitem></varlistentry>
</variablelist>
Then you should find the bundle contents inside a single directory,
<literal>ghc-<replaceable>version</replaceable></literal>.
</para>
<sect3 id="install">
......
Supports Markdown
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