1. 22 Mar, 2005 1 commit
  2. 08 Mar, 2005 1 commit
  3. 02 Mar, 2005 2 commits
  4. 21 Feb, 2005 1 commit
  5. 07 Feb, 2005 1 commit
  6. 27 Jan, 2005 1 commit
  7. 26 Jan, 2005 1 commit
  8. 20 Jan, 2005 1 commit
    • simonmar's avatar
      [project @ 2005-01-20 14:22:19 by simonmar] · c830ae13
      simonmar authored
      Fill in the haddock-interfaces and haddock-html fields in the
      package.conf files.
      
      To do this I had to make some changes:
      
        - haddock-interfaces requires the value of $(datadir).  We can't
          just plug this in, because $(datadir) might change at install-time
          (eg. a Windows installer can be placed anywhere, as can a Unix
          binary .tar.gz distribution).  The current trick is for the
          compiler to splice in the value of $libdir in package.conf at
          runtime.  So we could extend this mechanism and tell the compiler
          the value of $datadir via a command-line option, but that seems
          ugly.
      
          On Windows, $datadir==$libdir, so we don't need any changes:
          package.conf still uses $libdir, and a Windows installation is
          independent of its absolute location.  Even 'make install' on
          Windows should have this property.
      
          On Unix:
      	- for 'make install' and in-place execution, we just use
                absolute paths in package.conf
      
      	- for a binary dist, we generate a package.conf that refers
      	  to $libdir and $datadir, and splice in the values at
      	  install-time (distrib/Makefile-bin.in).
      
        - Also, I renamed $libdir to $topdir to more closely reflect its
          actual meaning.  This is somewhat malicious in that it will flush
          out all those clients using $libdir when they really shouldn't
          be :-)
      c830ae13
  9. 19 Jan, 2005 1 commit
  10. 14 Jan, 2005 1 commit
  11. 04 Jan, 2005 1 commit
    • simonmar's avatar
      [project @ 2005-01-04 13:41:53 by simonmar] · f3cdd93b
      simonmar authored
      ghc/mk/config.mk was never being included in ordinary Makefiles.  It
      was only included in the top-level fptools/Makefile for the purposes
      of obtaining binary distribution settings.
      
      This fixes that problem, and now as a side-effect $(GhcHasReadline)
      will start working again.
      f3cdd93b
  12. 07 Oct, 2004 1 commit
  13. 21 Sep, 2004 3 commits
  14. 26 Aug, 2004 1 commit
    • panne's avatar
      [project @ 2004-08-26 20:08:39 by panne] · a1939730
      panne authored
      SGML is dead, long live DocBook XML!
      
      Note: The BuildRequires tags in the spec files are still incomplete
      and the documentation about the DocBook tools needs to be updated,
      too. Stay tuned...
      a1939730
  15. 15 Aug, 2004 1 commit
    • panne's avatar
      [project @ 2004-08-15 20:28:02 by panne] · 53386c35
      panne authored
      <fanfare>Finally: Support for DocBook XML!</fanfare>
      
      After endless frustrating hours, I came to the conclusion that using (Open)Jade
      for DocBook XML is virtually impossible, there are *tons* of problems with it:
      Wildly differing paths, incorrect stylesheets, broken catalogs at funny places,
      broken wrapper scripts, missing support on Cygwin etc.  >:-P * * *
      
      So we follow the ubiquitous XSL hype and use xsltproc + DocBook XSL stylesheets
      to transform DocBook XML to HTML and FO. From FO there are two routes to PDF and
      PostScript: Either via FOP (preferred) or via PassiveTeX. Validation can be done
      via xmllint using the new make target "validate". When PassiveTeX is available,
      DVI can be generated, too.  A new make target "no-chunks-html" is available for
      generating an all-in-one HTML document. Currently there is no way to generate
      plain text or RTF, but at least the former could easily be added.
      
      Generating HTML works out-of-the-box on Cygwin now, but you will have to install
      FOP for other formats, because there seems to be no standard package for it.
      
      The HTML appearance can be controlled via CSS, but the current location of the
      master stylesheet below fptools/mk is a bit debatable. Better suggestions are
      welcome.
      
      Currently there is still support for SGML documents, but it will be dropped when
      all documents are converted to DocBook XML. The build system is complex enough
      already with the support for a *single* kind of DocBook...
      53386c35
  16. 20 May, 2004 1 commit
  17. 16 Mar, 2004 1 commit
  18. 01 Mar, 2004 1 commit
  19. 20 Feb, 2004 1 commit
    • panne's avatar
      [project @ 2004-02-20 21:29:36 by panne] · 0689f025
      panne authored
      Reverted to previous version, too, because of wrong SGMLDocWays-handling, sorry,
      but the build system should not be changed in a  non-backwards-compatible way
      easily...
      0689f025
  20. 12 Feb, 2004 1 commit
  21. 11 Nov, 2003 1 commit
  22. 17 Oct, 2003 1 commit
  23. 27 Aug, 2003 1 commit
    • panne's avatar
      [project @ 2003-08-27 15:18:29 by panne] · cab3c5cb
      panne authored
      green-card => greencard
      Green Card => GreenCard
      
      Although Alastair prefers "Greencard", the library's name is
      "Foreign.GreenCard", and unless we change this, too, "GreenCard" is
      more consistent.
      cab3c5cb
  24. 19 Aug, 2003 1 commit
  25. 18 Aug, 2003 1 commit
  26. 25 Jul, 2003 1 commit
  27. 24 Jul, 2003 1 commit
  28. 29 May, 2003 3 commits
  29. 19 May, 2003 1 commit
  30. 31 Mar, 2003 1 commit
  31. 12 Feb, 2003 1 commit
    • simonmar's avatar
      [project @ 2003-02-12 10:32:38 by simonmar] · 49a478ab
      simonmar authored
      Adapt the dist target a little to work with the nightly build's new
      way of building source dists.
      
      It now works by building a link tree to the build tree, and doing
      'make dist' on the link tree, to avoid destroying the real build tree.
      This just needed a couple of tweaks to the dist target to work.
      49a478ab
  32. 12 Dec, 2002 1 commit
  33. 19 Nov, 2002 1 commit
  34. 13 Nov, 2002 1 commit
    • simonmar's avatar
      [project @ 2002-11-13 12:21:08 by simonmar] · 351afa5a
      simonmar authored
      Add support for gcc-style "make bootstrap" which will build the stage
      1, 2 and 3 compilers in the same build tree.
      
      The idea is to simplify building a stage 2 or 3 compiler (now you only
      need one build tree), and also speed up the build: there's no need to
      compile the libraries more than once, because the stage 1 libraries
      are used for stages 2 & 3.
      
      In ghc/compiler, the objects and .hi files are now placed in
      subdirectories: ghc/compiler/stage1 has the stage1 objects,
      ghc/compiler/stage2 has the stage2 objects, etc.
      
      The story from the top-level (fptools) is this:
      
        make all 	  works as before (i.e. builds ghc (stage 1),
      		  libraries, etc.)
      
        make stage2     builds the stage 2 compiler
        make stage3     builds the stage 3 compiler
      
        make bootstrap  does 'make all' followed by 'make stage2'
        make bootstrap3 does 'make all' followed by 'make stage2; make stage3'
      
      In ghc/compiler, the story is now:
      
        make all	     works as before (i.e. builds stage 1 only)
      
        make boot          generate build dirs and dependencies for stage 1
        make boot stage=N  generate build dirs and dependencies for stage N
      
        make stageN
        make stage=N       builds stage N compiler.  Run it in-place using
      		    ./stageN/ghc-inplace.
      
      I haven't decided what to do about 'make install' yet, and this still
      needs documenting in the Building Guide.  Also, you still get the same
      $(GhcHcOpts) for each stage.
      351afa5a
  35. 30 Sep, 2002 1 commit