[Hackage] #200: Allow more convenient use of ghc profiling options -auto and -auto-all

Hackage trac at galois.com
Tue Dec 18 16:44:14 EST 2007


#200: Allow more convenient use of ghc profiling options -auto and -auto-all
----------------------------+-----------------------------------------------
  Reporter:  guest          |        Owner:         
      Type:  enhancement    |       Status:  new    
  Priority:  normal         |    Milestone:         
 Component:  Cabal library  |      Version:  1.2.3.0
  Severity:  normal         |   Resolution:         
  Keywords:                 |   Difficulty:  normal 
Ghcversion:  6.8.2          |     Platform:         
----------------------------+-----------------------------------------------
Changes (by duncan):

  * summary:  Feature request: Simplify the profiling process => Allow more
              convenient use of ghc profiling options -auto
              and -auto-all

Comment:

 Replying to [ticket:200 guest]:
 > Add Setup.(l)hs options that: 1) tells ghc to make a profiling library;

 This is covered by the existing configure `--enable-library-profiling`

 > 2) tells ghc to make a profiling executable

 This is covered by the existing configure `--enable-executable-profiling`

 > 3) pass on the (a) -auto or (b) -auto-all option

 This is currently missing.

 > 4) Let you do (1)-(2)-(3a) or (1)-(2)-(3b) with a single option, instead
 of three.

 This is covered by `cabal-install` since the `install` command does
 configure, build and install and it takes the above two options.


 So what we're currently missing is any way of handling the `-auto` or
 `-auto-all` options. I'm changing the summary to reflect that.

 See also the cabal-devel thread starting with this message:
 http://www.haskell.org/pipermail/cabal-devel/2007-January/000379.html

 Does anyone have any good suggestion about how to handle `-auto` or
 `-auto-all` ? We cannot make them default for profiling (see above thread)
 and they are not features that make sense for other haskell
 implementations.

 Currently one can put them in the .cabal file, but it's not really
 appropriate to do that since they're not static options.

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


More information about the cabal-devel mailing list