Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stack is missing cabal's --extra-framework-dirs #4022

Open
TravisWhitaker opened this issue May 13, 2018 · 3 comments
Open

Stack is missing cabal's --extra-framework-dirs #4022

TravisWhitaker opened this issue May 13, 2018 · 3 comments

Comments

@TravisWhitaker
Copy link

I'm working on a macOS-specific package that needs to link against frameworks. With cabal, I need to configure like this:

$ cabal configure --extra-framework-dirs=/System/Library/Frameworks/ ...

But stack seems to have no equivalent option. I'm sure it's possible to get around this with --ghc-options, but it'd be nice to be able to stick this in stack.yaml, just like extra-lib-dirs. I'd imagine that extra-framework-dirs works just like extra-lib-dirs and that this would be easy to add, but I don't know for sure.

@mgsloan mgsloan added this to the P2: Should milestone Jun 11, 2018
@mgsloan
Copy link
Contributor

mgsloan commented Jun 11, 2018

Indeed, this is not currently supported. Stack should really support arbitrary configure-options - it's been a longstanding omission - #1438

Alternatively, support for this specific option could be added.

@karamellpelle
Copy link

karamellpelle commented Apr 7, 2019

@TravisWhitaker : What about adding the cabal option extra-framework-dirs to your .cabal file?

extra-framwork-dirs was introduced by Cabal 1.24.0.0.

@TravisWhitaker
Copy link
Author

One can't assume what the value of extra-framework-dirs should be, especially if Nix is in use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants