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

Investigate whether we can avoid building all executables with Cabal-2.0 #3653

Closed
1 of 2 tasks
mgsloan opened this issue Dec 14, 2017 · 2 comments
Closed
1 of 2 tasks

Comments

@mgsloan
Copy link
Contributor

mgsloan commented Dec 14, 2017

See #1406 and #3486 . Currently, all executables need to be built at least once, otherwise the copy step fails.

IIRC there were some PRs to cabal that were supposed to fix this issue. However, they didn't make it into <= Cabal-2.0. In theory, I think this should be fixed in Cabal-2.0. So we should:

  • Check whether the logic to build all executables can be disabled when using Cabal-2.0 to do builds

  • If not, file a ticket with the cabal issue tracker

@mgsloan
Copy link
Contributor Author

mgsloan commented Dec 14, 2017

Indeed, not fixed in Cabal-2.0, here is the issue: haskell/cabal#2780

@mgsloan
Copy link
Contributor Author

mgsloan commented Dec 14, 2017

Going to go ahead and close this, can be tracked by #3486

@mgsloan mgsloan closed this as completed Dec 14, 2017
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

1 participant