conf package:Cabal

configureComponentLocalBuildInfos :: Verbosity -> Bool -> ComponentRequestedSpec -> Bool -> Flag String -> Flag ComponentId -> PackageDescription -> ([PreExistingComponent], [ConfiguredPromisedComponent]) -> FlagAssignment -> [(ModuleName, Module)] -> InstalledPackageIndex -> Compiler -> LogProgress ([ComponentLocalBuildInfo], InstalledPackageIndex)

Over-ride this hook to get different behavior during configure.

configCompilerAuxEx :: ConfigFlags -> IO (Compiler, Platform, ProgramDb)

Cabal Distribution.Simple.Configure

configCompilerEx :: Maybe CompilerFlavor -> Maybe FilePath -> Maybe FilePath -> ProgramDb -> Verbosity -> IO (Compiler, Platform, ProgramDb)

Cabal Distribution.Simple.Configure

configure :: (GenericPackageDescription, HookedBuildInfo) -> ConfigFlags -> IO LocalBuildInfo

Cabal Distribution.Simple.Configure

Perform the "./setup configure" action. Returns the .setup-config file.

configure_setupHooks :: ConfigureHooks -> (GenericPackageDescription, HookedBuildInfo) -> ConfigFlags -> IO LocalBuildInfo

Cabal Distribution.Simple.Configure

configure :: Verbosity -> Maybe FilePath -> Maybe FilePath -> ProgramDb -> IO (Compiler, Maybe Platform, ProgramDb)

Cabal Distribution.Simple.GHC Distribution.Simple.GHCJS Distribution.Simple.HaskellSuite

configureAllKnownPrograms :: Verbosity -> ProgramDb -> IO ProgramDb

Cabal Distribution.Simple.Program Distribution.Simple.Program.Db

Try to configure all the known programs that have not yet been configured.

configureProgram :: Verbosity -> Program -> ProgramDb -> IO ProgramDb

Cabal Distribution.Simple.Program Distribution.Simple.Program.Db

Try to configure a specific program and add it to the program database. If the program is already included in the collection of unconfigured programs, then we use any user-supplied location and arguments. If the program gets configured successfully, it gets added to the configured collection. Note that it is not a failure if the program cannot be configured. It's only a failure if the user supplied a location and the program could not be found at that location. The reason for it not being a failure at this stage is that we don't know up front all the programs we will need, so we try to configure them all. To verify that a program was actually successfully configured use requireProgram.

configureUnconfiguredProgram :: Verbosity -> Program -> ProgramDb -> IO (Maybe ConfiguredProgram)

Cabal Distribution.Simple.Program.Db

Try to configure a specific program. If the program is already included in the collection of unconfigured programs then we use any user-supplied location and arguments.

configuredPrograms :: ProgramDb -> [ConfiguredProgram]

Cabal Distribution.Simple.Program.Db

List all configured programs.

configuredProgs :: ProgramDb -> ConfiguredProgs

Cabal Distribution.Simple.Program.Db

configAllowDependingOnPrivateLibs :: ConfigFlags -> Flag Bool

Cabal Distribution.Simple.Setup

Allow depending on private sublibraries. This is used by external tools (like cabal-install) so they can add multiple-public-libraries compatibility to older ghcs by checking visibility externally.

configBenchmarks :: ConfigFlags -> Flag Bool

Cabal Distribution.Simple.Setup

Enable benchmark compilation

configCID :: ConfigFlags -> Flag ComponentId

Cabal Distribution.Simple.Setup

explicit CID to be used

configCommonFlags :: ConfigFlags -> !CommonSetupFlags

Cabal Distribution.Simple.Setup

configConfigurationsFlags :: ConfigFlags -> FlagAssignment

Cabal Distribution.Simple.Setup

configConfigureArgs :: ConfigFlags -> [String]

Cabal Distribution.Simple.Setup

Extra arguments to configure

configConstraints :: ConfigFlags -> [PackageVersionConstraint]

Cabal Distribution.Simple.Setup

Additional constraints for dependencies.

configCoverage :: ConfigFlags -> Flag Bool

Cabal Distribution.Simple.Setup

Enable program coverage

configCoverageFor :: ConfigFlags -> Flag [UnitId]

Cabal Distribution.Simple.Setup

The list of libraries to be included in the hpc coverage report for testsuites run with --enable-coverage. Notably, this list must exclude indefinite libraries and instantiations because HPC does not support backpack (Nov. 2023).

configDebugInfo :: ConfigFlags -> Flag DebugInfoLevel

Cabal Distribution.Simple.Setup

Emit debug info.

configDependencies :: ConfigFlags -> [GivenComponent]

Cabal Distribution.Simple.Setup

The packages depended on which already exist

configDeterministic :: ConfigFlags -> Flag Bool

Cabal Distribution.Simple.Setup

be as deterministic as possible (e.g., invariant over GHC, database, etc). Used by the test suite

configDumpBuildInfo :: ConfigFlags -> Flag DumpBuildInfo

Cabal Distribution.Simple.Setup

Should we dump available build information on build? Dump build information to disk before attempting to build, tooling can parse these files and use them to compile the source files themselves.