|(13 intermediate revisions by 9 users not shown)|
|−|There's an interesting Haskell package on [http://hackage.haskell.org/packages/archive/pkg-list.html HackageDB] you'd like to try. How do you install it on your system? | |
| || |
|−|# Check whether the package came with your Haskell implementation. |+|
Haskell package [http://hackage.haskell.org/ ] you'to . you install
|−|# If your [[:Category:OS|operating system]] has a packaging system (e.g. most Linux or BSD distributions), check whether it is already packaged there. | |
|−|# Otherwise, you'll have to build and install the package . By far the easiest way is to use [http://hackage.haskell.org/ trac/hackage/wiki/CabalInstall ''cabal-install''] to do everything automatically (note to build cabal-install for the first time, you' ll need to use the manual method below; Windows users can download a binary (cabal. exe) from [http://haskell.org/~duncan/cabal/ here]). If you so wish, you can still install packages manually -- see the section below. | |
| || |
packages manually == |+|
== Installing ==
|−|# First, ensure that all the packages it depends on are installed (by following these instructions recursively). | |
|−|# Unpack the tar file (yes, this assumes a Unix system; sorry about that ([[how to unpack a tar file in windows]])): | |
|−|#:<code>tar xzf PACKAGE-VERSION.tar.gz</code> | |
|−|# Move into the directory this creates: | |
|−|#:<code>cd PACKAGE-VERSION</code> | |
|−|# In order to install a package globally, perform the following commands (see the [http://www.haskell.org/ghc/docs/latest/html/Cabal/builders.html Cabal documentation] for more details): | |
|−|#:<code>runhaskell Setup configure</code> | |
|−|#:<code>runhaskell Setup build</code> | |
|−|#:<code>sudo runhaskell Setup install</code> | |
| || |
|−|=== Notes === |+|
to installa package ///
|−|# If instead of installing globally, you just wish to install a package for your normal user account, you could instead use the following <code>configure</ code> command, which would register the install in the user-specific database and install binaries and libraries in $HOME/ bin, $HOME/ lib, and so forth : |+|
|−|#:<code>runhaskell Setup configure --user --prefix=$HOME</code> |+|
|−|#: (Note that in Cabal 1.4 onwards, you may omit the <code>--prefix=$HOME</ code>, since <code>--prefix=$HOME/. cabal</ code> is now implied by <code>--user</ code>. Also note that you can omit <code>sudo</ code> in the install statement if you use this method. ) |+|
|−|# You can get more information about any of these commands by adding <code>--help</ code> after the command. For example, to see all the options available for the <code>configure</ code> step, you could use the following command: |+|
:<code>runhaskell Setup configure -- help</code> |+|
|−|# If you encounter unsatisfied dependencies when you run the configure step, that is when you recurse and first install the missing package. |+|
|−|# If you have more than one Haskell compiler on your system, use the <code>--with -compiler</code> option for the <code>configure</code> step. That will ensure that Cabal uses the correct compiler during the entire installation process. For example: |+|
|−|#: <code>runhaskell Setup configure --with-compiler=ghc-6.8.2</code> |+|
|−|#: <code>runhaskell Setup build </code> |+|
|−|#: <code>sudo runhaskell Setup install</code> |+|
, you .
If you have , the with the .
There's an interesting Haskell package on Hackage you'd like to try. How do you install it on your system?
Installing a library
While it is possible to "install" a library package "globally" it is most certainly a bad idea.
You should use project environment and package dependencies.
Please read the instructions for your package tool on how to set things up:
Installing an executable
First, check your package site for binary releases. It may turn out you don't have to build anything.
If you have to build from source, clone a package repository and look for the project files it uses. Then build with the appropriate project tool.
You may want to tweak the project file to use different options or dependency sets.
You may now use executables right from their build environment or copy them to your search $PATH.