Skip to content

Cabal passes invalid base-url to Haddock on Windows #1064

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
sol opened this issue Oct 10, 2012 · 1 comment · Fixed by #1407
Closed

Cabal passes invalid base-url to Haddock on Windows #1064

sol opened this issue Oct 10, 2012 · 1 comment · Fixed by #1407

Comments

@sol
Copy link
Member

sol commented Oct 10, 2012

Haddock can read interface files with e.g.

--read-interface=<base-url>,<path-to-haddock-interface-file>

where base-url has to be a a valid URL. On Windows, Cabal passes something like C:\foo\bar\baz as base-url which is not a valid URL. As a result, the generated index.html won't work with Firefox.

This has been originally report at the HP issue tracker, and Mark reported it on Haddock's issue tracker.

@dcoutts
Copy link
Contributor

dcoutts commented Dec 2, 2013

This change has broken the feature cabal haddock --html-location=URL when you specify the URL as relative. This is what is causing haddock docs on hackage to appear as file:// URLs. We build the docs using --html-location=/package/$pkg-$version/docs. It should to be a relative URL, both because it's the sensible thing to do but also because we need to not force http or https, but work with either.

Teino1978-Corp pushed a commit to Teino1978-Corp/Teino1978-Corp-standalone-haddock that referenced this issue Nov 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants