You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(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.
The text was updated successfully, but these errors were encountered:
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).
(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.
The text was updated successfully, but these errors were encountered: