This project is mirrored from Pull mirroring updated .
  1. 27 Apr, 2006 2 commits
  2. 28 Apr, 2006 2 commits
  3. 26 Apr, 2006 3 commits
    • 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
        include-dirs: myincludes
        install-includes: foo.h
      will install the header file myincludes/foo.h in
    • Simon Marlow's avatar
      merge from base: · 5c06af5d
      Simon Marlow authored
      Wed Apr 26 13:11:10 BST 2006  Simon Marlow <>
        * RequireOrder: do not collect unrecognised options after a non-opt
    • Simon Marlow's avatar
      pass unrecognised options before the command name to the command · 2fff06b4
      Simon Marlow authored
      Previously, options before the command name other than --help were
      just ignored, which is quite confusing behaviour.  So now,
      ./setup --with-compiler=ghc-6.4.2 configure
      works as you expect, instead of ignoring the --with-compiler option.
  4. 03 Mar, 2006 1 commit
    • Simon Marlow's avatar
      First attempt at a cabal-setup command · b5dabf1d
      Simon Marlow authored
      cabal-setup is a replacement for 'runhaskell Setup.hs'.  It accepts
      exactly the same commands.  Additionally, the following new features
      are provided:
       * Setup.{hs,lhs} is optional.  If omitted, cabal-setup behaves just
         like Distribution.Simple.defaultMain.
       * If the .cabal file contains a cabal-version field, then Setup.hs
         is built using an appropriate version of Cabal.  This might entail
         creating Setup.hs if it doesn't exist.
       * cabal-setup interprets the options --with-compiler and --with-hc-pkg
         to determine the compiler used to compile Setup.hs.
      Later, we could add support for building multiple packages in
      dependency order, as per recent discussions on
  5. 25 Apr, 2006 5 commits
  6. 11 Apr, 2006 2 commits
  7. 18 Mar, 2006 1 commit
  8. 21 Feb, 2006 1 commit
  9. 08 Apr, 2006 1 commit
  10. 04 Apr, 2006 2 commits
  11. 14 Mar, 2006 1 commit
  12. 03 Mar, 2006 4 commits
  13. 02 Mar, 2006 1 commit
    • Simon Marlow's avatar
      Support for -split-objs with GHC · bec12a91
      Simon Marlow authored
      New configure option: --enable-split-objs creates libraries using
      -split-objs with GHC (current HEAD or later only, the configure checks
      for version 6.5).  Fixes ticket #19.
  14. 06 Feb, 2006 1 commit
  15. 04 Feb, 2006 1 commit
  16. 01 Feb, 2006 3 commits
  17. 06 Feb, 2006 1 commit
  18. 01 Feb, 2006 1 commit
  19. 06 Feb, 2006 1 commit
  20. 30 Jan, 2006 2 commits
  21. 16 Jan, 2006 4 commits
    • ijones's avatar
      cleaned up suffix handler params to hooks · c4046dff
      ijones authored
      Summary if last few changes: I modified the hooks interface quite a
      bit, again.  There's good news and bad news about this.  The good news
      is that it's cleaned up and should be easier to maintain and to avoid
      future modifications.  The bad news is that this change itself will
      break stuff, of course.
      If you have any trouble building your Setup scripts, please let me
      know.  I really think that it was best to bite the bullet right now in
      one big go instead of down the road with lots of little changes.  I
      have a lot more confidence in the hooks interface, and I don't
      actually expect that it'll change as often.
      I made the types more consistent, and made sure there are accessor
      functions on each of the Flags types so that if the flags types change
      in the future, it shouldn't break lots of code.
      Another piece of good / bad news is that I decided not to get rid of
      the pre & post hooks.  They are nice for convenience and it wouldn't
      be nearly so easy to write hooks without them.
      That's bad because the interface to hooks is still pretty big, which
      means that there's more likelihood that it'll change in the future.
      Another weakness in the Hooks interface is that with command hooks
      (like sDistHook) it's tempting to add parameters to them; basically
      the stuff that we compute between the preSDist and sDist hook.  I
      removed such params and have their values computed elsewhere.
      Cabal hackers, please avoid adding parameters to these command hooks
      if at all possible in order to keep the interface steady.  If you need
      to compute a value to pass to these functions, compute it in the
      function and / or make it available as a function that someone
      crafting hooks can use as well, or consider whether it belongs in one
      of the parameters already being passed to the hooks,
      PackageDescription, LocalBuildInfo, UserHooks, Flags.
    • ijones's avatar
      make the order of params to cmd hooks consistent · 628f09a7
      ijones authored
    • ijones's avatar
      remove some flags from sdist, some cleanup · 760f2048
      ijones authored
    • ijones's avatar
      clarifying and making flags types consistent · 0e12894f
      ijones authored