14

1 Context

I am involved in a Haskell project that involves lots of C-bits and FFI. So I find myself frequently running and re-running commands like

$ stack build
$ stack build --force-dirty
$ stack clean
$ rm ./.stack-work

over and over in order for the C-bits to be linked properly to the Haskell bits. Put differently, sometimes things just work when running stack build, and sometimes they don't (in which case I'm forced to cycle through the above commands over and over until my project builds properly).

This means I don't have a proper understanding of how stack (through ghc) assembles the C-bits before assembling the Haskell bits. So here is one question to help me start clearing up my confusion:

2 Question

Are there any noteworthy difference between running stack clean and deleting the contents of the .stack-work directory? Are there cases where deleting the .stack-work directory is needed as a good precaution to ensure that you are actually running a clean build?

sjakobi
  • 3,546
  • 1
  • 25
  • 43
George
  • 6,927
  • 4
  • 34
  • 67
  • 1
    If you often run into linking issues with `stack build`, please [create a bug report](https://github.com/commercialhaskell/stack/issues/new)! – sjakobi Jan 11 '17 at 02:12
  • 1
    In a single package project `stack clean --full` is basically an alias for `rm .stack-work`. – sjakobi Jan 11 '17 at 02:33
  • 1
    [This issue](https://github.com/commercialhaskell/stack/issues/1609) recorded how the `--full` option of `stack clean` was created. – SnowOnion Mar 27 '18 at 14:24

1 Answers1

1

As you can see by reading the source here:

https://github.com/commercialhaskell/stack/blob/master/src/Stack/Clean.hs

There are two levels, full and shallow. I think shallow seems to be the default. It seems to be able to clean specific packages, or if you don't provide no options at all, it'll clean everything but extra-deps in local packages.

Julian Leviston
  • 1,646
  • 10
  • 21