Hoogle Search

Within LTS Haskell 24.51 (ghc-9.10.3)

Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.

Exact lookup

1. installExe :: Verbosity -> LocalBuildInfo -> FilePath -> FilePath -> (FilePath, FilePath) -> PackageDescription -> Executable -> IO ()

   Cabal	Distribution.Simple.GHCJS

   Install executables for GHCJS.

2. installFLib :: Verbosity -> LocalBuildInfo -> FilePath -> FilePath -> PackageDescription -> ForeignLib -> IO ()

   Cabal	Distribution.Simple.GHCJS

   Install foreign library for GHC.

3. installLib :: Verbosity -> LocalBuildInfo -> FilePath -> FilePath -> FilePath -> PackageDescription -> Library -> ComponentLocalBuildInfo -> IO ()

   Cabal	Distribution.Simple.GHCJS

   Install for ghc, .hi, .a and, if --with-ghci given, .o

4. getInstalledPackages :: Verbosity -> PackageDBStack -> ProgramDb -> IO InstalledPackageIndex

   Cabal	Distribution.Simple.HaskellSuite

   No documentation available.

5. installLib :: Verbosity -> LocalBuildInfo -> FilePath -> FilePath -> FilePath -> PackageDescription -> Library -> ComponentLocalBuildInfo -> IO ()

   Cabal	Distribution.Simple.HaskellSuite

   No documentation available.

6. module Distribution.Simple.Install

   This is the entry point into installing a built package. Performs the "./setup install" and "./setup copy" actions. It moves files into place based on the prefix argument. It does the generic bits and then calls compiler-specific functions to do the rest.

7. install :: PackageDescription -> LocalBuildInfo -> CopyFlags -> IO ()

   Cabal	Distribution.Simple.Install

   Perform the "./setup install" and "./setup copy" actions. Move files into place based on the prefix argument. This does NOT register libraries, you should call register to do that.

8. module Distribution.Simple.InstallDirs

   This manages everything to do with where files get installed (though does not get involved with actually doing any installation). It provides an InstallDirs type which is a set of directories for where to install things. It also handles the fact that we use templates in these install dirs. For example most install dirs are relative to some $prefix and by changing the prefix all other dirs still end up changed appropriately. So it provides a PathTemplate type and functions for substituting for these templates.

9. type InstallDirTemplates = InstallDirs PathTemplate

   Cabal	Distribution.Simple.InstallDirs

   The installation directories in terms of PathTemplates that contain variables. The defaults for most of the directories are relative to each other, in particular they are all relative to a single prefix. This makes it convenient for the user to override the default installation directory by only having to specify --prefix=... rather than overriding each individually. This is done by allowing $-style variables in the dirs. These are expanded by textual substitution (see substPathTemplate). A few of these installation directories are split into two components, the dir and subdir. The full installation path is formed by combining the two together with /. The reason for this is compatibility with other Unix build systems which also support --libdir and --datadir. We would like users to be able to configure --libdir=/usr/lib64 for example but because by default we want to support installing multiple versions of packages and building the same package for multiple compilers we append the libsubdir to get: /usr/lib64/$libname/$compiler. An additional complication is the need to support relocatable packages on systems which support such things, like Windows.

10. data InstallDirs dir

    Cabal	Distribution.Simple.InstallDirs

    The directories where we will install files for packages. We have several different directories for different types of files since many systems have conventions whereby different types of files in a package are installed in different directories. This is particularly the case on Unix style systems.

Page 234 of many | Previous | Next