This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 05 Aug, 2007 1 commit
  2. 03 Aug, 2007 1 commit
  3. 01 Aug, 2007 1 commit
  4. 24 Jul, 2007 1 commit
  5. 02 Jun, 2007 1 commit
  6. 21 May, 2007 1 commit
  7. 14 May, 2007 2 commits
    • Ian Lynagh's avatar
      Fix warnings · a51b47e2
      Ian Lynagh authored
      a51b47e2
    • Ian Lynagh's avatar
      Make a proper verbosity type, rather than using Int values · 28847431
      Ian Lynagh authored
      Hopefully this will make it easier to get better verbosity consistency.
      
      We could, by changing only Distribution.Verbosity, use
      "type Verbosity = Int" for now to give users of the library a chance to
      catch up, but the upcoming Cabal release seems like a good opportunity
      to cram in as much of the interface-changing stuff that we want to do
      as we can. I think the added benefit of a slow switch would be very low
      indeed.
      28847431
  8. 13 May, 2007 1 commit
    • Ross Paterson's avatar
      separate build and output directory for Hugs build · d0382615
      Ross Paterson authored
      Hugs requires a separate directory for the output files from the directory
      containing the preprocessed files.  The --scratchdir option now sets the
      former (and thus has an effect only for Hugs).
      
      This repairs the Hugs build.
      d0382615
  9. 01 May, 2007 1 commit
  10. 11 Jan, 2007 1 commit
  11. 10 Jan, 2007 1 commit
  12. 27 Nov, 2006 1 commit
  13. 21 Oct, 2006 1 commit
  14. 05 Oct, 2006 1 commit
  15. 08 Sep, 2006 1 commit
  16. 03 May, 2006 3 commits
  17. 02 May, 2006 1 commit
  18. 01 May, 2006 1 commit
  19. 26 Apr, 2006 1 commit
    • Simon Marlow's avatar
      Better support for packages that need to install header files · dc87abd4
      Simon Marlow authored
      There's a new field for .cabal files: 
      
           install-includes: foo.h bar.h
      
      This means the same as 'includes', except that the files named therein
      will be installed into $libdir/include.  'includes' should only be
      used for headers already installed on the system.
      
      Directories listed in 'include-dirs' still turn into -I options for
      hsc2hs, cpphs, and C compilations.  However, for installation
      purposes, relative directories in 'include-dirs' are now treated
      differently from absolute directories:
      
        - an absolute directory is copied to the include-dirs field
          of the installed package config
      
        - files names in install-includes are assumed to be found in
          one of the *relative* directories listed in include-dirs
      
      So the common pattern for providing a header file that you want to
      be available everywhere including to via-C compilations against this
      package:
      
        include-dirs: myincludes
        install-includes: foo.h
      
      will install the header file myincludes/foo.h in
      $libdir/include/foo.h.
      dc87abd4
  20. 25 Apr, 2006 1 commit