1. 20 Nov, 2007 1 commit
    • Simon Marlow's avatar
      Always do 'setup makefile' before building each library · 5ca2e94e
      Simon Marlow authored
      This forces preprocessing to happen, which is necessary if any of the
      .hsc files have been modified.  Without this change, a 'setup
      makefile' would be required by hand after a .hsc file changed.
      Fortunately 'setup makefile' isn't much extra work, and I've made it
      not overwrite GNUmakefile if it hasn't changed, which avoids
      recalculating the dependencies each time.
      5ca2e94e
  2. 11 Nov, 2007 1 commit
  3. 10 Nov, 2007 1 commit
  4. 05 Nov, 2007 2 commits
  5. 03 Nov, 2007 2 commits
  6. 28 Oct, 2007 1 commit
  7. 31 Oct, 2007 1 commit
  8. 29 Oct, 2007 1 commit
  9. 25 Oct, 2007 1 commit
  10. 24 Oct, 2007 1 commit
  11. 18 Oct, 2007 1 commit
  12. 27 Sep, 2007 1 commit
  13. 23 Sep, 2007 2 commits
    • Ian Lynagh's avatar
      Put packages in ../$$pkgid not ../$$pkg · 0a148fd7
      Ian Lynagh authored
      0a148fd7
    • sven.panne@aedion.de's avatar
      Fix bug #1725 (Haddock links between packages) · 02924d52
      sven.panne@aedion.de authored
      Resolving this bug is a bit tricky, it boils down to the question: Should the
      Haddock links between packages include the package version or not?
      
      Pro: We can differentiate between various versions of the same package,
      installed all at once. (How often does this really happen in practice?)
      
      Cons: When package A refers to a package B, and B is later upgraded, links
      in A's documentation will break. Furthermore, if an *additional* version of
      B is installed, which version should A refer to?
      
      Because IMHO it is not clear what to do when version numbers are included,
      let's leave them out. If somebody has a better idea, feel free to submit a
      better patch.
      
      MERGE TO STABLE
      02924d52
  14. 18 Sep, 2007 1 commit
  15. 16 Sep, 2007 1 commit
  16. 14 Sep, 2007 2 commits
  17. 13 Sep, 2007 4 commits
  18. 12 Sep, 2007 2 commits
  19. 11 Sep, 2007 1 commit
    • Ian Lynagh's avatar
      Further tweaking of haddock doc installation · 5dfc10ca
      Ian Lynagh authored
      On Windows we now always use a path beginning $topdir/ so bindists are
      relocatable.
      
      We also now tell "Setup configure" where we are putting the
      documentation, and tell installPackage to override as little as
      possible.
      5dfc10ca
  20. 09 Sep, 2007 2 commits
  21. 08 Sep, 2007 1 commit
  22. 07 Sep, 2007 1 commit
  23. 06 Sep, 2007 2 commits
  24. 05 Sep, 2007 3 commits
  25. 04 Sep, 2007 1 commit
    • sven.panne@aedion.de's avatar
      Don't hardwire the build path into the Haddock docs · bb7c2f85
      sven.panne@aedion.de authored
      Formerly, the ghc-pkg was called to get the HTML dirs for other packages, but
      of course doing this at *build* time is totally wrong. Now we use a relative
      path, just like before. This is probably not perfect, but much better than
      before.
      
      As a sidenote: Cabal calls the relevant flag "html-location", ghc-pkg calls the
      field "haddock-html", and Haddock itself uses it as part of "read-interface".
      Too much creativity is sometimes a bad thing...
      bb7c2f85
  26. 31 Aug, 2007 3 commits