1. 22 Feb, 2007 2 commits
  2. 08 Feb, 2007 2 commits
  3. 06 Feb, 2007 1 commit
    • Simon Marlow's avatar
      Detect the snapshot version number using darcs · 06decfcd
      Simon Marlow authored
      For non-release builds, we want to append a date to the version number
      (e.g. 6.7.20070206).  Previously this was done by the nightly build
      script, this new method figures out the snapshot version by querying
      the darcs repository and finding the date of the most recent patch
      (actually it finds the most recent of the last 100 patches, but that
      should be good enough).  This is done by the configure script.
      
      To handle source distributions, we create a file VERSION in the
      top-level directory that contains the version number, and ship this in
      the source distribution.  The configure script picks up the version
      from this file if it doesn't see a _darcs directory.
      06decfcd
  4. 05 Feb, 2007 2 commits
  5. 04 Feb, 2007 1 commit
  6. 16 Sep, 2006 1 commit
  7. 12 Aug, 2006 1 commit
  8. 03 May, 2006 1 commit
  9. 02 May, 2006 1 commit
  10. 24 Apr, 2006 1 commit
  11. 19 Apr, 2006 1 commit
  12. 07 Apr, 2006 3 commits
    • Simon Marlow's avatar
      fix source dists · 2670dc47
      Simon Marlow authored
      2670dc47
    • Simon Marlow's avatar
      fix binary dists · 55bb9846
      Simon Marlow authored
      55bb9846
    • Simon Marlow's avatar
      Reorganisation of the source tree · 0065d5ab
      Simon Marlow authored
      Most of the other users of the fptools build system have migrated to
      Cabal, and with the move to darcs we can now flatten the source tree
      without losing history, so here goes.
      
      The main change is that the ghc/ subdir is gone, and most of what it
      contained is now at the top level.  The build system now makes no
      pretense at being multi-project, it is just the GHC build system.
      
      No doubt this will break many things, and there will be a period of
      instability while we fix the dependencies.  A straightforward build
      should work, but I haven't yet fixed binary/source distributions.
      Changes to the Building Guide will follow, too.
      0065d5ab
  13. 09 Feb, 2006 1 commit
  14. 16 May, 2005 1 commit
  15. 29 Apr, 2005 1 commit
  16. 22 Mar, 2005 1 commit
  17. 08 Mar, 2005 1 commit
  18. 02 Mar, 2005 2 commits
  19. 21 Feb, 2005 1 commit
  20. 07 Feb, 2005 1 commit
  21. 27 Jan, 2005 1 commit
  22. 26 Jan, 2005 1 commit
  23. 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
  24. 19 Jan, 2005 1 commit
  25. 14 Jan, 2005 1 commit
  26. 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
  27. 07 Oct, 2004 1 commit
  28. 21 Sep, 2004 3 commits
  29. 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
  30. 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
  31. 20 May, 2004 1 commit
  32. 16 Mar, 2004 1 commit