pi package:Cabal-syntax

Pixar, Pixar License, SPDX License List 3.23, SPDX License List 3.25, SPDX License List 3.26
This has an enumeration of the various compilers that Cabal knows about. It also specifies the default compiler. Sadly you'll often see code that does case analysis on this compiler flavour enumeration like:
case compilerFlavor comp of
GHC -> GHC.getInstalledPackages verbosity packageDb progdb
Obviously it would be better to use the proper Compiler abstraction because that would keep all the compiler-specific code together. Unfortunately we cannot make this change yet without breaking the UserHooks api, which would break all custom Setup.hs files, so for the moment we just have to live with this deficiency. If you're interested, see ticket #57.
Compiler information used for resolving configurations. Some fields can be set to Nothing to indicate that the information is unknown.
PerCompilerFlavor carries only info per GHC and GHCJS Cabal parses only ghc-options and ghcjs-options, others are omitted.
Tag for distinguishing incompatible ABI's on the same architecture/os.
Other implementations that this compiler claims to be compatible with, if known.
Supported extensions, if known.
Compiler flavour and version.
Supported language standards, if known.
The default compiler flavour to pick when compiling stuff. This defaults to the compiler used to build the Cabal lib. However if it's not a recognised compiler then it's Nothing and the user will have to specify which compiler they want.
Make a CompilerInfo of which only the known information is its CompilerId, its AbiTag and that it does not claim to be compatible with other compiler id's.
Adobe-Utopia, Adobe Utopia Font License, SPDX License List 3.23, SPDX License List 3.25, SPDX License List 3.26