Skip to content

some way to specify common build-depends for library, executables and test-suites #938

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

Closed
bos opened this issue May 24, 2012 · 4 comments
Closed

Comments

@bos
Copy link
Contributor

bos commented May 24, 2012

(Imported from Trac #948, reported by Oblosys on 2012-04-27)

Not sure whether this is a feature request or a bug report. I sometimes have a number of dependencies that are the same for library, executable, and test-suite. The global property 'build-depends' looks like an ideal place to put these, but any dependencies I list there seem to be ignored by cabal.

@bos
Copy link
Contributor Author

bos commented May 24, 2012

(Imported comment by @kosmikus on 2012-04-27)

And making the executable and test-suite depend on the library does not work for you?

@Oblosys
Copy link

Oblosys commented Jul 17, 2012

That works indeed! I wasn't aware this was possible. But is the global "build-depends" property always ignored? If not, maybe a warning should be given when it is?

@grayjay
Copy link
Collaborator

grayjay commented May 30, 2016

#3404 and #2832 are related.

@ezyang ezyang modified the milestone: Cabal 2.0 Sep 6, 2016
@quasicomputational
Copy link
Contributor

Common stanzas are a thing now, hurrah!

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

7 participants