Developer FAQ

This is just getting started. It will absorb some of the other Developer docs.

Developing hledger

How do I get/build the hledger source ?

$ git clone https://github.com/simonmichael/hledger
$ stack build

You can specify hledger, hledger-ui or hledger-web as an argument to build just that executable. Please see Install > Build from source for more details and other build methods.

What other repos are there ?

There are three official repos: - https://github.com/simonmichael/hledger - the main hledger repo, for hledger, hledger-ui and hledger-web. Shortcut url: https://code.hledger.org - https://github.com/simonmichael/hledger_site - the hledger.org website - https://github.com/simonmichael/hledger_finance - the hledger project’s financial ledger

And third-party add-ons and tools (hledger-iadd, hledger-utils, full fledged hledger, hledger-flow, etc.) have their own repos.

How do I run a build in place ?

After building with stack,

$ stack exec -- hledger [ARGS]    # or hledger-ui, hledger-web

Or after building with cabal,

$ cabal exec -- hledger [ARGS]

How do I install a build in $PATH ?

$ stack install

This installs the hledger executables to ~/.local/bin. You should have this directory configured in $PATH. Or you can install to another directory with --local-bin-path. It builds the executables first if needed; see Install > Build from source for more about building. You can specify hledger, hledger-ui or hledger-web as an argument to build/install just that executable.

If you use cabal, it has a similar command; the argument is required. It will install executables to ~/.cabal/bin:

$ cabal install all:exes

How do I build/run hledger with ghc-debug support ?

$ stack build --flag hledger:ghcdebug --flag hledger-ui:ghcdebug --flag hledger-web:ghcdebug

You can check it in the –version output, which should mention “ghc-debug”:

$ stack exec -- hledger --version

With such a build, you can enable the ghc-debug listener by running hledger with a negative –debug level. Eg:

$ hledger ... --debug=-1    # run normally, while also listening for ghc-debug commands
$ hledger ... --debug=-2    # pause for ghc-debug commands at program start
$ hledger ... --debug=-3    # pause for ghc-debug commands at program end

Then you can pause/resume hledger’s execution and inspect memory and profile information with the interactive ghc-debug-brick client, or extract specific information with a custom ghc-debug script.

2.6 KiB Raw Blame History Unescape Escape