-
Notifications
You must be signed in to change notification settings - Fork 696
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
Haddock doesn't work (with Backpack?) #4905
Comments
Looks like this is not caused by Backpack, see #4506
|
I tried to use the same technique (modifying the file before
What does this line mean?
I'm not using any |
Alright, I figured out where this |
Summary so far:
|
I feel like I have successfully manually generated documentation for signatures before, c.f. http://next.hackage.haskell.org:8080/package/str-sig-0.1.0.2/docs/Str.html but it is possible that someone introduced a regression to Haddock when I wasn't looking. But I did have to work somewhat hard to make it work, since when I did this documentation generation I can definitely believe Haddock with Template Haskell isn't working, this code path was never tested. |
@int-index If possible, could you try a build of GHC with this patch? https://phabricator.haskell.org/D4234 I think I may have accidentally fixed this one too. |
I tried to test it, but Haddock
|
@int-index please try haddock/ghc-head branch. Master only build with current ghc stable. |
@alexbiehl Thank you for the suggestion, but it appears that |
I made another attempt to reproduce this with
Since (1) has its own issue #4506, I am closing this one. |
The HTML documentation is not generated at all. UPD: seems to be caused by #4506
System configuration: Xubuntu,
ghc-8.2.2
andcabal-head
installed fromppa:hvr/ghc
.Project structure:
File contents:
cabal.project
:cabal.project.local
:pkg-example/pkg-example.cabal
:pkg-example/Setup.hs
:pkg-example/src/Pkg/Sig.hsig
:pkg-example/src/Pkg/Core.hs
:Steps to reproduce:
Expected result: there are HTML files in
dist-newstyle
.Actual result: no documentation generated.
The text was updated successfully, but these errors were encountered: