[ci skip]
5.4 KiB
A. I want to download a packaged version
Packaged versions may lag behind the latest release, but are the quickest to install.
Windows: | Download and run the latest development builds (-> Appveyor CI) |
Mac: | brew install hledger |
Debian, Ubuntu: | sudo apt install hledger hledger-ui hledger-web |
Fedora, RHEL: | sudo dnf install hledger |
Gentoo: | sudo layman -a haskell && sudo emerge hledger hledger-ui hledger-web |
NixOS: | nix-env -iA nixpkgs.haskellPackages.hledger \ nixpkgs.haskellPackages.hledger-ui \ nixpkgs.haskellPackages.hledger-web |
Only some of the hledger tools may be available, eg Homebrew does not yet include hledger-ui, hledger-web or hledger-api (packagers welcome!).
B. I want to build the latest release
The latest release (see release notes) is a good choice. You have to build it, but that's pretty easy.
-
Install
stack
. On Windows, the 64-bit version is recommended. -
stack install --resolver=nightly hledger [hledger-ui] [hledger-web] [hledger-api]
On Windows, hledger-ui is not yet available.
If stack says you need to runstack setup
, do that first.
Warnings about "No packages found in snapshot which provide a "hsc2hs" executable" can be ignored.
If required C libraries (like curses) are not installed, you might need to install those manually and try again, eg:Debian, Ubuntu: sudo apt install libncurses5-dev
Fedora, RHEL: sudo dnf install ncurses-devel
-
If stack warns that
~/.local/bin
(or the Windows equivalent) is not in$PATH
, fix that. Eg if you're a bash user:
echo "export PATH=$PATH:~/.local/bin" >> ~/.bashrc && source ~/.bashrc
Now you can runhledger --version
,hledger-ui --version
etc.
Installing with cabal
is similar, if you're familiar with that.
C. I want to build the development version
The dev version includes not-yet-released features and is stable enough for daily use.
-
git clone http://code.hledger.org hledger
-
cd hledger
-
stack install
with the same caveats as mentioned above:- if stack says you need to run
stack setup
, do that first, - if building fails due to missing C libs, install those first
- if stack warns that
~/.local/bin
(or the Windows equivalent) is not in$PATH
, fix that - warnings about "No packages found in snapshot which provide a hsc2hs executable" can be ignored
- if stack says you need to run
Cabal users can use the cabal-install.sh
or the cabal.project
files instead.