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

Hackage trac at galois.com
Mon Feb 1 07:00:22 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 AnttiJuhaniKaijanaho):

 Replying to [comment:22 duncan]:
 > For ghc --make you simply get wrong results (it does not track when you
 change compile options).

 Which is relevant in sophisticated cases.  I'm concerned that cabal makes
 simple things more complicated than they need to be.

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

 Which is a nice thing to have when you need it.

 > > 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.

 Similarly, I'd like a way to specify compilation options (such as
 warnings) common to all executables.

 ... Heh.  Should I be opening a separate ticket? :)

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

More information about the cabal-devel mailing list