Paul Brauner schrieb:
Hi,
i'm working on a project made of
- lots of modules - one excutable importing these modules - another excutable importing these same modules
I don't especially want to expose those modules as libraries, especially on hackage, since they are meaningless without the executables.
But, if I declare two executables in my .cabal file, cabal will compile all those modules two times each time I want to compile the executables.
Is there a way to tell cabal that those modules should be considered part of a "private" library ?
You can at least add Other-Modules to the Executables, but the problem of recompilation remains. Otherwise you may create a separate library package that contains all the code for the executables but only exposes the two main functions.