[Hackage] #189: Handle framework paths (-F) in Cabal

Hackage trac at galois.com
Mon Dec 10 18:24:10 EST 2007

#189: Handle framework paths (-F) in Cabal
  Reporter:  guest        |        Owner:         
      Type:  enhancement  |       Status:  new    
  Priority:  normal       |    Milestone:         
 Component:  Cabal        |      Version:
  Severity:  normal       |     Keywords:         
Difficulty:  normal       |   Ghcversion:  6.8.1  
  Platform:  Mac OS       |  
 There's been some discussion on the GHC trac
 ([http://hackage.haskell.org/trac/ghc/ticket/1931 1931],
 [http://hackage.haskell.org/trac/ghc/ticket/1798 1798],
 [http://hackage.haskell.org/trac/ghc/ticket/1395 1395]) about adding
 framework search paths (gcc's `-F` flag, and ghc's `-framework-path`
 flag).  Currently Cabal handles `-framework`, but not `-framework-path`.

 I propose the following behavior for Cabal:
  1. Add a `framework-path:` field which will pass `-framework-path` to
 `ghc` and `-F` to `gcc`, `hsc2hs`, et. al.
  2. Always add `-F$HOME/Library/Frameworks` as an argument to the above
 programs (regardless of any `framework-path` entries).

 I believe `#1` to be uncontroversial.  My reasoning for `#2` is the
  - `$HOME/Library/Frameworks` is the standard location to put frameworks
 if you do not have administrative access.
  -  Without it, `readline.cabal` (e.g.) would need
 framework-path: /Users/judah/Library/Frameworks
   which is not portable between machines.

 Finally, note that these flags only affect build behavior, not runtime
 loading of libraries (which searches `$HOME/Library/Frameworks` by
 default).  See [http://hackage.haskell.org/trac/ghc/wiki/OSXFrameworks
 OSXFrameworks] for more info.


Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/189>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects

More information about the cabal-devel mailing list