GitLab

This is the portable thing to do and fixes things on FreeBSD where make/=gmake

The -P flag wasn't superfluous, but it was wrong for executables.

Add explicit types for a couple of constants to work around Hugs's
imperfect implementation of the monomorphism restriction.

Patch to fix "-ixyz" being overwritten by "-i" and to remove Cabal's dependency on the Cabal package.

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.

Wed Apr 26 13:11:10 BST 2006  Simon Marlow <simonmar@microsoft.com>
  * RequireOrder: do not collect unrecognised options after a non-opt

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.

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 libraries@haskell.org.

 
There are a few changes in this patch:
 
   - New flag to register, --inplace.  "setup register --inplace"
     registers the package for use in the build tree, i.e. without
     installing.  It works with GHC only, currently.
     
   - The parameters to RegisterCmd, UnregisterCmd and InstallCmd are a
     legacy from before the time of hooks (or something) and don't
     serve any purpose any more, AFAICT.  So I removed them.
 
   - I don't think "setup register" worked propertly before if
     --user was given to configure.  It does now.

   - New flag to register: --with-hc-pkg (just the same as when
     given to configure, but lets you override it at register-time)

This also matches package.conf.in.

This also matches Cabal.cabal.