Skip to content
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

The Make build-type doesn't pass haddock options to make #234

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

The Make build-type doesn't pass haddock options to make #234

bos opened this issue May 24, 2012 · 3 comments

Comments

@bos
Copy link
Contributor

bos commented May 24, 2012

(Imported from Trac #241, reported by ross on 2008-02-16)

The Simple build-type works out the correct options for haddock, including the extra options for haddock2 and --read-interface options taking into account the --html-location option. For example this is used by hackageDB to generate correct inter-package links. There is no way for the makefile to figure out where those links should point. (e.g. the wxcore package.)

The Make build-type ought to put these options in a HADDOCKOPTS setting on the make command line, so that the makefile can pass these to haddock.

@bos
Copy link
Contributor Author

bos commented May 24, 2012

(Imported comment by @dcoutts on 2008-02-16)

The Haddock module now has a function haddockPackageFlags that returns all the --read-interface= flags.

I'm not quite clear about what the other options should be.

@bos
Copy link
Contributor Author

bos commented May 24, 2012

(Imported comment by ross on 2008-02-19)

Replying to @dcoutts:

The Haddock module now has a function haddockPackageFlags that returns all the --read-interface= flags. I'm not quite clear about what the other options should be.

Probably just about everything except -o and possibly -h.

But I'm not sure the Make build-type can ever be made to work properly (Custom even more so, of course). I think we need a build type that is mostly Simple, but with program hooks (as Configure does for postConfig).

@tibbe
Copy link
Member

tibbe commented Jan 28, 2013

No activity for 5 years, so closing.

@tibbe tibbe closed this as completed Jan 28, 2013
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

2 participants