-
Notifications
You must be signed in to change notification settings - Fork 704
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
Support pure test packages #1186
Milestone
Comments
This would be helpful to resolve #960. @BardurArantsson This would be a good task for a newcomer. There isn't any technical problem to resolve here, it's just a matter of flipping a switch in the source code. |
Here are a few notes about what must be done before we close this issue.
|
grayjay
added a commit
to grayjay/cabal
that referenced
this issue
Jul 4, 2015
This commit relaxes D.PackageDescription.Check.checkConfiguredPackage so that it only warns when a package declares no executables, libraries, tests, or benchmarks. Similarly, it relaxes the check during build to only require one component that is buildable and enabled. Install now requires an executable or library.
dcoutts
added a commit
that referenced
this issue
Jul 6, 2015
Support pure test packages (issue #1186)
Looks like this was fixed by #2699. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently if I have a package description file that defines just a test suite (without a library), I get the message
I suppose there are no technical issues with building and running such tests?
The reason I want to do this is that the test for smallcheck also depends on test-framework-smallcheck, which in turn depends on smallcheck. If I put the test suite description into
smallcheck.cabal
, the build command will produce the following error:The text was updated successfully, but these errors were encountered: