[Hackage] #89: Sharing of object files between executable builds?

Hackage trac at galois.com
Sun Jan 31 17:24:49 EST 2010

#89: Sharing of object files between executable builds?
  Reporter:  bjorn@…             |        Owner:  blackh   
      Type:  enhancement         |       Status:  assigned 
  Priority:  normal              |    Milestone:  Cabal-1.8
 Component:  Cabal library       |      Version:           
  Severity:  normal              |     Keywords:           
Difficulty:  easy (<4 hours)     |   Ghcversion:  6.4.2    
  Platform:  Linux               |  

Comment(by duncan):

 Replying to [comment:21 AnttiJuhaniKaijanaho]:
 > For me as a user, this feature request is obvious and it's rather
 disappointing that Cabal will not support it.  A simple makefile-based
 system, or even running ghc --make by hand!, does better on this count.

 With the makefile you are explicitly sharing modules and you specify the
 compile options once for each source file. For ghc --make you simply get
 wrong results (it does not track when you change compile options).

 As a design choice (one made long ago) Cabal lets you specify different
 compile options for the same source file when used in different

 > What about allowing specifying a list of modules common to all
 executables?  That would help me.  (Or, of course, if the "private
 libraries" are lightweight enough that I just have to list the modules
 that are included in it, that's good enough.)

 That would be similar though I think I prefer the private library
 approach, it's a bit more flexible. The "common modules" approach does not
 work for sharing modules between a library and an executable with ghc
 because the module need to be compiled differently.

Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/89#comment:22>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects

More information about the cabal-devel mailing list