Question: Behaviour of `cabal install` vs `cabal build`? (Placement of build artefacts)

Open
#12,270 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Active
Tech stack
haskell
Domain
build-system, cli

Research direction

Start by reproducing the reported commands in a Cabal checkout: cabal install cabal-install followed by cabal build. Trace where each command places build artefacts and why dependencies rebuild, then document the distinction and expected locations so the reported behavior is clearly explained.

Written by the indexing model from the issue text.

Description

type: user-question

I used to be under the assumption that cabal install basically boils down to cabal build and copying over executables.

Indeed when I run cabal install cabal-install in a cabal checkout it seems to build the checkout rather than the version published on hackage:

Starting     cabal-install-3.19.0.0 (exe:cabal)
Building     cabal-install-3.19.0.0 (exe:cabal)
Installing   cabal-install-3.19.0.0 (exe:cabal)
Completed    cabal-install-3.19.0.0 (exe:cabal)

However the binaries don't seem to be placed in dist-newstyle but some other place. As there is no cabal.exe in the checkout folder after cabal install cabal-install.

And if I run cabal build afterwards I rebuilds not just cabal but also some of the dependencies, ultimately producing a cabal.exe under dist-newstyle as expected.


I suspect this is somehow related to the behaviour of cabal configure which states:

The options of all of these flags apply only to local packages in a project; this behavior is different than that of cabal install, which applies flags to every package that would be built.

But I never explicitly invoked cabal configure so maybe transitively this is a reason, but still quite surprising.

Maybe this was always the case and I just never noticed. But it seems like surprising behaviour to me.

Dominant language
Haskell
Stars
1.8k
Forks
766
Avg merge
5d 21h
Merged PRs (30d)
27

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from haskell/cabal

All issues in haskell/cabal

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.