If true, after a build failure, continue to build other unaffected keep-going : boolean ¶ -keep-going ¶ Default value j2 is also supported a bare -jobs or -j is equivalent The command line variant of this field is -jobs=2 a short form Package building is often quite parallel, so turning on parallelism Specified, run the number of jobs equal to the number of CPUs. Run nat jobs simultaneously when building. jobs : nat or $ncpus ¶ -jobs =n, -jn, -jobs =$ncpus ¶ Default value The command line variant of this field is -verbose=2 a shortįorm -v2 is also supported. Package, and thus apply globally: verbose : nat ¶ -verbose =n, -vn ¶ Default valueĬontrol the verbosity of cabal commands, valid values are from 0 The following top-level configuration options are not specific to any Of a local package, the local package is preferentially used.įor subdirectories to be considered local packages, the following setting (including external ones from Hackage) depend on a package with the name There is no command line variant of this field.Īll local packages are vendored, in the sense that if other packages Should be considered local packages.] (Not implemented) [STRIKEOUT:Specifies a list of external packages from Hackage which extra-packages : package list with version bounds (comma separated) ¶ There is no command line variant of this field. They are placed in a subdirectory, but not error if there aren’t any. Is to make it so that vendored packages can be automatically picked up if The intended use-case for optional-packages If we glob for a package, it is permissible for the glob to match against Like packages, specifies a list of package locationsĬontaining local packages to be built. optional-packages : package location list (space or comma-separated) ¶ Default value There is no command line variant of this field see #3585. URL, representing the path to a remote tarball to be downloaded Subdirectories, as well as the Cabal projects in the parent
cabal), or (c) tarballs which contain Cabalįor example, to match all Cabal files in all More (a) directories containing a (single) Cabal file, (b) Cabalįiles (extension.
They can specify a glob-style wildcards, which must match one or They can specify a Cabal file, or a directory containing a Cabalįile, e.g., packages: Cabal cabal-install/cabal-install.cabal. Specifies the list of package locations which contain the local Project are: packages : package location list (space or comma separated) ¶ Default value The following top-level options specify what the local packages of a ~/.cabal/config (the user-wide global configuration)Ĭabal.project (the project configuration)Ĭ (the output of cabal v2-freeze)Ĭ (the output of cabal v2-configure)
#CABAL CODE ZERO FULL#
The full configuration of a project is determined by combining theįollowing sources (later entries override earlier ones): For example,Ĭabal v2-configure -enable-profiling will write out a project
#CABAL CODE ZERO INSTALL#
Line flags that cabal install and other commands take. In general, the accepted field names coincide with the accepted command
0 kommentar(er)
