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

[Hackage]

#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:23 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.

 Just to note, this is not a model we ever intend to support in the
 "Simple" build system. Build systems should be purely functional.

 The one concession we will need to make to a purely functional description
 is the ability to specify exceptions that some changed input will not
 trigger another function to be recalculated (eg while hacking, temporarily
 specifying that stage1 of a compiler changing will not cause rebuild of
 stage2).

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

 Probably. A common section is not a bad thing. Note that this would not
 give any sharing of build results. It's just a shortcut to putting the
 same options in each section.

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