> thanks for the kind words; using shake for our build system has been a
> very good decision so far, we've been able to minimise the time spent
> with platform-dependent build systems and IDEs and get to write haskell
> code instead ;)
Glad to hear it! It's always very nice to know that it works for others too.
>> * Released my tool to generate Haddock documentation and upload it to
>> Hackage, since without docs finding out about shake-language-c is
>> quite difficult. I suggest you read and follow
>>
http://neilmitchell.blogspot.co.uk/2014/10/fixing-haddock-docs-on-hackage.html,
>> then your docs will be populated.
>
> cool, thanks! i wasn't aware of the fact that hackage still doesn't
> build documentation. using your tool, i've uploaded documentation for
> shake-language-c now [1].
I think it's been restarted, but the doc builder has quite a long
backlog to get through. It also seems to have been restarted with a
newer version of Haddock, so the bugs my tool papers over are mostly
gone.
> btw, i had to add a missing double quote in one shell command line in
> src/Cabal.hs:
>
> system_ $ "cp -R dist/doc/html/" ++ name ++ " \"" ++ dir ++ "/" ++ name
> ++ "-" ++ ver ++ "-docs\""
I've pushed a new version of the 'neil' tool with that fix. I'm on
Windows, and it doesn't seem to have been an issue there - the
problems with manually quoting your command lines.
Looking over your module, it certainly looks impressively thorough.
Thanks, Neil