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.
-
Cabal Distribution.Simple.InstallDirs No documentation available.
-
Cabal Distribution.Simple.InstallDirs Convert from abstract install directories to actual absolute ones by substituting for all the variables in the abstract paths, to get real absolute path.
combineInstallDirs :: (a -> b -> c) -> InstallDirs a -> InstallDirs b -> InstallDirs cCabal Distribution.Simple.InstallDirs No documentation available.
defaultInstallDirs :: CompilerFlavor -> Bool -> Bool -> IO InstallDirTemplatesCabal Distribution.Simple.InstallDirs No documentation available.
defaultInstallDirs' :: Bool -> CompilerFlavor -> Bool -> Bool -> IO InstallDirTemplatesCabal Distribution.Simple.InstallDirs No documentation available.
installDirsTemplateEnv :: InstallDirs PathTemplate -> PathTemplateEnvCabal Distribution.Simple.InstallDirs No documentation available.
-
Cabal Distribution.Simple.InstallDirs Check which of the paths are relative to the installation $prefix. If any of the paths are not relative, ie they are absolute paths, then it prevents us from making a relocatable package (also known as a "prefix independent" package).
substituteInstallDirTemplates :: PathTemplateEnv -> InstallDirTemplates -> InstallDirTemplatesCabal Distribution.Simple.InstallDirs Substitute the install dir templates into each other. To prevent cyclic substitutions, only some variables are allowed in particular dir templates. If out of scope vars are present, they are not substituted for. Checking for any remaining unsubstituted vars can be done as a subsequent operation. The reason it is done this way is so that in prefixRelativeInstallDirs we can replace prefix with the PrefixVar and get resulting PathTemplates that still have the PrefixVar in them. Doing this makes it each to check which paths are relative to the $prefix.
type
InstallDirTemplates = InstallDirs PathTemplateCabal Distribution.Simple.LocalBuildInfo 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.
-
Cabal Distribution.Simple.LocalBuildInfo 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.