ModuleCabal-3.16.0.0Haskell2010
Distribution.Simple.BuildPaths
A bunch of dirs, paths and file names used for intermediate build steps.
- 42 values
- PackageCabal-3.16.0.0
- Exports42
- LanguageHaskell2010
- LicenceBSD-3-Clause
- SourceBuildPaths.hs
Build info json file, generated in every build
This is the name of the directory in which the generated haddocks
should be stored. It does not include the distdochtml prefix.
It is also used by `haddock-project` when constructing its output directory.
This is the name of the directory in which the generated haddocks for
a (sub)library should be stored. It does not include the distdochtml
prefix.
It is also used by `haddock-project` when constructing its output directory.
The directory to which generated haddock documentation should be written.
The directory in which we put auto-generated modules for EVERY component in the package.
The directory in which we put auto-generated modules for a particular component.
The name of the auto-generated Paths_* module associated with a package
The name of the auto-generated PackageInfo_* module associated with a package
A name of a (sub)library used by haddock.
File path of the ".haddock" file.
Create a library name for a static library from a given name.
Prepends lib and appends the static library extension (.a).
Default extension for executable files on the current platform.
(typically "" on Unix and "exe" on Windows or OS/2)
Extension for object files. For GHC the extension is "o".
Extension for dynamically linked (or shared) libraries
(typically "so" on Unix and "dll" on Windows)
Extension for static libraries
TODO: Here, as well as in dllExtension, it's really the target OS that we're interested in, not the build OS.
Source files & build directories
11 declarationsThe directory where we put build results for an executable
The directory where we put build results for a foreign library
The name of the stub executable associated with a library TestSuite.
The directory where we put build results for a test suite
The directory where we put build results for a benchmark suite