Distribution.Types.LocalBuildConfig

Options passed to the configuration step. Needed to re-run configuration when .cabal is out of date

The final set of flags which were picked for this package

What components were enabled during configuration, and why.

The compiler we're building with

The platform we're building for

the filename containing the .cabal file, if available

WARNING WARNING WARNING Be VERY careful about using this function; we haven't deprecated it but using it could introduce subtle bugs related to HookedBuildInfo.

In principle, this is supposed to contain the resolved package description, that does not contain any conditionals. However, it MAY NOT contain the description with a HookedBuildInfo applied to it; see HookedBuildInfo for the whole sordid saga. As much as possible, Cabal library should avoid using this parameter.

The installation directories for the various different kinds of files TODO: inplaceDirTemplates :: InstallDirs FilePath

What package database to use, global/user

For per-package builds-only: an extra 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).

All the components to build, ordered by topological sort, and with their INTERNAL dependencies over the intrapackage dependency graph. TODO: this is assumed to be short; otherwise we want some sort of ordered map.

A map from component name to all matching components. These coincide with componentGraph There may be more than one matching component because of backpack instantiations

The packages we were promised, but aren't already installed. MP: Perhaps this just needs to be a Set UnitId at this stage.

All the info about the installed packages that the current package depends on (directly or indirectly). The copy saved on disk does NOT include internal dependencies (because we just don't have enough information at this point to have an InstalledPackageInfo for an internal dep), but we will often update it with the internal dependencies; see for example build. (This admonition doesn't apply for per-component builds.)

Information that is available after configuring the package itself, before looking at individual components.

Information about individual components in the package determined after the configure step.

Extra args on the command line for the configuration step. Needed to re-run configuration when .cabal is out of date

Location and args for all programs

Options to control the build, e.g. whether to enable profiling or to enable program coverage.

Whether to build normal libs.

Whether to build profiling versions of libs.

Whether to build shared versions of libs.

Whether to build static versions of libs (with all other libs rolled in)

Whether to link executables dynamically

Whether to link executables fully statically

Whether to build executables for profiling.

Level of automatic profile detail.

Level of automatic profile detail.

Whether to build with optimization (if available).

Whether to emit debug info (if available).

Whether to build libs suitable for use with GHCi.

Use -split-sections with GHC, if available

Use -split-objs with GHC, if available

Whether to strip executables during install

Whether to strip libraries during install

Whether to enable executable program coverage

Whether to enable library program coverage

Whether to build a relocatable package