Hoogle Search
Within LTS Haskell 24.67 (ghc-9.10.3)
Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.
-
Cabal Distribution.Simple.BuildTarget No documentation available.
getAllInternalToolDependencies :: PackageDescription -> BuildInfo -> [UnqualComponentName]Cabal Distribution.Simple.BuildToolDepends Get internal "build-tool-depends", along with internal "build-tools" This is a tiny function, but used in a number of places. The same restrictions that apply to isInternal also apply to this function.
getAllToolDependencies :: PackageDescription -> BuildInfo -> [ExeDependency]Cabal Distribution.Simple.BuildToolDepends Get everything from "build-tool-depends", along with entries from "build-tools" that we know how to desugar. This should almost always be used instead of just accessing the buildToolDepends field directly.
-
Cabal Distribution.Simple.Command No documentation available.
defaultCommandFallback :: [Command action] -> String -> [String] -> IO (CommandParse action)Cabal Distribution.Simple.Command No documentation available.
ProfDetailAllFunctions :: ProfDetailLevelCabal Distribution.Simple.Compiler No documentation available.
-
Cabal Distribution.Simple.Configure List all installed packages in the given package databases. Non-existent package databases do not cause errors, they just get skipped with a warning and treated as empty ones, since technically they do not contain any package.
-
Cabal Distribution.Simple.Configure Looks up the InstalledPackageInfo of the given UnitIds from the PackageDBStack in the LocalBuildInfo.
-
Cabal Distribution.Simple.Configure A set of files (or directories) that can be monitored to detect when there might have been a change in the installed packages.
getInternalLibraries :: GenericPackageDescription -> Set LibraryNameCabal Distribution.Simple.Configure Create a PackageIndex that makes *any libraries that might be* defined internally to this package look like installed packages, in case an executable should refer to any of them as dependencies. It must be *any libraries that might be* defined rather than the actual definitions, because these depend on conditionals in the .cabal file, and we haven't resolved them yet. finalizePD does the resolution of conditionals, and it takes internalPackageSet as part of its input.