-
Notifications
You must be signed in to change notification settings - Fork 74
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
Determine command line options to doctest based on .cabal file #6
Comments
Something like ekmett/lens@d2459a0 can help with the actual package versions. You could augment the |
An approach that doesn't need a build-type: Custom like ekmett's solution is to get the flags by interacting with the ghci started with |
That ties you rather inextricably to the current version of Cabal though. |
Yes, same thought here, looks pretty cool, but only works with |
@aavogt you approach does not work for cases when package collisions
This bug is very interesting: Would be great if @dcoutts or @23Skidoo gave an advice on how to rebuild cmd here. |
@trofi Doesn't |
@aavogt oh, looks like cabal-install -HEAD handles it better, than current release. @23Skidoo it does (looks like in -HEAD only), but AFAIU ideally doctest needs one level deeper: doctest testsuite needs to know depends it was built against to rerun ghci Is there an easy way in cabal to dump all args like this thing in lens Would be fun to have something like Paths_$package.hs but for CompilerOptions_$package.hs. Thanks! |
@trofi I don't understand - if you're using |
|
Say
doctest foo.cabal
should run all doctests for projectfoo
and take care of the details.The text was updated successfully, but these errors were encountered: