Configuring hatThe automatic configuration and installation utility, called configure, should always be used to prepare for building and installing hat. Unlike many configuration utilities, this one can be run safely at any time to change any options - it will never leave your system in an inconsistent state. You can choose your own configuration options, but the default behaviour is to prepare to build the components of hat under the targets directory, and to install those components under /usr/local, in the subdirectories bin (for scripts), lib/hat (for executables and libraries), include/hat (for Hat interface files), and man/man1 for man pages. Your machine/operating-system is detected and used during building and installation to ensure that object files and executables from different architectures do not interfere with each other. We search for an existing installation of a Haskell compiler, and hmake, and configure the build system to use them. We also guess which compiler you will use to build hat - in order of preference: ghc, then nhc98. A note about C compilers: If you do not have gcc as the name of your C compiler (e.g. on MacOS X ≤10.2 , gcc is called cc), then you need to set the CC environment variable with the real name of the compiler at configuration time. For instance: CC=cc ./configure --buildwith=... configure has many options to override the default build and installation behaviours. The options fall into three categories, but they may appear in any order on the command-line. The first group of options controls what task configure will do. You can only choose one of these - if you choose more than one, only the final one will take effect. The other two groups of options are cached and re-used in later invocations of configure, but you can always override them on the current commandline.
The second and third group of options control the configuration process and are entirely orthogonal to each other. The second group configures some general settings.
Finally, the third group of options allows you to select which components of the package you wish to install. They can be useful when installing the same software for many architectures on a heterogeneous network, if you don't want to continually re-install shared components such as man pages. As another example, you may want to update just the scripts from a new beta release, without re-installing the executables.
The latest updates to these pages are available on the WWW from
http://www.haskell.org/hat/
This page last modified: 15th August 2002 |