Hoogle Search
Within LTS Haskell 24.45 (ghc-9.10.3)
Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.
PreBuildComponentInputs :: BuildingWhat -> LocalBuildInfo -> TargetInfo -> PreBuildComponentInputsCabal Distribution.Simple.Build.Inputs No documentation available.
module Distribution.Simple.Build.
PackageInfoModule Generating the PackageInfo_pkgname module. This is a module that Cabal generates for the benefit of packages. It enables them to find their package informations.
module Distribution.Simple.Build.
PathsModule Generating the Paths_pkgname module. This is a module that Cabal generates for the benefit of packages. It enables them to find their version number and find any installed data files at runtime. This code should probably be split off into another module.
-
Cabal Distribution.Simple.Command No documentation available.
-
Cabal Distribution.Simple.Compiler Some compilers have a notion of a database of available packages. For some there is just one global db of packages, other compilers support a per-user or an arbitrary db specified at some location in the file system. This can be used to build isolated environments of packages, for example to build a collection of related packages without installing them globally.
type
PackageDBStack = [PackageDB]Cabal Distribution.Simple.Compiler We typically get packages from several databases, and stack them together. This type lets us be explicit about that stacking. For example typical stacks include:
[GlobalPackageDB] [GlobalPackageDB, UserPackageDB] [GlobalPackageDB, SpecificPackageDB "package.conf.inplace"]
Note that the GlobalPackageDB is invariably at the bottom since it contains the rts, base and other special compiler-specific packages. We are not restricted to using just the above combinations. In particular we can use several custom package dbs and the user package db together. When it comes to writing, the top most (last) package is used.ProfDetailAllFunctions :: ProfDetailLevelCabal Distribution.Simple.Compiler No documentation available.
ProfDetailDefault :: ProfDetailLevelCabal Distribution.Simple.Compiler No documentation available.
ProfDetailExportedFunctions :: ProfDetailLevelCabal Distribution.Simple.Compiler No documentation available.
-
Cabal Distribution.Simple.Compiler Some compilers (notably GHC) support profiling and can instrument programs so the system can account costs to different functions. There are different levels of detail that can be used for this accounting. For compilers that do not support this notion or the particular detail levels, this is either ignored or just capped to some similar level they do support.