I am working on this Haskell project and I have a file for it. Now my project is structured as a library that implements a simple interpreter. I also have a very short main file that needs to be created in an executable to call the library. I want to do this:
1) compile the library and expose some of the modules
2) compile the executable file
I have a cabal file that works and seems to be doing this. The problem is that when compiling the executable file, it recompiles all the modules that were already compiled in step (1). I don’t quite understand why he does it - is there a way to stop him without creating two separate bondage files?
I really don’t want to create two separate cabal files, because the cabal doesn’t seem to like having both cabal files in the same directory, and I really don’t want to set up a separate project directory for the second step, since it basically comes down to compiling a single file.
cabal-version: >= 1.6 build-type: Simple name: HaSC version: 0.2.3 license: OtherLicense category: Language author: Chris B maintainer: Chris B copyright: Chris B 2010 - 2011 synopsis: (HA)skell (S)ound (C)hange applier (HaSC) library description: HaSC implements a little language for applying sound changes to words homepage: http:
haskell cabal
chrisdb Jul 15 2018-11-17T00: 00Z
source share