On Tue, 2006-03-14 at 17:15 +0100, Daniel Fischer wrote:
Okay, I've got myself gtk2hs now (and remebered what shied me away the first time: click on dowload opens Pandora's cookie box). Seems to work, although linking takes ages and the binaries are awe-inspiringly huge. Now two questions remain (well, two I find fit to post here): - is there a user-manual or tutorial ? - when building with --enable-docs, how far should the ghc-docdir-path reach? I tried /usr/local/share/ghc-6.4.1/html/libraries and /usr/local/share/ghc-6.4.1/html and was confronted with lots of WARNING: could not resolve ... in both cases.
Even when it works perfectly we still get lots of "WARNING: could not resolve ...". There are broken cross references in our docs. We've been fixing these but they're not as high a priority as many other things. You can tell if the docs are linking to the ghc base docs if you don't get warnings about not being able to resolve things like Int and String. Rather embarrassingly, it turns out that --ghc-docdir does nothing at all. It has been a broken option for a couple years. Other people noticed it too recently. I'll be replaced or fixed in the next version. In the mean time I think yo might be able to get the effect with: make HADDOCK="haddock --use-package=base" or whatever other options you need. Otherwise you'll have to make do with docs that are not linked to the ghc base docs (which is not such a great hardship since almost all the links to things in the base package are just for simple types). Or use the docs online which link to the docs on the ghc website. Duncan