€cdocutils.nodes document q)q}q(U nametypesq}q(X executablesqNXpvpqˆX&accessing data files from package codeqNX quickstartq NX.example: a package containing a simple libraryq NXthe point of packagesq NX6explicit dependencies and automatic package managementq NXdownloading a package's sourceq NXpackage descriptionsqNXlibraryqNX test suitesqNXpackage versioning policyqˆXmodules included in the packageqNXhoogleqˆX*listing outdated dependency version boundsqNXconditional compilationqNX$generating dependency version boundsqNXhackageqˆXediting the .cabal fileqNXrunning executablesqNXsystem-dependent parametersqNXhscolourqˆXmore elaborate solutionsqˆX/meaning of field values when using conditionalsqNXfreezing dependency versionsqNXhaddockqˆXbuilding the packageq NXaccessing the package versionq!NXdeveloping packagesq"NX1example: a package containing executable programsq#NXalexq$ˆX"resolution of conditions and flagsq%NXrunning benchmarksq&NXconfiguration flagsq'NX conditionsq(NXcpphsq)ˆXhappyq*ˆXforeign librariesq+NXsource repositoriesq,NX-example: package using detailed-0.9 interfaceq-NXpackage propertiesq.NXcreating a packageq/NXghcq0ˆXpackage names and versionsq1NXfoo-bench.cabalq2ˆXexample: using autoconfq3NXAexample: using explicit braces rather than indentation for layoutq4NXmore complex packagesq5NX next stepsq6NXunit of distributionq7NX$modules imported from other packagesq8NXmodules and preprocessorsq9NXlayoutq:NX?example: a package containing a library and executable programsq;NX buildtoolsbcq<ˆXusing "cabal init"q=NX portabilityq>NXrunning test suitesq?NXbuild informationq@NX(kinds of package: cabal vs ghc vs systemqANXpackage conceptsqBNXconditional blocksqCNXcustom setup scriptsqDNXhaskellqEˆXopening an interpreter sessionqFNX benchmarksqGNX3example: package using exitcode-stdio-1.0 interfaceqHNXautogenerated modulesqINXfind these files at run-timeqJˆX2see below for backwards compatibility information.qKˆXconfigurationsqLNuUsubstitution_defsqM}qNUparse_messagesqO]qP(cdocutils.nodes system_message qQ)qR}qS(U rawsourceqTUUparentqUcdocutils.nodes section qV)qW}qX(hTUU referencedqYKhUhV)qZ}q[(hTUhUhV)q\}q](hTUhYKhUhV)q^}q_(hTUhUhUsourceq`XE/home/refold/code/haskell/cabal-2.0/Cabal/doc/developing-packages.rstqaUtagnameqbUsectionqcU attributesqd}qe(Udupnamesqf]Uclassesqg]Ubackrefsqh]Uidsqi]qjUdeveloping-packagesqkaUnamesql]qmh"auUlineqnMÄUdocumentqohUchildrenqp]qq(cdocutils.nodes title qr)qs}qt(hTXDeveloping packagesquhUh^h`hahbUtitleqvhd}qw(hf]hg]hh]hi]hl]uhnMÄhohhp]qxcdocutils.nodes Text qyXDeveloping packagesqz…q{}q|(hThuh`NhnNhohhUhsubaubcdocutils.nodes paragraph q})q~}q(hTX`The Cabal package is the unit of distribution. When installed, its purpose is to make available:q€hUh^h`hahbU paragraphqhd}q‚(hf]hg]hh]hi]hl]uhnMÆhohhp]qƒhyX`The Cabal package is the unit of distribution. When installed, its purpose is to make available:q„…q…}q†(hTh€h`NhnNhohhUh~ubaubcdocutils.nodes bullet_list q‡)qˆ}q‰(hTUhUh^h`hahbU bullet_listqŠhd}q‹(UbulletqŒX-hi]hh]hf]hg]hl]uhnMÉhohhp]q(cdocutils.nodes list_item qŽ)q}q(hTXOne or more Haskell programs. hUhˆh`hahbU list_itemq‘hd}q’(hf]hg]hh]hi]hl]uhnNhohhp]q“h})q”}q•(hTXOne or more Haskell programs.q–hUhh`hahbhhd}q—(hf]hg]hh]hi]hl]uhnMÉhp]q˜hyXOne or more Haskell programs.q™…qš}q›(hTh–hUh”ubaubaubhŽ)qœ}q(hTX;At most one library, exposing a number of Haskell modules. hUhˆh`hahbh‘hd}qž(hf]hg]hh]hi]hl]uhnNhohhp]qŸh})q }q¡(hTX:At most one library, exposing a number of Haskell modules.q¢hUhœh`hahbhhd}q£(hf]hg]hh]hi]hl]uhnMËhp]q¤hyX:At most one library, exposing a number of Haskell modules.q¥…q¦}q§(hTh¢hUh ubaubaubeubh})q¨}q©(hTX­However having both a library and executables in a package does not work very well; if the executables depend on the library, they must explicitly list all the modules they directly or indirectly import from that library. Fortunately, starting with Cabal 1.8.0.4, executables can also declare the package that they are in as a dependency, and Cabal will treat them as if they were in another package that depended on the library.qªhUh^h`hahbhhd}q«(hf]hg]hh]hi]hl]uhnMÍhohhp]q¬hyX­However having both a library and executables in a package does not work very well; if the executables depend on the library, they must explicitly list all the modules they directly or indirectly import from that library. Fortunately, starting with Cabal 1.8.0.4, executables can also declare the package that they are in as a dependency, and Cabal will treat them as if they were in another package that depended on the library.q­…q®}q¯(hThªh`NhnNhohhUh¨ubaubh})q°}q±(hTX×Internally, the package may consist of much more than a bunch of Haskell modules: it may also have C source code and header files, source code meant for preprocessing, documentation, test cases, auxiliary tools etc.q²hUh^h`hahbhhd}q³(hf]hg]hh]hi]hl]uhnMÕhohhp]q´hyX×Internally, the package may consist of much more than a bunch of Haskell modules: it may also have C source code and header files, source code meant for preprocessing, documentation, test cases, auxiliary tools etc.qµ…q¶}q·(hTh²h`NhnNhohhUh°ubaubh})q¸}q¹(hTXWA package is identified by a globally-unique *package name*, which consists of one or more alphanumeric words separated by hyphens. To avoid ambiguity, each of these words should contain at least one letter. Chaos will result if two distinct packages with the same name are installed on the same system. A particular version of the package is distinguished by a *version number*, consisting of a sequence of one or more integers separated by dots. These can be combined to form a single text string called the *package ID*, using a hyphen to separate the name from the version, e.g. "``HUnit-1.1``".hUh^h`hahbhhd}qº(hf]hg]hh]hi]hl]uhnMÙhohhp]q»(hyX-A package is identified by a globally-unique q¼…q½}q¾(hTX-A package is identified by a globally-unique h`NhnNhohhUh¸ubcdocutils.nodes emphasis q¿)qÀ}qÁ(hTX*package name*hd}qÂ(hf]hg]hh]hi]hl]uhUh¸hp]qÃhyX package nameqÄ…qÅ}qÆ(hTUhUhÀubahbUemphasisqÇubhyX/, which consists of one or more alphanumeric words separated by hyphens. To avoid ambiguity, each of these words should contain at least one letter. Chaos will result if two distinct packages with the same name are installed on the same system. A particular version of the package is distinguished by a qÈ…qÉ}qÊ(hTX/, which consists of one or more alphanumeric words separated by hyphens. To avoid ambiguity, each of these words should contain at least one letter. Chaos will result if two distinct packages with the same name are installed on the same system. A particular version of the package is distinguished by a h`NhnNhohhUh¸ubh¿)qË}qÌ(hTX*version number*hd}qÍ(hf]hg]hh]hi]hl]uhUh¸hp]qÎhyXversion numberqÏ…qÐ}qÑ(hTUhUhËubahbhÇubhyX„, consisting of a sequence of one or more integers separated by dots. These can be combined to form a single text string called the qÒ…qÓ}qÔ(hTX„, consisting of a sequence of one or more integers separated by dots. These can be combined to form a single text string called the h`NhnNhohhUh¸ubh¿)qÕ}qÖ(hTX *package ID*hd}q×(hf]hg]hh]hi]hl]uhUh¸hp]qØhyX package IDqÙ…qÚ}qÛ(hTUhUhÕubahbhÇubhyX@, using a hyphen to separate the name from the version, e.g. “qÜ…qÝ}qÞ(hTX>, using a hyphen to separate the name from the version, e.g. "h`NhnNhohhUh¸ubcdocutils.nodes literal qß)qà}qá(hTX ``HUnit-1.1``hd}qâ(hf]hg]hh]hi]hl]uhUh¸hp]qãhyX HUnit-1.1qä…qå}qæ(hTUhUhàubahbUliteralqçubhyXâ€.qè…qé}qê(hTX".h`NhnNhohhUh¸ubeubcdocutils.nodes note që)qì}qí(hTXTPackages are not part of the Haskell language; they simply populate the hierarchical space of module names. In GHC 6.6 and later a program may contain multiple modules with the same name if they come from separate packages; in all other current Haskell systems packages may not overlap in the modules they provide, including hidden modules.hUh^h`hahbUnoteqîhd}qï(hf]hg]hh]hi]hl]uhnNhohhp]qðh})qñ}qò(hTXTPackages are not part of the Haskell language; they simply populate the hierarchical space of module names. In GHC 6.6 and later a program may contain multiple modules with the same name if they come from separate packages; in all other current Haskell systems packages may not overlap in the modules they provide, including hidden modules.qóhUhìh`hahbhhd}qô(hf]hg]hh]hi]hl]uhnMåhp]qõhyXTPackages are not part of the Haskell language; they simply populate the hierarchical space of module names. In GHC 6.6 and later a program may contain multiple modules with the same name if they come from separate packages; in all other current Haskell systems packages may not overlap in the modules they provide, including hidden modules.qö…q÷}qø(hThóhUhñubaubaubhV)qù}qú(hTUhUh^h`hahbhchd}qû(hf]hg]hh]hi]qüUcreating-a-packageqýahl]qþh/auhnMìhohhp]qÿ(hr)r}r(hTXCreating a packagerhUhùh`hahbhvhd}r(hf]hg]hh]hi]hl]uhnMìhohhp]rhyXCreating a packager…r}r(hTjh`NhnNhohhUjubaubh})r}r (hTX§Suppose you have a directory hierarchy containing the source files that make up your package. You will need to add two more files to the root directory of the package:r hUhùh`hahbhhd}r (hf]hg]hh]hi]hl]uhnMîhohhp]r hyX§Suppose you have a directory hierarchy containing the source files that make up your package. You will need to add two more files to the root directory of the package:r …r}r(hTj h`NhnNhohhUjubaubcdocutils.nodes definition_list r)r}r(hTUhUhùh`hahbUdefinition_listrhd}r(hf]hg]hh]hi]hl]uhnNhohhp]r(cdocutils.nodes definition_list_item r)r}r(hTX¨:file:`{package}.cabal` a Unicode UTF-8 text file containing a package description. For details of the syntax of this file, see the section on `package descriptions`_. hUjh`hahbUdefinition_list_itemrhd}r(hf]hg]hh]hi]hl]uhnMõhp]r(cdocutils.nodes term r)r}r(hTX:file:`{package}.cabal`rhUjh`hahbUtermr hd}r!(hf]hg]hh]hi]hl]uhnMõhp]r"hß)r#}r$(hTX package.cabalhd}r%(hi]hh]hf]hg]r&Xfiler'aUrolej'hl]uhUjhp]r((h¿)r)}r*(hTXpackagehd}r+(hf]hg]hh]hi]hl]uhUj#hp]r,hyXpackager-…r.}r/(hTUhUj)ubahbhÇubhyX.cabalr0…r1}r2(hTX.cabalhUj#ubehbhçubaubcdocutils.nodes definition r3)r4}r5(hTUhd}r6(hf]hg]hh]hi]hl]uhUjhp]r7h})r8}r9(hTXa Unicode UTF-8 text file containing a package description. For details of the syntax of this file, see the section on `package descriptions`_.hUj4h`hahbhhd}r:(hf]hg]hh]hi]hl]uhnMóhp]r;(hyXwa Unicode UTF-8 text file containing a package description. For details of the syntax of this file, see the section on r<…r=}r>(hTXwa Unicode UTF-8 text file containing a package description. For details of the syntax of this file, see the section on hUj8ubcdocutils.nodes reference r?)r@}rA(hTX`package descriptions`_UresolvedrBKhUj8hbU referencerChd}rD(UnameXpackage descriptionshi]hh]hf]hg]hl]UrefidrEUpackage-descriptionsrFuhp]rGhyXpackage descriptionsrH…rI}rJ(hTUhUj@ubaubhyX.…rK}rL(hTX.hUj8ubeubahbU definitionrMubeubj)rN}rO(hTXÞ:file:`Setup.hs` a single-module Haskell program to perform various setup tasks (with the interface described in the section on :ref:`installing-packages`). This module should import only modules that will be present in all Haskell implementations, including modules of the Cabal library. The content of this file is determined by the :pkg-field:`build-type` setting in the ``.cabal`` file. In most cases it will be trivial, calling on the Cabal library to do most of the work. hUjh`hahbjhd}rP(hf]hg]hh]hi]hl]uhnMþhohhp]rQ(j)rR}rS(hTX:file:`Setup.hs`rThUjNh`hahbj hd}rU(hf]hg]hh]hi]hl]uhnMþhp]rVhß)rW}rX(hTXSetup.hshd}rY(hi]hh]hf]hg]rZXfiler[aUrolej[hl]uhUjRhp]r\hyXSetup.hsr]…r^}r_(hTXSetup.hshUjWubahbhçubaubj3)r`}ra(hTUhd}rb(hf]hg]hh]hi]hl]uhUjNhp]rch})rd}re(hTXÌa single-module Haskell program to perform various setup tasks (with the interface described in the section on :ref:`installing-packages`). This module should import only modules that will be present in all Haskell implementations, including modules of the Cabal library. The content of this file is determined by the :pkg-field:`build-type` setting in the ``.cabal`` file. In most cases it will be trivial, calling on the Cabal library to do most of the work.hUj`h`hahbhhd}rf(hf]hg]hh]hi]hl]uhnMøhp]rg(hyXoa single-module Haskell program to perform various setup tasks (with the interface described in the section on rh…ri}rj(hTXoa single-module Haskell program to perform various setup tasks (with the interface described in the section on hUjdubcsphinx.addnodes pending_xref rk)rl}rm(hTX:ref:`installing-packages`rnhUjdh`hahbU pending_xrefrohd}rp(UreftypeXrefUrefwarnrqˆU reftargetrrXinstalling-packagesU refdomainXstdrshi]hh]U refexplicit‰hf]hg]hl]UrefdocrtXdeveloping-packagesruuhnMøhp]rvcdocutils.nodes inline rw)rx}ry(hTjnhd}rz(hf]hg]r{(Uxrefr|jsXstd-refr}ehh]hi]hl]uhUjlhp]r~hyXinstalling-packagesr…r€}r(hTUhUjxubahbUinliner‚ubaubhyXµ). This module should import only modules that will be present in all Haskell implementations, including modules of the Cabal library. The content of this file is determined by the rƒ…r„}r…(hTXµ). This module should import only modules that will be present in all Haskell implementations, including modules of the Cabal library. The content of this file is determined by the hUjdubjk)r†}r‡(hTX:pkg-field:`build-type`rˆhUjdh`hahbjohd}r‰(UreftypeX pkg-fieldjqˆjrX build-typeU refdomainXcabalrŠhi]hh]U refexplicit‰hf]hg]hl]jtjuUcabal:pkg-sectionr‹NuhnMøhp]rŒhß)r}rŽ(hTjˆhd}r(hf]hg]r(j|jŠXcabal-pkg-fieldr‘ehh]hi]hl]uhUj†hp]r’hyX build-typer“…r”}r•(hTUhUjubahbhçubaubhyX setting in the r–…r—}r˜(hTX setting in the hUjdubhß)r™}rš(hTX ``.cabal``hd}r›(hf]hg]hh]hi]hl]uhUjdhp]rœhyX.cabalr…rž}rŸ(hTUhUj™ubahbhçubhyX] file. In most cases it will be trivial, calling on the Cabal library to do most of the work.r …r¡}r¢(hTX] file. In most cases it will be trivial, calling on the Cabal library to do most of the work.hUjdubeubahbjMubeubeubh})r£}r¤(hTXªOnce you have these, you can create a source bundle of this directory for distribution. Building of the package is discussed in the section on :ref:`installing-packages`.hUhùh`hahbhhd}r¥(hf]hg]hh]hi]hl]uhnMhohhp]r¦(hyXOnce you have these, you can create a source bundle of this directory for distribution. Building of the package is discussed in the section on r§…r¨}r©(hTXOnce you have these, you can create a source bundle of this directory for distribution. Building of the package is discussed in the section on h`NhnNhohhUj£ubjk)rª}r«(hTX:ref:`installing-packages`r¬hUj£h`hahbjohd}r­(UreftypeXrefjqˆjrXinstalling-packagesU refdomainXstdr®hi]hh]U refexplicit‰hf]hg]hl]jtjuuhnMhp]r¯jw)r°}r±(hTj¬hd}r²(hf]hg]r³(j|j®Xstd-refr´ehh]hi]hl]uhUjªhp]rµhyXinstalling-packagesr¶…r·}r¸(hTUhUj°ubahbj‚ubaubhyX.…r¹}rº(hTX.h`NhnNhohhUj£ubeubh})r»}r¼(hTX¤One of the purposes of Cabal is to make it easier to build a package with different Haskell implementations. So it provides abstractions of features present in different Haskell implementations and wherever possible it is best to take advantage of these to increase portability. Where necessary however it is possible to use specific features of specific implementations. For example one of the pieces of information a package author can put in the package's ``.cabal`` file is what language extensions the code uses. This is far preferable to specifying flags for a specific compiler as it allows Cabal to pick the right flags for the Haskell implementation that the user picks. It also allows Cabal to figure out if the language extension is even supported by the Haskell implementation that the user picks. Where compiler-specific options are needed however, there is an "escape hatch" available. The developer can specify implementation-specific options and more generally there is a configuration mechanism to customise many aspects of how a package is built depending on the Haskell implementation, the Operating system, computer architecture and user-specified configuration flags.hUhùh`hahbhhd}r½(hf]hg]hh]hi]hl]uhnMhohhp]r¾(hyXÍOne of the purposes of Cabal is to make it easier to build a package with different Haskell implementations. So it provides abstractions of features present in different Haskell implementations and wherever possible it is best to take advantage of these to increase portability. Where necessary however it is possible to use specific features of specific implementations. For example one of the pieces of information a package author can put in the package’s r¿…rÀ}rÁ(hTXËOne of the purposes of Cabal is to make it easier to build a package with different Haskell implementations. So it provides abstractions of features present in different Haskell implementations and wherever possible it is best to take advantage of these to increase portability. Where necessary however it is possible to use specific features of specific implementations. For example one of the pieces of information a package author can put in the package's h`NhnNhohhUj»ubhß)rÂ}rÃ(hTX ``.cabal``hd}rÄ(hf]hg]hh]hi]hl]uhUj»hp]rÅhyX.cabalrÆ…rÇ}rÈ(hTUhUjÂubahbhçubhyXÓ file is what language extensions the code uses. This is far preferable to specifying flags for a specific compiler as it allows Cabal to pick the right flags for the Haskell implementation that the user picks. It also allows Cabal to figure out if the language extension is even supported by the Haskell implementation that the user picks. Where compiler-specific options are needed however, there is an “escape hatch†available. The developer can specify implementation-specific options and more generally there is a configuration mechanism to customise many aspects of how a package is built depending on the Haskell implementation, the Operating system, computer architecture and user-specified configuration flags.rÉ…rÊ}rË(hTXÏ file is what language extensions the code uses. This is far preferable to specifying flags for a specific compiler as it allows Cabal to pick the right flags for the Haskell implementation that the user picks. It also allows Cabal to figure out if the language extension is even supported by the Haskell implementation that the user picks. Where compiler-specific options are needed however, there is an "escape hatch" available. The developer can specify implementation-specific options and more generally there is a configuration mechanism to customise many aspects of how a package is built depending on the Haskell implementation, the Operating system, computer architecture and user-specified configuration flags.h`NhnNhohhUj»ubeubcdocutils.nodes literal_block rÌ)rÍ}rÎ(hTXÂname: Foo version: 1.0 library build-depends: base exposed-modules: Foo extensions: ForeignFunctionInterface ghc-options: -Wall if os(windows) build-depends: Win32hUhùh`hahbU literal_blockrÏhd}rÐ(U xml:spacerÑUpreserverÒhi]hh]hf]hg]hl]uhnMhohhp]rÓhyXÂname: Foo version: 1.0 library build-depends: base exposed-modules: Foo extensions: ForeignFunctionInterface ghc-options: -Wall if os(windows) build-depends: Win32rÔ…rÕ}rÖ(hTUhUjÍubaubhV)r×}rØ(hTUhUhùh`hahbhchd}rÙ(hf]hg]hh]hi]rÚU-example-a-package-containing-a-simple-libraryrÛahl]rÜh auhnM$hohhp]rÝ(hr)rÞ}rß(hTX.Example: A package containing a simple libraryràhUj×h`hahbhvhd}rá(hf]hg]hh]hi]hl]uhnM$hohhp]râhyX.Example: A package containing a simple libraryrã…rä}rå(hTjàh`NhnNhohhUjÞubaubh})ræ}rç(hTX=The HUnit package contains a file ``HUnit.cabal`` containing:rèhUj×h`hahbhhd}ré(hf]hg]hh]hi]hl]uhnM&hohhp]rê(hyX"The HUnit package contains a file rë…rì}rí(hTX"The HUnit package contains a file h`NhnNhohhUjæubhß)rî}rï(hTX``HUnit.cabal``hd}rð(hf]hg]hh]hi]hl]uhUjæhp]rñhyX HUnit.cabalrò…ró}rô(hTUhUjîubahbhçubhyX containing:rõ…rö}r÷(hTX containing:h`NhnNhohhUjæubeubjÌ)rø}rù(hTXêname: HUnit version: 1.1.1 synopsis: A unit testing framework for Haskell homepage: http://hunit.sourceforge.net/ category: Testing author: Dean Herington license: BSD3 license-file: LICENSE cabal-version: >= 1.10 build-type: Simple library build-depends: base >= 2 && < 4 exposed-modules: Test.HUnit.Base, Test.HUnit.Lang, Test.HUnit.Terminal, Test.HUnit.Text, Test.HUnit default-extensions: CPPhUj×h`hahbjÏhd}rú(jÑjÒhi]hh]hf]hg]hl]uhnM*hohhp]rûhyXêname: HUnit version: 1.1.1 synopsis: A unit testing framework for Haskell homepage: http://hunit.sourceforge.net/ category: Testing author: Dean Herington license: BSD3 license-file: LICENSE cabal-version: >= 1.10 build-type: Simple library build-depends: base >= 2 && < 4 exposed-modules: Test.HUnit.Base, Test.HUnit.Lang, Test.HUnit.Terminal, Test.HUnit.Text, Test.HUnit default-extensions: CPPrü…rý}rþ(hTUhUjøubaubh})rÿ}r(hTXand the following ``Setup.hs``:rhUj×h`hahbhhd}r(hf]hg]hh]hi]hl]uhnM;hohhp]r(hyXand the following r…r}r(hTXand the following h`NhnNhohhUjÿubhß)r}r(hTX ``Setup.hs``hd}r (hf]hg]hh]hi]hl]uhUjÿhp]r hyXSetup.hsr …r }r (hTUhUjubahbhçubhyX:…r}r(hTX:h`NhnNhohhUjÿubeubjÌ)r}r(hTX-import Distribution.Simple main = defaultMainhUj×h`hahbjÏhd}r(Ulinenosr‰UlanguagerXhaskelljÑjÒhi]hh]hf]Uhighlight_argsr}hg]hl]uhnM=hohhp]rhyX-import Distribution.Simple main = defaultMainr…r}r(hTUhUjubaubeubhV)r}r(hTUhUhùh`hahbhchd}r(hf]hg]hh]hi]rU0example-a-package-containing-executable-programsrahl]rh#auhnMChohhp]r (hr)r!}r"(hTX1Example: A package containing executable programsr#hUjh`hahbhvhd}r$(hf]hg]hh]hi]hl]uhnMChohhp]r%hyX1Example: A package containing executable programsr&…r'}r((hTj#h`NhnNhohhUj!ubaubjÌ)r)}r*(hTX–name: TestPackage version: 0.0 synopsis: Small package with two programs author: Angela Author license: BSD3 build-type: Simple cabal-version: >= 1.2 executable program1 build-depends: HUnit main-is: Main.hs hs-source-dirs: prog1 executable program2 main-is: Main.hs build-depends: HUnit hs-source-dirs: prog2 other-modules: UtilshUjh`hahbjÏhd}r+(jÑjÒhi]hh]hf]hg]hl]uhnMGhohhp]r,hyX–name: TestPackage version: 0.0 synopsis: Small package with two programs author: Angela Author license: BSD3 build-type: Simple cabal-version: >= 1.2 executable program1 build-depends: HUnit main-is: Main.hs hs-source-dirs: prog1 executable program2 main-is: Main.hs build-depends: HUnit hs-source-dirs: prog2 other-modules: Utilsr-…r.}r/(hTUhUj)ubaubh})r0}r1(hTX$with ``Setup.hs`` the same as above.r2hUjh`hahbhhd}r3(hf]hg]hh]hi]hl]uhnMZhohhp]r4(hyXwith r5…r6}r7(hTXwith h`NhnNhohhUj0ubhß)r8}r9(hTX ``Setup.hs``hd}r:(hf]hg]hh]hi]hl]uhUj0hp]r;hyXSetup.hsr<…r=}r>(hTUhUj8ubahbhçubhyX the same as above.r?…r@}rA(hTX the same as above.h`NhnNhohhUj0ubeubeubhV)rB}rC(hTUhYKhUhùh`hahbhchd}rD(hf]rEX?example: a package containing a library and executable programsrFahg]hh]hi]rGU>example-a-package-containing-a-library-and-executable-programsrHahl]uhnM]hohhp]rI(hr)rJ}rK(hTX?Example: A package containing a library and executable programsrLhUjBh`hahbhvhd}rM(hf]hg]hh]hi]hl]uhnM]hohhp]rNhyX?Example: A package containing a library and executable programsrO…rP}rQ(hTjLh`NhnNhohhUjJubaubjÌ)rR}rS(hTXÓname: TestPackage version: 0.0 synopsis: Package with library and two programs license: BSD3 author: Angela Author build-type: Simple cabal-version: >= 1.2 library build-depends: HUnit exposed-modules: A, B, C executable program1 main-is: Main.hs hs-source-dirs: prog1 other-modules: A, B executable program2 main-is: Main.hs hs-source-dirs: prog2 other-modules: A, C, UtilshUjBh`hahbjÏhd}rT(jÑjÒhi]hh]hf]hg]hl]uhnMahohhp]rUhyXÓname: TestPackage version: 0.0 synopsis: Package with library and two programs license: BSD3 author: Angela Author build-type: Simple cabal-version: >= 1.2 library build-depends: HUnit exposed-modules: A, B, C executable program1 main-is: Main.hs hs-source-dirs: prog1 other-modules: A, B executable program2 main-is: Main.hs hs-source-dirs: prog2 other-modules: A, C, UtilsrV…rW}rX(hTUhUjRubaubh})rY}rZ(hTX‹with ``Setup.hs`` the same as above. Note that any library modules required (directly or indirectly) by an executable must be listed again.hUjBh`hahbhhd}r[(hf]hg]hh]hi]hl]uhnMwhohhp]r\(hyXwith r]…r^}r_(hTXwith h`NhnNhohhUjYubhß)r`}ra(hTX ``Setup.hs``hd}rb(hf]hg]hh]hi]hl]uhUjYhp]rchyXSetup.hsrd…re}rf(hTUhUj`ubahbhçubhyXz the same as above. Note that any library modules required (directly or indirectly) by an executable must be listed again.rg…rh}ri(hTXz the same as above. Note that any library modules required (directly or indirectly) by an executable must be listed again.h`NhnNhohhUjYubeubh})rj}rk(hTX–The trivial setup script used in these examples uses the *simple build infrastructure* provided by the Cabal library (see `Distribution.Simple <../release/cabal-latest/doc/API/Cabal/Distribution-Simple.html>`__). The simplicity lies in its interface rather that its implementation. It automatically handles preprocessing with standard preprocessors, and builds packages for all the Haskell implementations.hUjBh`hahbhhd}rl(hf]hg]hh]hi]hl]uhnMzhohhp]rm(hyX9The trivial setup script used in these examples uses the rn…ro}rp(hTX9The trivial setup script used in these examples uses the h`NhnNhohhUjjubh¿)rq}rr(hTX*simple build infrastructure*hd}rs(hf]hg]hh]hi]hl]uhUjjhp]rthyXsimple build infrastructureru…rv}rw(hTUhUjqubahbhÇubhyX$ provided by the Cabal library (see rx…ry}rz(hTX$ provided by the Cabal library (see h`NhnNhohhUjjubj?)r{}r|(hTXX`Distribution.Simple <../release/cabal-latest/doc/API/Cabal/Distribution-Simple.html>`__hd}r}(UnameXDistribution.SimpleUrefurir~X>../release/cabal-latest/doc/API/Cabal/Distribution-Simple.htmlhi]hh]hf]hg]hl]uhUjjhp]rhyXDistribution.Simpler€…r}r‚(hTUhUj{ubahbjCubhyXÄ). The simplicity lies in its interface rather that its implementation. It automatically handles preprocessing with standard preprocessors, and builds packages for all the Haskell implementations.rƒ…r„}r…(hTXÄ). The simplicity lies in its interface rather that its implementation. It automatically handles preprocessing with standard preprocessors, and builds packages for all the Haskell implementations.h`NhnNhohhUjjubeubh})r†}r‡(hTXThe simple build infrastructure can also handle packages where building is governed by system-dependent parameters, if you specify a little more (see the section on `system-dependent parameters`_). A few packages require `more elaborate solutions `_.hUjBh`hahbhhd}rˆ(hf]hg]hh]hi]hl]uhnMhohhp]r‰(hyX¥The simple build infrastructure can also handle packages where building is governed by system-dependent parameters, if you specify a little more (see the section on rŠ…r‹}rŒ(hTX¥The simple build infrastructure can also handle packages where building is governed by system-dependent parameters, if you specify a little more (see the section on h`NhnNhohhUj†ubj?)r}rŽ(hTX`system-dependent parameters`_jBKhUj†hbjChd}r(UnameXsystem-dependent parametershi]hh]hf]hg]hl]jEUsystem-dependent-parametersruhp]r‘hyXsystem-dependent parametersr’…r“}r”(hTUhUjubaubhyX). A few packages require r•…r–}r—(hTX). A few packages require h`NhnNhohhUj†ubj?)r˜}r™(hTX3`more elaborate solutions `_hd}rš(UnameXmore elaborate solutionsj~Xmorecomplexpackagesr›hi]hh]hf]hg]hl]uhUj†hp]rœhyXmore elaborate solutionsr…rž}rŸ(hTUhUj˜ubahbjCubcdocutils.nodes target r )r¡}r¢(hTX hYKhUj†hbUtargetr£hd}r¤(Urefurij›hi]r¥Umore-elaborate-solutionsr¦ahh]hf]hg]hl]r§hauhp]ubhyX.…r¨}r©(hTX.h`NhnNhohhUj†ubeubeubeubh\hV)rª}r«(hTUhUh^h`hahbhchd}r¬(hf]hg]hh]hi]r­Ucustom-setup-scriptsr®ahl]r¯hDauhnM hohhp]r°(hr)r±}r²(hTXCustom setup scriptsr³hUjªh`hahbhvhd}r´(hf]hg]hh]hi]hl]uhnM hohhp]rµhyXCustom setup scriptsr¶…r·}r¸(hTj³h`NhnNhohhUj±ubaubcsphinx.addnodes index r¹)rº}r»(hTUhUjªh`hahbUindexr¼hd}r½(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubcsphinx.addnodes desc r¾)r¿}rÀ(hTUhUjªh`hahbUdescrÁhd}rÂ(UnoindexrÉUdomainrÄXcabalhi]hh]hf]hg]hl]UobjtyperÅX pkg-sectionrÆUdesctyperÇjÆuhnNhohhp]rÈ(csphinx.addnodes desc_signature rÉ)rÊ}rË(hTX custom-setuprÌhUj¿h`hahbUdesc_signaturerÍhd}rÎ(hi]rÏX%pkg-section-custom-setup-custom-setuprÐahh]hf]hg]hl]UfirstrщuhnNhohhp]rÒ(j¹)rÓ}rÔ(hTUhUjÊh`hahbj¼hd}rÕ(hi]hh]hf]hg]hl]Uentries]rÖ(Upairr×X0custom-setup:custom-setup; package.cabal sectionjÐUNtrØauhnNhohhp]ubcsphinx.addnodes desc_name rÙ)rÚ}rÛ(hTjÌhUjÊh`hahbU desc_namerÜhd}rÝ(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rÞhyX custom-setuprß…rà}rá(hTUh`NhnNhohhUjÚubaubcsphinx.addnodes desc_addname râ)rã}rä(hTU hUjÊh`hahbU desc_addnameråhd}ræ(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rçhyX …rè}ré(hTUh`NhnNhohhUjãubaubeubcsphinx.addnodes desc_content rê)rë}rì(hTUhUj¿h`hahbU desc_contentríhd}rî(hf]hg]hh]hi]hl]uhnNhohhp]rï(cdocutils.nodes field_list rð)rñ}rò(hTUhUjëh`hahbU field_listróhd}rô(hf]hg]hh]hi]hl]uhnNhohhp]rõcdocutils.nodes field rö)r÷}rø(hTUhUjñh`hahbUfieldrùhd}rú(hf]hg]hh]hi]hl]uhnNhohhp]rû(cdocutils.nodes field_name rü)rý}rþ(hTUSincerÿhUj÷h`hahbU field_namerhd}r(hf]hg]hh]hi]hl]uhnKhp]rhyXSincer…r}r(hTUhUjýubaubcdocutils.nodes field_body r)r}r(hTU Cabal 1.24r hd}r (hf]hg]hh]hi]hl]uhUj÷hp]r h})r }r (hTj hd}r(hf]hg]hh]hi]hl]uhUjhp]rhyX Cabal 1.24r…r}r(hTUhUj ubahbhubahbU field_bodyrubeubaubh})r}r(hTXThe optional :pkg-section:`custom-setup` stanza contains information needed for the compilation of custom ``Setup.hs`` scripts,hUjëh`hahbhhd}r(hf]hg]hh]hi]hl]uhnM£ hohhp]r(hyX The optional r…r}r(hTX The optional h`NhnNhohhUjubjk)r}r(hTX:pkg-section:`custom-setup`rhUjh`hahbjohd}r(UreftypeX pkg-sectionjqˆjrX custom-setupU refdomainXcabalrhi]hh]U refexplicit‰hf]hg]hl]jtjuuhnM£ hp]r hß)r!}r"(hTjhd}r#(hf]hg]r$(j|jXcabal-pkg-sectionr%ehh]hi]hl]uhUjhp]r&hyX custom-setupr'…r(}r)(hTUhUj!ubahbhçubaubhyXB stanza contains information needed for the compilation of custom r*…r+}r,(hTXB stanza contains information needed for the compilation of custom h`NhnNhohhUjubhß)r-}r.(hTX ``Setup.hs``hd}r/(hf]hg]hh]hi]hl]uhUjhp]r0hyXSetup.hsr1…r2}r3(hTUhUj-ubahbhçubhyX scripts,r4…r5}r6(hTX scripts,h`NhnNhohhUjubeubeubeubjÌ)r7}r8(hTXIcustom-setup setup-depends: base >= 4.5 && < 4.11, Cabal < 1.25hUjªh`hahbjÏhd}r9(jÑjÒhi]hh]hf]hg]hl]uhnM¨ hohhp]r:hyXIcustom-setup setup-depends: base >= 4.5 && < 4.11, Cabal < 1.25r;…r<}r=(hTUhUj7ubaubj¹)r>}r?(hTUhUjªh`hahbj¼hd}r@(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rA}rB(hTUhUjªh`hahbjÁhd}rC(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrDjÇjDuhnNhohhp]rE(jÉ)rF}rG(hTXsetup-depends: package listhUjAh`hahbjÍhd}rH(hi]rIX$pkg-field-custom-setup-setup-dependsrJahh]hf]hg]hl]jщuhnNhohhp]rK(j¹)rL}rM(hTUhUjFh`hahbj¼hd}rN(hi]hh]hf]hg]hl]Uentries]rO(j×X/custom-setup:setup-depends; package.cabal fieldjJUNtrPauhnNhohhp]ubjÙ)rQ}rR(hTX setup-dependsrShUjFh`hahbjÜhd}rT(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rUhyX setup-dependsrV…rW}rX(hTUh`NhnNhohhUjQubaubjâ)rY}rZ(hTU: r[hUjFh`hahbjåhd}r\(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]r]hyX: r^…r_}r`(hTUh`NhnNhohhUjYubaubcsphinx.addnodes desc_annotation ra)rb}rc(hTX package listhUjFh`hahbUdesc_annotationrdhd}re(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rfhyX package listrg…rh}ri(hTUh`NhnNhohhUjbubaubeubjê)rj}rk(hTUhUjAh`hahbjíhd}rl(hf]hg]hh]hi]hl]uhnNhohhp]rm(jð)rn}ro(hTUhUjjh`hahbjóhd}rp(hf]hg]hh]hi]hl]uhnNhohhp]rqjö)rr}rs(hTUhUjnh`hahbjùhd}rt(hf]hg]hh]hi]hl]uhnNhohhp]ru(jü)rv}rw(hTjÿhUjrh`hahbjhd}rx(hf]hg]hh]hi]hl]uhnKhp]ryhyXSincerz…r{}r|(hTUhUjvubaubj)r}}r~(hTU Cabal 1.24rhd}r€(hf]hg]hh]hi]hl]uhUjrhp]rh})r‚}rƒ(hTjhd}r„(hf]hg]hh]hi]hl]uhUj}hp]r…hyX Cabal 1.24r†…r‡}rˆ(hTUhUj‚ubahbhubahbjubeubaubh})r‰}rŠ(hTX‘The dependencies needed to compile ``Setup.hs``. See the :pkg-field:`build-depends` field for a description of the syntax expected by this field.hUjjh`hahbhhd}r‹(hf]hg]hh]hi]hl]uhnM° hohhp]rŒ(hyX#The dependencies needed to compile r…rŽ}r(hTX#The dependencies needed to compile h`NhnNhohhUj‰ubhß)r}r‘(hTX ``Setup.hs``hd}r’(hf]hg]hh]hi]hl]uhUj‰hp]r“hyXSetup.hsr”…r•}r–(hTUhUjubahbhçubhyX . See the r—…r˜}r™(hTX . See the h`NhnNhohhUj‰ubjk)rš}r›(hTX:pkg-field:`build-depends`rœhUj‰h`hahbjohd}r(UreftypeX pkg-fieldjqˆjrX build-dependsU refdomainXcabalržhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM° hp]rŸhß)r }r¡(hTjœhd}r¢(hf]hg]r£(j|jžXcabal-pkg-fieldr¤ehh]hi]hl]uhUjšhp]r¥hyX build-dependsr¦…r§}r¨(hTUhUj ubahbhçubaubhyX> field for a description of the syntax expected by this field.r©…rª}r«(hTX> field for a description of the syntax expected by this field.h`NhnNhohhUj‰ubeubeubeubeubhV)r¬}r­(hTUhUh^h`hahbhchd}r®(hf]hg]hh]hi]r¯Uautogenerated-modulesr°ahl]r±hIauhnMµ hohhp]r²(hr)r³}r´(hTXAutogenerated modulesrµhUj¬h`hahbhvhd}r¶(hf]hg]hh]hi]hl]uhnMµ hohhp]r·hyXAutogenerated modulesr¸…r¹}rº(hTjµh`NhnNhohhUj³ubaubh})r»}r¼(hTXzModules that are built automatically at setup, created with a custom setup script, must appear on :pkg-field:`other-modules` for the library, executable, test-suite or benchmark stanzas or also on :pkg-field:`library:exposed-modules` for libraries to be used, but are not really on the package when distributed. This makes commands like sdist fail because the file is not found.hUj¬h`hahbhhd}r½(hf]hg]hh]hi]hl]uhnM· hohhp]r¾(hyXbModules that are built automatically at setup, created with a custom setup script, must appear on r¿…rÀ}rÁ(hTXbModules that are built automatically at setup, created with a custom setup script, must appear on h`NhnNhohhUj»ubjk)rÂ}rÃ(hTX:pkg-field:`other-modules`rÄhUj»h`hahbjohd}rÅ(UreftypeX pkg-fieldjqˆjrX other-modulesU refdomainXcabalrÆhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM· hp]rÇhß)rÈ}rÉ(hTjÄhd}rÊ(hf]hg]rË(j|jÆXcabal-pkg-fieldrÌehh]hi]hl]uhUjÂhp]rÍhyX other-modulesrÎ…rÏ}rÐ(hTUhUjÈubahbhçubaubhyXI for the library, executable, test-suite or benchmark stanzas or also on rÑ…rÒ}rÓ(hTXI for the library, executable, test-suite or benchmark stanzas or also on h`NhnNhohhUj»ubjk)rÔ}rÕ(hTX$:pkg-field:`library:exposed-modules`rÖhUj»h`hahbjohd}r×(UreftypeX pkg-fieldjqˆjrXexposed-modulesU refdomainXcabalrØhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹XlibraryuhnM· hp]rÙhß)rÚ}rÛ(hTjÖhd}rÜ(hf]hg]rÝ(j|jØXcabal-pkg-fieldrÞehh]hi]hl]uhUjÔhp]rßhyXlibrary:exposed-modulesrà…rá}râ(hTUhUjÚubahbhçubaubhyX‘ for libraries to be used, but are not really on the package when distributed. This makes commands like sdist fail because the file is not found.rã…rä}rå(hTX‘ for libraries to be used, but are not really on the package when distributed. This makes commands like sdist fail because the file is not found.h`NhnNhohhUj»ubeubh})ræ}rç(hTXThese special modules must appear again on the :pkg-field:`autogen-modules` field of the stanza that is using it, besides :pkg-field:`other-modules` or :pkg-field:`library:exposed-modules`. With this there is no need to create complex build hooks for this poweruser case.hUj¬h`hahbhhd}rè(hf]hg]hh]hi]hl]uhnM¾ hohhp]ré(hyX/These special modules must appear again on the rê…rë}rì(hTX/These special modules must appear again on the h`NhnNhohhUjæubjk)rí}rî(hTX:pkg-field:`autogen-modules`rïhUjæh`hahbjohd}rð(UreftypeX pkg-fieldjqˆjrXautogen-modulesU refdomainXcabalrñhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM¾ hp]ròhß)ró}rô(hTjïhd}rõ(hf]hg]rö(j|jñXcabal-pkg-fieldr÷ehh]hi]hl]uhUjíhp]røhyXautogen-modulesrù…rú}rû(hTUhUjóubahbhçubaubhyX/ field of the stanza that is using it, besides rü…rý}rþ(hTX/ field of the stanza that is using it, besides h`NhnNhohhUjæubjk)rÿ}r(hTX:pkg-field:`other-modules`rhUjæh`hahbjohd}r(UreftypeX pkg-fieldjqˆjrX other-modulesU refdomainXcabalrhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM¾ hp]rhß)r}r(hTjhd}r(hf]hg]r(j|jXcabal-pkg-fieldr ehh]hi]hl]uhUjÿhp]r hyX other-modulesr …r }r (hTUhUjubahbhçubaubhyX or r…r}r(hTX or h`NhnNhohhUjæubjk)r}r(hTX$:pkg-field:`library:exposed-modules`rhUjæh`hahbjohd}r(UreftypeX pkg-fieldjqˆjrXexposed-modulesU refdomainXcabalrhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹XlibraryuhnM¾ hp]rhß)r}r(hTjhd}r(hf]hg]r(j|jXcabal-pkg-fieldrehh]hi]hl]uhUjhp]rhyXlibrary:exposed-modulesr…r}r(hTUhUjubahbhçubaubhyXS. With this there is no need to create complex build hooks for this poweruser case.r …r!}r"(hTXS. With this there is no need to create complex build hooks for this poweruser case.h`NhnNhohhUjæubeubj¹)r#}r$(hTUhUj¬h`Nhbj¼hd}r%(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r&}r'(hTUhUj¬h`NhbjÁhd}r((jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr)jÇj)uhnNhohhp]r*(jÉ)r+}r,(hTXautogen-modules: module listhUj&h`hahbjÍhd}r-(hi]r.X&pkg-field-custom-setup-autogen-modulesr/ahh]hf]hg]hl]jщuhnMÆ hohhp]r0(j¹)r1}r2(hTUhUj+h`hahbj¼hd}r3(hi]hh]hf]hg]hl]Uentries]r4(j×X1custom-setup:autogen-modules; package.cabal fieldj/UNtr5auhnMÆ hohhp]ubjÙ)r6}r7(hTXautogen-modulesr8hUj+h`hahbjÜhd}r9(jÑjÒhi]hh]hf]hg]hl]uhnMÆ hohhp]r:hyXautogen-modulesr;…r<}r=(hTUh`NhnNhohhUj6ubaubjâ)r>}r?(hTj[hUj+h`hahbjåhd}r@(jÑjÒhi]hh]hf]hg]hl]uhnMÆ hohhp]rAhyX: rB…rC}rD(hTUh`NhnNhohhUj>ubaubja)rE}rF(hTX module listhUj+h`hahbjdhd}rG(jÑjÒhi]hh]hf]hg]hl]uhnMÆ hohhp]rHhyX module listrI…rJ}rK(hTUh`NhnNhohhUjEubaubeubjê)rL}rM(hTUhUj&h`hahbjíhd}rN(hf]hg]hh]hi]hl]uhnMÆ hohhp]rOcdocutils.nodes comment rP)rQ}rR(hTX$TODO: document autogen-modules fieldhUjLh`hahbUcommentrShd}rT(jÑjÒhi]hh]hf]hg]hl]uhnMÅ hohhp]rUhyX$TODO: document autogen-modules fieldrV…rW}rX(hTUhUjQubaubaubeubh})rY}rZ(hTXdRight now :pkg-field:`executable:main-is` modules are not supported on :pkg-field:`autogen-modules`.hUj¬h`hahbhhd}r[(hf]hg]hh]hi]hl]uhnMÇ hohhp]r\(hyX Right now r]…r^}r_(hTX Right now h`NhnNhohhUjYubjk)r`}ra(hTX:pkg-field:`executable:main-is`rbhUjYh`hahbjohd}rc(UreftypeX pkg-fieldjqˆjrXmain-isU refdomainXcabalrdhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹X executableuhnMÇ hp]rehß)rf}rg(hTjbhd}rh(hf]hg]ri(j|jdXcabal-pkg-fieldrjehh]hi]hl]uhUj`hp]rkhyXexecutable:main-isrl…rm}rn(hTUhUjfubahbhçubaubhyX modules are not supported on ro…rp}rq(hTX modules are not supported on h`NhnNhohhUjYubjk)rr}rs(hTX:pkg-field:`autogen-modules`rthUjYh`hahbjohd}ru(UreftypeX pkg-fieldjqˆjrXautogen-modulesU refdomainXcabalrvhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnMÇ hp]rwhß)rx}ry(hTjthd}rz(hf]hg]r{(j|jvXcabal-pkg-fieldr|ehh]hi]hl]uhUjrhp]r}hyXautogen-modulesr~…r}r€(hTUhUjxubahbhçubaubhyX.…r}r‚(hTX.h`NhnNhohhUjYubeubjÌ)rƒ}r„(hTX¨Library default-language: Haskell2010 build-depends: base exposed-modules: MyLibrary MyLibHelperModule other-modules: MyLibModule autogen-modules: MyLibHelperModule Executable Exe default-language: Haskell2010 main-is: Dummy.hs build-depends: base other-modules: MyExeModule MyExeHelperModule autogen-modules: MyExeHelperModulehUj¬h`hahbjÏhd}r…(jÑjÒhi]hh]hf]hg]hl]uhnMÌ hohhp]r†hyX¨Library default-language: Haskell2010 build-depends: base exposed-modules: MyLibrary MyLibHelperModule other-modules: MyLibModule autogen-modules: MyLibHelperModule Executable Exe default-language: Haskell2010 main-is: Dummy.hs build-depends: base other-modules: MyExeModule MyExeHelperModule autogen-modules: MyExeHelperModuler‡…rˆ}r‰(hTUhUjƒubaubeubhV)rŠ}r‹(hTUhUh^h`hahbhchd}rŒ(hf]hg]hh]hi]rU&accessing-data-files-from-package-coderŽahl]rhauhnMâ hohhp]r(hr)r‘}r’(hTX&Accessing data files from package coder“hUjŠh`hahbhvhd}r”(hf]hg]hh]hi]hl]uhnMâ hohhp]r•hyX&Accessing data files from package coder–…r—}r˜(hTj“h`NhnNhohhUj‘ubaubh})r™}rš(hTXThe placement on the target system of files listed in the :pkg-field:`data-files` field varies between systems, and in some cases one can even move packages around after installation (see `prefix independence `__). To enable packages to find these files in a portable way, Cabal generates a module called :file:`Paths_{pkgname}` (with any hyphens in *pkgname* replaced by underscores) during building, so that it may be imported by modules of the package. This module defines a functionhUjŠh`hahbhhd}r›(hf]hg]hh]hi]hl]uhnMä hohhp]rœ(hyX:The placement on the target system of files listed in the r…rž}rŸ(hTX:The placement on the target system of files listed in the h`NhnNhohhUj™ubjk)r }r¡(hTX:pkg-field:`data-files`r¢hUj™h`hahbjohd}r£(UreftypeX pkg-fieldjqˆjrX data-filesU refdomainXcabalr¤hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnMä hp]r¥hß)r¦}r§(hTj¢hd}r¨(hf]hg]r©(j|j¤Xcabal-pkg-fieldrªehh]hi]hl]uhUj hp]r«hyX data-filesr¬…r­}r®(hTUhUj¦ubahbhçubaubhyXk field varies between systems, and in some cases one can even move packages around after installation (see r¯…r°}r±(hTXk field varies between systems, and in some cases one can even move packages around after installation (see h`NhnNhohhUj™ubj?)r²}r³(hTXF`prefix independence `__hd}r´(UnameXprefix independencej~X,installing-packages.html#prefix-independencehi]hh]hf]hg]hl]uhUj™hp]rµhyXprefix independencer¶…r·}r¸(hTUhUj²ubahbjCubhyX]). To enable packages to find these files in a portable way, Cabal generates a module called r¹…rº}r»(hTX]). To enable packages to find these files in a portable way, Cabal generates a module called h`NhnNhohhUj™ubhß)r¼}r½(hTX Paths_pkgnamehd}r¾(hi]hh]hf]hg]r¿XfilerÀaUrolejÀhl]uhUj™hp]rÁ(hyXPaths_rÂ…rÃ}rÄ(hTXPaths_hUj¼ubh¿)rÅ}rÆ(hTXpkgnamehd}rÇ(hf]hg]hh]hi]hl]uhUj¼hp]rÈhyXpkgnamerÉ…rÊ}rË(hTUhUjÅubahbhÇubehbhçubhyX (with any hyphens in rÌ…rÍ}rÎ(hTX (with any hyphens in h`NhnNhohhUj™ubh¿)rÏ}rÐ(hTX *pkgname*hd}rÑ(hf]hg]hh]hi]hl]uhUj™hp]rÒhyXpkgnamerÓ…rÔ}rÕ(hTUhUjÏubahbhÇubhyX replaced by underscores) during building, so that it may be imported by modules of the package. This module defines a functionrÖ…r×}rØ(hTX replaced by underscores) during building, so that it may be imported by modules of the package. This module defines a functionh`NhnNhohhUj™ubeubjÌ)rÙ}rÚ(hTX*getDataFileName :: FilePath -> IO FilePathhUjŠh`hahbjÏhd}rÛ(j‰jXhaskelljÑjÒhi]hh]hf]j}hg]hl]uhnMí hohhp]rÜhyX*getDataFileName :: FilePath -> IO FilePathrÝ…rÞ}rß(hTUhUjÙubaubh})rà}rá(hTXªIf the argument is a filename listed in the :pkg-field:`data-files` field, the result is the name of the corresponding file on the system on which the program is running.hUjŠh`hahbhhd}râ(hf]hg]hh]hi]hl]uhnMñ hohhp]rã(hyX,If the argument is a filename listed in the rä…rå}ræ(hTX,If the argument is a filename listed in the h`NhnNhohhUjàubjk)rç}rè(hTX:pkg-field:`data-files`réhUjàh`hahbjohd}rê(UreftypeX pkg-fieldjqˆjrX data-filesU refdomainXcabalrëhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnMñ hp]rìhß)rí}rî(hTjéhd}rï(hf]hg]rð(j|jëXcabal-pkg-fieldrñehh]hi]hl]uhUjçhp]ròhyX data-filesró…rô}rõ(hTUhUjíubahbhçubaubhyXg field, the result is the name of the corresponding file on the system on which the program is running.rö…r÷}rø(hTXg field, the result is the name of the corresponding file on the system on which the program is running.h`NhnNhohhUjàubeubhë)rù}rú(hTXèIf you decide to import the :file:`Paths_{pkgname}` module then it *must* be listed in the :pkg-field:`other-modules` field just like any other module in your package and on :pkg-field:`autogen-modules` as the file is autogenerated.hUjŠh`hahbhîhd}rû(hf]hg]hh]hi]hl]uhnNhohhp]rüh})rý}rþ(hTXèIf you decide to import the :file:`Paths_{pkgname}` module then it *must* be listed in the :pkg-field:`other-modules` field just like any other module in your package and on :pkg-field:`autogen-modules` as the file is autogenerated.hUjùh`hahbhhd}rÿ(hf]hg]hh]hi]hl]uhnM÷ hp]r(hyXIf you decide to import the r…r}r(hTXIf you decide to import the hUjýubhß)r}r(hTX Paths_pkgnamehd}r(hi]hh]hf]hg]rXfileraUrolejhl]uhUjýhp]r (hyXPaths_r …r }r (hTXPaths_hUjubh¿)r }r(hTXpkgnamehd}r(hf]hg]hh]hi]hl]uhUjhp]rhyXpkgnamer…r}r(hTUhUj ubahbhÇubehbhçubhyX module then it r…r}r(hTX module then it hUjýubh¿)r}r(hTX*must*hd}r(hf]hg]hh]hi]hl]uhUjýhp]rhyXmustr…r}r(hTUhUjubahbhÇubhyX be listed in the r…r}r (hTX be listed in the hUjýubjk)r!}r"(hTX:pkg-field:`other-modules`r#hUjýh`hahbjohd}r$(UreftypeX pkg-fieldjqˆjrX other-modulesU refdomainXcabalr%hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM÷ hp]r&hß)r'}r((hTj#hd}r)(hf]hg]r*(j|j%Xcabal-pkg-fieldr+ehh]hi]hl]uhUj!hp]r,hyX other-modulesr-…r.}r/(hTUhUj'ubahbhçubaubhyX9 field just like any other module in your package and on r0…r1}r2(hTX9 field just like any other module in your package and on hUjýubjk)r3}r4(hTX:pkg-field:`autogen-modules`r5hUjýh`hahbjohd}r6(UreftypeX pkg-fieldjqˆjrXautogen-modulesU refdomainXcabalr7hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM÷ hp]r8hß)r9}r:(hTj5hd}r;(hf]hg]r<(j|j7Xcabal-pkg-fieldr=ehh]hi]hl]uhUj3hp]r>hyXautogen-modulesr?…r@}rA(hTUhUj9ubahbhçubaubhyX as the file is autogenerated.rB…rC}rD(hTX as the file is autogenerated.hUjýubeubaubh})rE}rF(hTX­The :file:`Paths_{pkgname}` module is not platform independent, as any other autogenerated module, so it does not get included in the source tarballs generated by ``sdist``.hUjŠh`hahbhhd}rG(hf]hg]hh]hi]hl]uhnMü hohhp]rH(hyXThe rI…rJ}rK(hTXThe h`NhnNhohhUjEubhß)rL}rM(hTX Paths_pkgnamehd}rN(hi]hh]hf]hg]rOXfilerPaUrolejPhl]uhUjEhp]rQ(hyXPaths_rR…rS}rT(hTXPaths_hUjLubh¿)rU}rV(hTXpkgnamehd}rW(hf]hg]hh]hi]hl]uhUjLhp]rXhyXpkgnamerY…rZ}r[(hTUhUjUubahbhÇubehbhçubhyXˆ module is not platform independent, as any other autogenerated module, so it does not get included in the source tarballs generated by r\…r]}r^(hTXˆ module is not platform independent, as any other autogenerated module, so it does not get included in the source tarballs generated by h`NhnNhohhUjEubhß)r_}r`(hTX ``sdist``hd}ra(hf]hg]hh]hi]hl]uhUjEhp]rbhyXsdistrc…rd}re(hTUhUj_ubahbhçubhyX.…rf}rg(hTX.h`NhnNhohhUjEubeubh})rh}ri(hTXThe :file:`Paths_{pkgname}` module also includes some other useful functions and values, which record the version of the package and some other directories which the package has been configured to be installed into (e.g. data files live in ``getDataDir``):hUjŠh`hahbhhd}rj(hf]hg]hh]hi]hl]uhnM hohhp]rk(hyXThe rl…rm}rn(hTXThe h`NhnNhohhUjhubhß)ro}rp(hTX Paths_pkgnamehd}rq(hi]hh]hf]hg]rrXfilersaUrolejshl]uhUjhhp]rt(hyXPaths_ru…rv}rw(hTXPaths_hUjoubh¿)rx}ry(hTXpkgnamehd}rz(hf]hg]hh]hi]hl]uhUjohp]r{hyXpkgnamer|…r}}r~(hTUhUjxubahbhÇubehbhçubhyXÕ module also includes some other useful functions and values, which record the version of the package and some other directories which the package has been configured to be installed into (e.g. data files live in r…r€}r(hTXÕ module also includes some other useful functions and values, which record the version of the package and some other directories which the package has been configured to be installed into (e.g. data files live in h`NhnNhohhUjhubhß)r‚}rƒ(hTX``getDataDir``hd}r„(hf]hg]hh]hi]hl]uhUjhhp]r…hyX getDataDirr†…r‡}rˆ(hTUhUj‚ubahbhçubhyX):r‰…rŠ}r‹(hTX):h`NhnNhohhUjhubeubjÌ)rŒ}r(hTXµversion :: Version getBinDir :: IO FilePath getLibDir :: IO FilePath getDynLibDir :: IO FilePath getDataDir :: IO FilePath getLibexecDir :: IO FilePath getSysconfDir :: IO FilePathhUjŠh`hahbjÏhd}rŽ(j‰jXhaskelljÑjÒhi]hh]hf]j}hg]hl]uhnM hohhp]rhyXµversion :: Version getBinDir :: IO FilePath getLibDir :: IO FilePath getDynLibDir :: IO FilePath getDataDir :: IO FilePath getLibexecDir :: IO FilePath getSysconfDir :: IO FilePathr…r‘}r’(hTUhUjŒubaubh})r“}r”(hTXÚThe actual location of all these directories can be individually overridden at runtime using environment variables of the form ``pkg_name_var``, where ``pkg_name`` is the name of the package with all hyphens converted into underscores, and ``var`` is either ``bindir``, ``libdir``, ``dynlibdir``, ``datadir``, ``libexedir`` or ``sysconfdir``. For example, the configured data directory for ``pretty-show`` is controlled with the ``pretty_show_datadir`` environment variable.hUjŠh`hahbhhd}r•(hf]hg]hh]hi]hl]uhnM hohhp]r–(hyXThe actual location of all these directories can be individually overridden at runtime using environment variables of the form r—…r˜}r™(hTXThe actual location of all these directories can be individually overridden at runtime using environment variables of the form h`NhnNhohhUj“ubhß)rš}r›(hTX``pkg_name_var``hd}rœ(hf]hg]hh]hi]hl]uhUj“hp]rhyX pkg_name_varrž…rŸ}r (hTUhUjšubahbhçubhyX, where r¡…r¢}r£(hTX, where h`NhnNhohhUj“ubhß)r¤}r¥(hTX ``pkg_name``hd}r¦(hf]hg]hh]hi]hl]uhUj“hp]r§hyXpkg_namer¨…r©}rª(hTUhUj¤ubahbhçubhyXM is the name of the package with all hyphens converted into underscores, and r«…r¬}r­(hTXM is the name of the package with all hyphens converted into underscores, and h`NhnNhohhUj“ubhß)r®}r¯(hTX``var``hd}r°(hf]hg]hh]hi]hl]uhUj“hp]r±hyXvarr²…r³}r´(hTUhUj®ubahbhçubhyX is either rµ…r¶}r·(hTX is either h`NhnNhohhUj“ubhß)r¸}r¹(hTX ``bindir``hd}rº(hf]hg]hh]hi]hl]uhUj“hp]r»hyXbindirr¼…r½}r¾(hTUhUj¸ubahbhçubhyX, r¿…rÀ}rÁ(hTX, h`NhnNhohhUj“ubhß)rÂ}rÃ(hTX ``libdir``hd}rÄ(hf]hg]hh]hi]hl]uhUj“hp]rÅhyXlibdirrÆ…rÇ}rÈ(hTUhUjÂubahbhçubhyX, rÉ…rÊ}rË(hTX, rÌh`NhnNhohhUj“ubhß)rÍ}rÎ(hTX ``dynlibdir``hd}rÏ(hf]hg]hh]hi]hl]uhUj“hp]rÐhyX dynlibdirrÑ…rÒ}rÓ(hTUhUjÍubahbhçubhyX, rÔ…rÕ}rÖ(hTX, hUj“ubhß)r×}rØ(hTX ``datadir``hd}rÙ(hf]hg]hh]hi]hl]uhUj“hp]rÚhyXdatadirrÛ…rÜ}rÝ(hTUhUj×ubahbhçubhyX, rÞ…rß}rà(hTjÌhUj“ubhß)rá}râ(hTX ``libexedir``hd}rã(hf]hg]hh]hi]hl]uhUj“hp]rähyX libexedirrå…ræ}rç(hTUhUjáubahbhçubhyX or rè…ré}rê(hTX or h`NhnNhohhUj“ubhß)rë}rì(hTX``sysconfdir``hd}rí(hf]hg]hh]hi]hl]uhUj“hp]rîhyX sysconfdirrï…rð}rñ(hTUhUjëubahbhçubhyX1. For example, the configured data directory for rò…ró}rô(hTX1. For example, the configured data directory for h`NhnNhohhUj“ubhß)rõ}rö(hTX``pretty-show``hd}r÷(hf]hg]hh]hi]hl]uhUj“hp]røhyX pretty-showrù…rú}rû(hTUhUjõubahbhçubhyX is controlled with the rü…rý}rþ(hTX is controlled with the h`NhnNhohhUj“ubhß)rÿ}r(hTX``pretty_show_datadir``hd}r(hf]hg]hh]hi]hl]uhUj“hp]rhyXpretty_show_datadirr…r}r(hTUhUjÿubahbhçubhyX environment variable.r…r}r(hTX environment variable.h`NhnNhohhUj“ubeubhV)r }r (hTUhUjŠh`hahbhchd}r (hf]hg]hh]hi]r Uaccessing-the-package-versionr ahl]rh!auhnM hohhp]r(hr)r}r(hTXAccessing the package versionrhUj h`hahbhvhd}r(hf]hg]hh]hi]hl]uhnM hohhp]rhyXAccessing the package versionr…r}r(hTjh`NhnNhohhUjubaubh})r}r(hTX The aforementioned auto generated :file:`Paths_{pkgname}` module also exports the constant ``version ::`` `Version `__ which is defined as the version of your package as specified in the ``version`` field.hUj h`hahbhhd}r(hf]hg]hh]hi]hl]uhnM hohhp]r(hyX"The aforementioned auto generated r…r}r(hTX"The aforementioned auto generated h`NhnNhohhUjubhß)r}r (hTX Paths_pkgnamehd}r!(hi]hh]hf]hg]r"Xfiler#aUrolej#hl]uhUjhp]r$(hyXPaths_r%…r&}r'(hTXPaths_hUjubh¿)r(}r)(hTXpkgnamehd}r*(hf]hg]hh]hi]hl]uhUjhp]r+hyXpkgnamer,…r-}r.(hTUhUj(ubahbhÇubehbhçubhyX" module also exports the constant r/…r0}r1(hTX" module also exports the constant h`NhnNhohhUjubhß)r2}r3(hTX``version ::``hd}r4(hf]hg]hh]hi]hl]uhUjhp]r5hyX version ::r6…r7}r8(hTUhUj2ubahbhçubhyX …r9}r:(hTX h`NhnNhohhUjubj?)r;}r<(hTXL`Version `__hd}r=(UnameXVersionj~X>http://hackage.haskell.org/package/base/docs/Data-Version.htmlhi]hh]hf]hg]hl]uhUjhp]r>hyXVersionr?…r@}rA(hTUhUj;ubahbjCubhyXE which is defined as the version of your package as specified in the rB…rC}rD(hTXE which is defined as the version of your package as specified in the h`NhnNhohhUjubhß)rE}rF(hTX ``version``hd}rG(hf]hg]hh]hi]hl]uhUjhp]rHhyXversionrI…rJ}rK(hTUhUjEubahbhçubhyX field.rL…rM}rN(hTX field.h`NhnNhohhUjubeubeubeubhV)rO}rP(hTUhYKhUh^h`hahbhchd}rQ(hf]hg]hh]hi]rRjahl]rShauhnM" hohhp]rT(hr)rU}rV(hTXSystem-dependent parametersrWhUjOh`hahbhvhd}rX(hf]hg]hh]hi]hl]uhnM" hohhp]rYhyXSystem-dependent parametersrZ…r[}r\(hTjWh`NhnNhohhUjUubaubh})r]}r^(hTXFor some packages, especially those interfacing with C libraries, implementation details and the build procedure depend on the build environment. The ``build-type`` ``Configure`` can be used to handle many such situations. In this case, ``Setup.hs`` should be:hUjOh`hahbhhd}r_(hf]hg]hh]hi]hl]uhnM$ hohhp]r`(hyX–For some packages, especially those interfacing with C libraries, implementation details and the build procedure depend on the build environment. The ra…rb}rc(hTX–For some packages, especially those interfacing with C libraries, implementation details and the build procedure depend on the build environment. The h`NhnNhohhUj]ubhß)rd}re(hTX``build-type``hd}rf(hf]hg]hh]hi]hl]uhUj]hp]rghyX build-typerh…ri}rj(hTUhUjdubahbhçubhyX …rk}rl(hTX h`NhnNhohhUj]ubhß)rm}rn(hTX ``Configure``hd}ro(hf]hg]hh]hi]hl]uhUj]hp]rphyX Configurerq…rr}rs(hTUhUjmubahbhçubhyX; can be used to handle many such situations. In this case, rt…ru}rv(hTX; can be used to handle many such situations. In this case, h`NhnNhohhUj]ubhß)rw}rx(hTX ``Setup.hs``hd}ry(hf]hg]hh]hi]hl]uhUj]hp]rzhyXSetup.hsr{…r|}r}(hTUhUjwubahbhçubhyX should be:r~…r}r€(hTX should be:h`NhnNhohhUj]ubeubjÌ)r}r‚(hTXHimport Distribution.Simple main = defaultMainWithHooks autoconfUserHookshUjOh`hahbjÏhd}rƒ(j‰jXhaskelljÑjÒhi]hh]hf]j}hg]hl]uhnM) hohhp]r„hyXHimport Distribution.Simple main = defaultMainWithHooks autoconfUserHooksr……r†}r‡(hTUhUjubaubh})rˆ}r‰(hTXgMost packages, however, would probably do better using the ``Simple`` build type and `configurations`_.hUjOh`hahbhhd}rŠ(hf]hg]hh]hi]hl]uhnM. hohhp]r‹(hyX;Most packages, however, would probably do better using the rŒ…r}rŽ(hTX;Most packages, however, would probably do better using the h`NhnNhohhUjˆubhß)r}r(hTX ``Simple``hd}r‘(hf]hg]hh]hi]hl]uhUjˆhp]r’hyXSimpler“…r”}r•(hTUhUjubahbhçubhyX build type and r–…r—}r˜(hTX build type and h`NhnNhohhUjˆubj?)r™}rš(hTX`configurations`_jBKhUjˆhbjChd}r›(UnameXconfigurationshi]hh]hf]hg]hl]jEUconfigurationsrœuhp]rhyXconfigurationsrž…rŸ}r (hTUhUj™ubaubhyX.…r¡}r¢(hTX.h`NhnNhohhUjˆubeubh})r£}r¤(hTXNThe :pkg-field:`build-type` ``Configure`` differs from ``Simple`` in two ways:r¥hUjOh`hahbhhd}r¦(hf]hg]hh]hi]hl]uhnM1 hohhp]r§(hyXThe r¨…r©}rª(hTXThe h`NhnNhohhUj£ubjk)r«}r¬(hTX:pkg-field:`build-type`r­hUj£h`hahbjohd}r®(UreftypeX pkg-fieldjqˆjrX build-typeU refdomainXcabalr¯hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM1 hp]r°hß)r±}r²(hTj­hd}r³(hf]hg]r´(j|j¯Xcabal-pkg-fieldrµehh]hi]hl]uhUj«hp]r¶hyX build-typer·…r¸}r¹(hTUhUj±ubahbhçubaubhyX …rº}r»(hTX h`NhnNhohhUj£ubhß)r¼}r½(hTX ``Configure``hd}r¾(hf]hg]hh]hi]hl]uhUj£hp]r¿hyX ConfigurerÀ…rÁ}rÂ(hTUhUj¼ubahbhçubhyX differs from rÃ…rÄ}rÅ(hTX differs from h`NhnNhohhUj£ubhß)rÆ}rÇ(hTX ``Simple``hd}rÈ(hf]hg]hh]hi]hl]uhUj£hp]rÉhyXSimplerÊ…rË}rÌ(hTUhUjÆubahbhçubhyX in two ways:rÍ…rÎ}rÏ(hTX in two ways:h`NhnNhohhUj£ubeubh‡)rÐ}rÑ(hTUhUjOh`hahbhŠhd}rÒ(hŒX-hi]hh]hf]hg]hl]uhnM3 hohhp]rÓ(hŽ)rÔ}rÕ(hTX'The package root directory must contain a shell script called ``configure``. The configure step will run the script. This ``configure`` script may be produced by `autoconf `__ or may be hand-written. The ``configure`` script typically discovers information about the system and records it for later steps, e.g. by generating system-dependent header files for inclusion in C source files and preprocessed Haskell source files. (Clearly this won't work for Windows without MSYS or Cygwin: other ideas are needed.) hUjÐh`hahbh‘hd}rÖ(hf]hg]hh]hi]hl]uhnNhohhp]r×h})rØ}rÙ(hTX&The package root directory must contain a shell script called ``configure``. The configure step will run the script. This ``configure`` script may be produced by `autoconf `__ or may be hand-written. The ``configure`` script typically discovers information about the system and records it for later steps, e.g. by generating system-dependent header files for inclusion in C source files and preprocessed Haskell source files. (Clearly this won't work for Windows without MSYS or Cygwin: other ideas are needed.)hUjÔh`hahbhhd}rÚ(hf]hg]hh]hi]hl]uhnM3 hp]rÛ(hyX>The package root directory must contain a shell script called rÜ…rÝ}rÞ(hTX>The package root directory must contain a shell script called hUjØubhß)rß}rà(hTX ``configure``hd}rá(hf]hg]hh]hi]hl]uhUjØhp]râhyX configurerã…rä}rå(hTUhUjßubahbhçubhyX/. The configure step will run the script. This ræ…rç}rè(hTX/. The configure step will run the script. This hUjØubhß)ré}rê(hTX ``configure``hd}rë(hf]hg]hh]hi]hl]uhUjØhp]rìhyX configurerí…rî}rï(hTUhUjéubahbhçubhyX script may be produced by rð…rñ}rò(hTX script may be produced by hUjØubj?)ró}rô(hTX4`autoconf `__hd}rõ(UnameXautoconfj~X%http://www.gnu.org/software/autoconf/hi]hh]hf]hg]hl]uhUjØhp]röhyXautoconfr÷…rø}rù(hTUhUjóubahbjCubhyX or may be hand-written. The rú…rû}rü(hTX or may be hand-written. The hUjØubhß)rý}rþ(hTX ``configure``hd}rÿ(hf]hg]hh]hi]hl]uhUjØhp]rhyX configurer…r}r(hTUhUjýubahbhçubhyX( script typically discovers information about the system and records it for later steps, e.g. by generating system-dependent header files for inclusion in C source files and preprocessed Haskell source files. (Clearly this won’t work for Windows without MSYS or Cygwin: other ideas are needed.)r…r}r(hTX& script typically discovers information about the system and records it for later steps, e.g. by generating system-dependent header files for inclusion in C source files and preprocessed Haskell source files. (Clearly this won't work for Windows without MSYS or Cygwin: other ideas are needed.)hUjØubeubaubhŽ)r}r(hTXIf the package root directory contains a file called *package*\ ``.buildinfo`` after the configuration step, subsequent steps will read it to obtain additional settings for `build information`_ fields,to be merged with the ones given in the ``.cabal`` file. In particular, this file may be generated by the ``configure`` script mentioned above, allowing these settings to vary depending on the build environment. hUjÐh`hahbh‘hd}r (hf]hg]hh]hi]hl]uhnNhohhp]r h})r }r (hTXœIf the package root directory contains a file called *package*\ ``.buildinfo`` after the configuration step, subsequent steps will read it to obtain additional settings for `build information`_ fields,to be merged with the ones given in the ``.cabal`` file. In particular, this file may be generated by the ``configure`` script mentioned above, allowing these settings to vary depending on the build environment.hUjh`hahbhhd}r (hf]hg]hh]hi]hl]uhnM= hp]r(hyX5If the package root directory contains a file called r…r}r(hTX5If the package root directory contains a file called hUj ubh¿)r}r(hTX *package*hd}r(hf]hg]hh]hi]hl]uhUj hp]rhyXpackager…r}r(hTUhUjubahbhÇubhyX…r}r(hTX\ hUj ubhß)r}r(hTX``.buildinfo``hd}r(hf]hg]hh]hi]hl]uhUj hp]rhyX .buildinfor…r }r!(hTUhUjubahbhçubhyX_ after the configuration step, subsequent steps will read it to obtain additional settings for r"…r#}r$(hTX_ after the configuration step, subsequent steps will read it to obtain additional settings for hUj ubj?)r%}r&(hTX`build information`_jBKhUj hbjChd}r'(UnameXbuild informationhi]hh]hf]hg]hl]jEUbuild-informationr(uhp]r)hyXbuild informationr*…r+}r,(hTUhUj%ubaubhyX0 fields,to be merged with the ones given in the r-…r.}r/(hTX0 fields,to be merged with the ones given in the hUj ubhß)r0}r1(hTX ``.cabal``hd}r2(hf]hg]hh]hi]hl]uhUj hp]r3hyX.cabalr4…r5}r6(hTUhUj0ubahbhçubhyX8 file. In particular, this file may be generated by the r7…r8}r9(hTX8 file. In particular, this file may be generated by the hUj ubhß)r:}r;(hTX ``configure``hd}r<(hf]hg]hh]hi]hl]uhUj hp]r=hyX configurer>…r?}r@(hTUhUj:ubahbhçubhyX\ script mentioned above, allowing these settings to vary depending on the build environment.rA…rB}rC(hTX\ script mentioned above, allowing these settings to vary depending on the build environment.hUj ubeubaubeubh})rD}rE(hTX?The build information file should have the following structure:rFhUjOh`hahbhhd}rG(hf]hg]hh]hi]hl]uhnME hohhp]rHhyX?The build information file should have the following structure:rI…rJ}rK(hTjFh`NhnNhohhUjDubaubcdocutils.nodes block_quote rL)rM}rN(hTUhUjOh`hahbU block_quoterOhd}rP(hf]hg]hh]hi]hl]uhnNhohhp]rQ(h})rR}rS(hTX *buildinfo*rThUjMh`hahbhhd}rU(hf]hg]hh]hi]hl]uhnMG hp]rVh¿)rW}rX(hTjThd}rY(hf]hg]hh]hi]hl]uhUjRhp]rZhyX buildinfor[…r\}r](hTUhUjWubahbhÇubaubh})r^}r_(hTX"``executable:`` *name* *buildinfo*hUjMh`hahbhhd}r`(hf]hg]hh]hi]hl]uhnMI hp]ra(hß)rb}rc(hTX``executable:``hd}rd(hf]hg]hh]hi]hl]uhUj^hp]rehyX executable:rf…rg}rh(hTUhUjbubahbhçubhyX …ri}rj(hTX hUj^ubh¿)rk}rl(hTX*name*hd}rm(hf]hg]hh]hi]hl]uhUj^hp]rnhyXnamero…rp}rq(hTUhUjkubahbhÇubhyX …rr}rs(hTX hUj^ubh¿)rt}ru(hTX *buildinfo*hd}rv(hf]hg]hh]hi]hl]uhUj^hp]rwhyX buildinforx…ry}rz(hTUhUjtubahbhÇubeubh})r{}r|(hTX&``executable:`` *name* *buildinfo* ...hUjMh`hahbhhd}r}(hf]hg]hh]hi]hl]uhnMK hp]r~(hß)r}r€(hTX``executable:``hd}r(hf]hg]hh]hi]hl]uhUj{hp]r‚hyX executable:rƒ…r„}r…(hTUhUjubahbhçubhyX …r†}r‡(hTX hUj{ubh¿)rˆ}r‰(hTX*name*hd}rŠ(hf]hg]hh]hi]hl]uhUj{hp]r‹hyXnamerŒ…r}rŽ(hTUhUjˆubahbhÇubhyX …r}r(hTX hUj{ubh¿)r‘}r’(hTX *buildinfo*hd}r“(hf]hg]hh]hi]hl]uhUj{hp]r”hyX buildinfor•…r–}r—(hTUhUj‘ubahbhÇubhyX …r˜…r™}rš(hTX ...hUj{ubeubeubh})r›}rœ(hTX4where each *buildinfo* consists of settings of fields listed in the section on `build information`_. The first one (if present) relates to the library, while each of the others relate to the named executable. (The names must match the package description, but you don't have to have entries for all of them.)hUjOh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMM hohhp]rž(hyX where each rŸ…r }r¡(hTX where each h`NhnNhohhUj›ubh¿)r¢}r£(hTX *buildinfo*hd}r¤(hf]hg]hh]hi]hl]uhUj›hp]r¥hyX buildinfor¦…r§}r¨(hTUhUj¢ubahbhÇubhyX9 consists of settings of fields listed in the section on r©…rª}r«(hTX9 consists of settings of fields listed in the section on h`NhnNhohhUj›ubj?)r¬}r­(hTX`build information`_jBKhUj›hbjChd}r®(UnameXbuild informationhi]hh]hf]hg]hl]jEj(uhp]r¯hyXbuild informationr°…r±}r²(hTUhUj¬ubaubhyXÓ. The first one (if present) relates to the library, while each of the others relate to the named executable. (The names must match the package description, but you don’t have to have entries for all of them.)r³…r´}rµ(hTXÑ. The first one (if present) relates to the library, while each of the others relate to the named executable. (The names must match the package description, but you don't have to have entries for all of them.)h`NhnNhohhUj›ubeubh})r¶}r·(hTXkNeither of these files is required. If they are absent, this setup script is equivalent to ``defaultMain``.hUjOh`hahbhhd}r¸(hf]hg]hh]hi]hl]uhnMS hohhp]r¹(hyX[Neither of these files is required. If they are absent, this setup script is equivalent to rº…r»}r¼(hTX[Neither of these files is required. If they are absent, this setup script is equivalent to h`NhnNhohhUj¶ubhß)r½}r¾(hTX``defaultMain``hd}r¿(hf]hg]hh]hi]hl]uhUj¶hp]rÀhyX defaultMainrÁ…rÂ}rÃ(hTUhUj½ubahbhçubhyX.…rÄ}rÅ(hTX.h`NhnNhohhUj¶ubeubhV)rÆ}rÇ(hTUhUjOh`hahbhchd}rÈ(hf]hg]hh]hi]rÉUexample-using-autoconfrÊahl]rËh3auhnMW hohhp]rÌ(hr)rÍ}rÎ(hTXExample: Using autoconfrÏhUjÆh`hahbhvhd}rÐ(hf]hg]hh]hi]hl]uhnMW hohhp]rÑhyXExample: Using autoconfrÒ…rÓ}rÔ(hTjÏh`NhnNhohhUjÍubaubh})rÕ}rÖ(hTXhThis example is for people familiar with the `autoconf `__ tools.hUjÆh`hahbhhd}r×(hf]hg]hh]hi]hl]uhnMY hohhp]rØ(hyX-This example is for people familiar with the rÙ…rÚ}rÛ(hTX-This example is for people familiar with the h`NhnNhohhUjÕubj?)rÜ}rÝ(hTX4`autoconf `__hd}rÞ(UnameXautoconfj~X%http://www.gnu.org/software/autoconf/hi]hh]hf]hg]hl]uhUjÕhp]rßhyXautoconfrà…rá}râ(hTUhUjÜubahbjCubhyX tools.rã…rä}rå(hTX tools.h`NhnNhohhUjÕubeubh})ræ}rç(hTX7In the X11 package, the file ``configure.ac`` contains:rèhUjÆh`hahbhhd}ré(hf]hg]hh]hi]hl]uhnM\ hohhp]rê(hyXIn the X11 package, the file rë…rì}rí(hTXIn the X11 package, the file h`NhnNhohhUjæubhß)rî}rï(hTX``configure.ac``hd}rð(hf]hg]hh]hi]hl]uhUjæhp]rñhyX configure.acrò…ró}rô(hTUhUjîubahbhçubhyX contains:rõ…rö}r÷(hTX contains:h`NhnNhohhUjæubeubjÌ)rø}rù(hTX*AC_INIT([Haskell X11 package], [1.1], [libraries@haskell.org], [X11]) # Safety check: Ensure that we are in the correct source directory. AC_CONFIG_SRCDIR([X11.cabal]) # Header file to place defines in AC_CONFIG_HEADERS([include/HsX11Config.h]) # Check for X11 include paths and libraries AC_PATH_XTRA AC_TRY_CPP([#include ],,[no_x=yes]) # Build the package if we found X11 stuff if test "$no_x" = yes then BUILD_PACKAGE_BOOL=False else BUILD_PACKAGE_BOOL=True fi AC_SUBST([BUILD_PACKAGE_BOOL]) AC_CONFIG_FILES([X11.buildinfo]) AC_OUTPUThUjÆh`hahbjÏhd}rú(j‰jXshelljÑjÒhi]hh]hf]j}hg]hl]uhnM^ hohhp]rûhyX*AC_INIT([Haskell X11 package], [1.1], [libraries@haskell.org], [X11]) # Safety check: Ensure that we are in the correct source directory. AC_CONFIG_SRCDIR([X11.cabal]) # Header file to place defines in AC_CONFIG_HEADERS([include/HsX11Config.h]) # Check for X11 include paths and libraries AC_PATH_XTRA AC_TRY_CPP([#include ],,[no_x=yes]) # Build the package if we found X11 stuff if test "$no_x" = yes then BUILD_PACKAGE_BOOL=False else BUILD_PACKAGE_BOOL=True fi AC_SUBST([BUILD_PACKAGE_BOOL]) AC_CONFIG_FILES([X11.buildinfo]) AC_OUTPUTrü…rý}rþ(hTUhUjøubaubh})rÿ}r(hTX«Then the setup script will run the ``configure`` script, which checks for the presence of the X11 libraries and substitutes for variables in the file ``X11.buildinfo.in``:hUjÆh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMv hohhp]r(hyX#Then the setup script will run the r…r}r(hTX#Then the setup script will run the h`NhnNhohhUjÿubhß)r}r(hTX ``configure``hd}r(hf]hg]hh]hi]hl]uhUjÿhp]r hyX configurer …r }r (hTUhUjubahbhçubhyXf script, which checks for the presence of the X11 libraries and substitutes for variables in the file r …r}r(hTXf script, which checks for the presence of the X11 libraries and substitutes for variables in the file h`NhnNhohhUjÿubhß)r}r(hTX``X11.buildinfo.in``hd}r(hf]hg]hh]hi]hl]uhUjÿhp]rhyXX11.buildinfo.inr…r}r(hTUhUjubahbhçubhyX:…r}r(hTX:h`NhnNhohhUjÿubeubjÌ)r}r(hTXKbuildable: @BUILD_PACKAGE_BOOL@ cc-options: @X_CFLAGS@ ld-options: @X_LIBS@hUjÆh`hahbjÏhd}r(jÑjÒhi]hh]hf]hg]hl]uhnM| hohhp]rhyXKbuildable: @BUILD_PACKAGE_BOOL@ cc-options: @X_CFLAGS@ ld-options: @X_LIBS@r…r}r(hTUhUjubaubh})r }r!(hTXXThis generates a file ``X11.buildinfo`` supplying the parameters needed by later stages:hUjÆh`hahbhhd}r"(hf]hg]hh]hi]hl]uhnM€ hohhp]r#(hyXThis generates a file r$…r%}r&(hTXThis generates a file h`NhnNhohhUj ubhß)r'}r((hTX``X11.buildinfo``hd}r)(hf]hg]hh]hi]hl]uhUj hp]r*hyX X11.buildinfor+…r,}r-(hTUhUj'ubahbhçubhyX1 supplying the parameters needed by later stages:r.…r/}r0(hTX1 supplying the parameters needed by later stages:h`NhnNhohhUj ubeubjÌ)r1}r2(hTXObuildable: True cc-options: -I/usr/X11R6/include ld-options: -L/usr/X11R6/libhUjÆh`hahbjÏhd}r3(jÑjÒhi]hh]hf]hg]hl]uhnM… hohhp]r4hyXObuildable: True cc-options: -I/usr/X11R6/include ld-options: -L/usr/X11R6/libr5…r6}r7(hTUhUj1ubaubh})r8}r9(hTXûThe ``configure`` script also generates a header file ``include/HsX11Config.h`` containing C preprocessor defines recording the results of various tests. This file may be included by C source files and preprocessed Haskell source files in the package.hUjÆh`hahbhhd}r:(hf]hg]hh]hi]hl]uhnM‰ hohhp]r;(hyXThe r<…r=}r>(hTXThe h`NhnNhohhUj8ubhß)r?}r@(hTX ``configure``hd}rA(hf]hg]hh]hi]hl]uhUj8hp]rBhyX configurerC…rD}rE(hTUhUj?ubahbhçubhyX% script also generates a header file rF…rG}rH(hTX% script also generates a header file h`NhnNhohhUj8ubhß)rI}rJ(hTX``include/HsX11Config.h``hd}rK(hf]hg]hh]hi]hl]uhUj8hp]rLhyXinclude/HsX11Config.hrM…rN}rO(hTUhUjIubahbhçubhyX¬ containing C preprocessor defines recording the results of various tests. This file may be included by C source files and preprocessed Haskell source files in the package.rP…rQ}rR(hTX¬ containing C preprocessor defines recording the results of various tests. This file may be included by C source files and preprocessed Haskell source files in the package.h`NhnNhohhUj8ubeubhë)rS}rT(hTXÍPackages using these features will also need to list additional files such as ``configure``, templates for ``.buildinfo`` files, files named only in ``.buildinfo`` files, header files and so on in the :pkg-field:`extra-source-files` field to ensure that they are included in source distributions. They should also list files and directories generated by ``configure`` in the :pkg-field:`extra-tmp-files` field to ensure that they are removed by ``setup clean``.hUjÆh`hahbhîhd}rU(hf]hg]hh]hi]hl]uhnNhohhp]rVh})rW}rX(hTXÍPackages using these features will also need to list additional files such as ``configure``, templates for ``.buildinfo`` files, files named only in ``.buildinfo`` files, header files and so on in the :pkg-field:`extra-source-files` field to ensure that they are included in source distributions. They should also list files and directories generated by ``configure`` in the :pkg-field:`extra-tmp-files` field to ensure that they are removed by ``setup clean``.hUjSh`hahbhhd}rY(hf]hg]hh]hi]hl]uhnM hp]rZ(hyXNPackages using these features will also need to list additional files such as r[…r\}r](hTXNPackages using these features will also need to list additional files such as hUjWubhß)r^}r_(hTX ``configure``hd}r`(hf]hg]hh]hi]hl]uhUjWhp]rahyX configurerb…rc}rd(hTUhUj^ubahbhçubhyX, templates for re…rf}rg(hTX, templates for hUjWubhß)rh}ri(hTX``.buildinfo``hd}rj(hf]hg]hh]hi]hl]uhUjWhp]rkhyX .buildinforl…rm}rn(hTUhUjhubahbhçubhyX files, files named only in ro…rp}rq(hTX files, files named only in hUjWubhß)rr}rs(hTX``.buildinfo``hd}rt(hf]hg]hh]hi]hl]uhUjWhp]ruhyX .buildinforv…rw}rx(hTUhUjrubahbhçubhyX& files, header files and so on in the ry…rz}r{(hTX& files, header files and so on in the hUjWubjk)r|}r}(hTX:pkg-field:`extra-source-files`r~hUjWh`hahbjohd}r(UreftypeX pkg-fieldjqˆjrXextra-source-filesU refdomainXcabalr€hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM hp]rhß)r‚}rƒ(hTj~hd}r„(hf]hg]r…(j|j€Xcabal-pkg-fieldr†ehh]hi]hl]uhUj|hp]r‡hyXextra-source-filesrˆ…r‰}rŠ(hTUhUj‚ubahbhçubaubhyXz field to ensure that they are included in source distributions. They should also list files and directories generated by r‹…rŒ}r(hTXz field to ensure that they are included in source distributions. They should also list files and directories generated by hUjWubhß)rŽ}r(hTX ``configure``hd}r(hf]hg]hh]hi]hl]uhUjWhp]r‘hyX configurer’…r“}r”(hTUhUjŽubahbhçubhyX in the r•…r–}r—(hTX in the hUjWubjk)r˜}r™(hTX:pkg-field:`extra-tmp-files`ršhUjWh`hahbjohd}r›(UreftypeX pkg-fieldjqˆjrXextra-tmp-filesU refdomainXcabalrœhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM hp]rhß)rž}rŸ(hTjšhd}r (hf]hg]r¡(j|jœXcabal-pkg-fieldr¢ehh]hi]hl]uhUj˜hp]r£hyXextra-tmp-filesr¤…r¥}r¦(hTUhUjžubahbhçubaubhyX* field to ensure that they are removed by r§…r¨}r©(hTX* field to ensure that they are removed by hUjWubhß)rª}r«(hTX``setup clean``hd}r¬(hf]hg]hh]hi]hl]uhUjWhp]r­hyX setup cleanr®…r¯}r°(hTUhUjªubahbhçubhyX.…r±}r²(hTX.hUjWubeubaubh})r³}r´(hTXQuite often the files generated by ``configure`` need to be listed somewhere in the package description (for example, in the :pkg-field:`install-includes` field). However, we usually don't want generated files to be included in the source tarball. The solution is again provided by the ``.buildinfo`` file. In the above example, the following line should be added to ``X11.buildinfo``:hUjÆh`hahbhhd}rµ(hf]hg]hh]hi]hl]uhnM˜ hohhp]r¶(hyX#Quite often the files generated by r·…r¸}r¹(hTX#Quite often the files generated by h`NhnNhohhUj³ubhß)rº}r»(hTX ``configure``hd}r¼(hf]hg]hh]hi]hl]uhUj³hp]r½hyX configurer¾…r¿}rÀ(hTUhUjºubahbhçubhyXM need to be listed somewhere in the package description (for example, in the rÁ…rÂ}rÃ(hTXM need to be listed somewhere in the package description (for example, in the h`NhnNhohhUj³ubjk)rÄ}rÅ(hTX:pkg-field:`install-includes`rÆhUj³h`hahbjohd}rÇ(UreftypeX pkg-fieldjqˆjrXinstall-includesU refdomainXcabalrÈhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM˜ hp]rÉhß)rÊ}rË(hTjÆhd}rÌ(hf]hg]rÍ(j|jÈXcabal-pkg-fieldrÎehh]hi]hl]uhUjÄhp]rÏhyXinstall-includesrÐ…rÑ}rÒ(hTUhUjÊubahbhçubaubhyX† field). However, we usually don’t want generated files to be included in the source tarball. The solution is again provided by the rÓ…rÔ}rÕ(hTX„ field). However, we usually don't want generated files to be included in the source tarball. The solution is again provided by the h`NhnNhohhUj³ubhß)rÖ}r×(hTX``.buildinfo``hd}rØ(hf]hg]hh]hi]hl]uhUj³hp]rÙhyX .buildinforÚ…rÛ}rÜ(hTUhUjÖubahbhçubhyXC file. In the above example, the following line should be added to rÝ…rÞ}rß(hTXC file. In the above example, the following line should be added to h`NhnNhohhUj³ubhß)rà}rá(hTX``X11.buildinfo``hd}râ(hf]hg]hh]hi]hl]uhUj³hp]rãhyX X11.buildinforä…rå}ræ(hTUhUjàubahbhçubhyX:…rç}rè(hTX:h`NhnNhohhUj³ubeubjÌ)ré}rê(hTXinstall-includes: HsX11Config.hhUjÆh`hahbjÏhd}rë(jÑjÒhi]hh]hf]hg]hl]uhnM¡ hohhp]rìhyXinstall-includes: HsX11Config.hrí…rî}rï(hTUhUjéubaubh})rð}rñ(hTXOIn this way, the generated ``HsX11Config.h`` file won't be included in the source tarball in addition to ``HsX11Config.h.in``, but it will be copied to the right location during the install process. Packages that use custom ``Setup.hs`` scripts can update the necessary fields programmatically instead of using the ``.buildinfo`` file.hUjÆh`hahbhhd}rò(hf]hg]hh]hi]hl]uhnM£ hohhp]ró(hyXIn this way, the generated rô…rõ}rö(hTXIn this way, the generated h`NhnNhohhUjðubhß)r÷}rø(hTX``HsX11Config.h``hd}rù(hf]hg]hh]hi]hl]uhUjðhp]rúhyX HsX11Config.hrû…rü}rý(hTUhUj÷ubahbhçubhyX? file won’t be included in the source tarball in addition to rþ…rÿ}r (hTX= file won't be included in the source tarball in addition to h`NhnNhohhUjðubhß)r }r (hTX``HsX11Config.h.in``hd}r (hf]hg]hh]hi]hl]uhUjðhp]r hyXHsX11Config.h.inr …r }r (hTUhUj ubahbhçubhyXc, but it will be copied to the right location during the install process. Packages that use custom r …r }r (hTXc, but it will be copied to the right location during the install process. Packages that use custom h`NhnNhohhUjðubhß)r }r (hTX ``Setup.hs``hd}r (hf]hg]hh]hi]hl]uhUjðhp]r hyXSetup.hsr …r }r (hTUhUj ubahbhçubhyXO scripts can update the necessary fields programmatically instead of using the r …r }r (hTXO scripts can update the necessary fields programmatically instead of using the h`NhnNhohhUjðubhß)r }r (hTX``.buildinfo``hd}r (hf]hg]hh]hi]hl]uhUjðhp]r hyX .buildinfor …r }r (hTUhUj ubahbhçubhyX file.r …r }r (hTX file.h`NhnNhohhUjðubeubeubeubhV)r }r (hTUhUh^h`hahbhchd}r! (hf]hg]hh]hi]r" Uconditional-compilationr# ahl]r$ hauhnMª hohhp]r% (hr)r& }r' (hTXConditional compilationr( hUj h`hahbhvhd}r) (hf]hg]hh]hi]hl]uhnMª hohhp]r* hyXConditional compilationr+ …r, }r- (hTj( h`NhnNhohhUj& ubaubh})r. }r/ (hTXSometimes you want to write code that works with more than one version of a dependency. You can specify a range of versions for the dependency in the :pkg-field:`build-depends`, but how do you then write the code that can use different versions of the API?hUj h`hahbhhd}r0 (hf]hg]hh]hi]hl]uhnM¬ hohhp]r1 (hyX–Sometimes you want to write code that works with more than one version of a dependency. You can specify a range of versions for the dependency in the r2 …r3 }r4 (hTX–Sometimes you want to write code that works with more than one version of a dependency. You can specify a range of versions for the dependency in the h`NhnNhohhUj. ubjk)r5 }r6 (hTX:pkg-field:`build-depends`r7 hUj. h`hahbjohd}r8 (UreftypeX pkg-fieldjqˆjrX build-dependsU refdomainXcabalr9 hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM¬ hp]r: hß)r; }r< (hTj7 hd}r= (hf]hg]r> (j|j9 Xcabal-pkg-fieldr? ehh]hi]hl]uhUj5 hp]r@ hyX build-dependsrA …rB }rC (hTUhUj; ubahbhçubaubhyXP, but how do you then write the code that can use different versions of the API?rD …rE }rF (hTXP, but how do you then write the code that can use different versions of the API?h`NhnNhohhUj. ubeubh})rG }rH (hTXËHaskell lets you preprocess your code using the C preprocessor (either the real C preprocessor, or ``cpphs``). To enable this, add ``extensions: CPP`` to your package description. When using CPP, Cabal provides some pre-defined macros to let you test the version of dependent packages; for example, suppose your package works with either version 3 or version 4 of the ``base`` package, you could select the available version in your Haskell modules like this:hUj h`hahbhhd}rI (hf]hg]hh]hi]hl]uhnM± hohhp]rJ (hyXcHaskell lets you preprocess your code using the C preprocessor (either the real C preprocessor, or rK …rL }rM (hTXcHaskell lets you preprocess your code using the C preprocessor (either the real C preprocessor, or h`NhnNhohhUjG ubhß)rN }rO (hTX ``cpphs``hd}rP (hf]hg]hh]hi]hl]uhUjG hp]rQ hyXcpphsrR …rS }rT (hTUhUjN ubahbhçubhyX). To enable this, add rU …rV }rW (hTX). To enable this, add h`NhnNhohhUjG ubhß)rX }rY (hTX``extensions: CPP``hd}rZ (hf]hg]hh]hi]hl]uhUjG hp]r[ hyXextensions: CPPr\ …r] }r^ (hTUhUjX ubahbhçubhyXÚ to your package description. When using CPP, Cabal provides some pre-defined macros to let you test the version of dependent packages; for example, suppose your package works with either version 3 or version 4 of the r_ …r` }ra (hTXÚ to your package description. When using CPP, Cabal provides some pre-defined macros to let you test the version of dependent packages; for example, suppose your package works with either version 3 or version 4 of the h`NhnNhohhUjG ubhß)rb }rc (hTX``base``hd}rd (hf]hg]hh]hi]hl]uhUjG hp]re hyXbaserf …rg }rh (hTUhUjb ubahbhçubhyXS package, you could select the available version in your Haskell modules like this:ri …rj }rk (hTXS package, you could select the available version in your Haskell modules like this:h`NhnNhohhUjG ubeubjÌ)rl }rm (hTXp#if MIN_VERSION_base(4,0,0) ... code that works with base-4 ... #else ... code that works with base-3 ... #endifhUj h`hahbjÏhd}rn (j‰jXcppjÑjÒhi]hh]hf]j}hg]hl]uhnM¹ hohhp]ro hyXp#if MIN_VERSION_base(4,0,0) ... code that works with base-4 ... #else ... code that works with base-3 ... #endifrp …rq }rr (hTUhUjl ubaubh})rs }rt (hTX›In general, Cabal supplies a macro ``MIN_VERSION_``\ *``package``*\ ``_(A,B,C)`` for each package depended on via :pkg-field:`build-depends`. This macro is true if the actual version of the package in use is greater than or equal to ``A.B.C`` (using the conventional ordering on version numbers, which is lexicographic on the sequence, but numeric on each component, so for example 1.2.0 is greater than 1.0.3).hUj h`hahbhhd}ru (hf]hg]hh]hi]hl]uhnMÁ hohhp]rv (hyX#In general, Cabal supplies a macro rw …rx }ry (hTX#In general, Cabal supplies a macro h`NhnNhohhUjs ubhß)rz }r{ (hTX``MIN_VERSION_``hd}r| (hf]hg]hh]hi]hl]uhUjs hp]r} hyX MIN_VERSION_r~ …r }r€ (hTUhUjz ubahbhçubhyX…r }r‚ (hTX\ rƒ h`NhnNhohhUjs ubh¿)r„ }r… (hTX *``package``*hd}r† (hf]hg]hh]hi]hl]uhUjs hp]r‡ hyX ``package``rˆ …r‰ }rŠ (hTUhUj„ ubahbhÇubhyX…r‹ }rŒ (hTjƒ hUjs ubhß)r }rŽ (hTX ``_(A,B,C)``hd}r (hf]hg]hh]hi]hl]uhUjs hp]r hyX_(A,B,C)r‘ …r’ }r“ (hTUhUj ubahbhçubhyX" for each package depended on via r” …r• }r– (hTX" for each package depended on via h`NhnNhohhUjs ubjk)r— }r˜ (hTX:pkg-field:`build-depends`r™ hUjs h`hahbjohd}rš (UreftypeX pkg-fieldjqˆjrX build-dependsU refdomainXcabalr› hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnMÁ hp]rœ hß)r }rž (hTj™ hd}rŸ (hf]hg]r  (j|j› Xcabal-pkg-fieldr¡ ehh]hi]hl]uhUj— hp]r¢ hyX build-dependsr£ …r¤ }r¥ (hTUhUj ubahbhçubaubhyX]. This macro is true if the actual version of the package in use is greater than or equal to r¦ …r§ }r¨ (hTX]. This macro is true if the actual version of the package in use is greater than or equal to h`NhnNhohhUjs ubhß)r© }rª (hTX ``A.B.C``hd}r« (hf]hg]hh]hi]hl]uhUjs hp]r¬ hyXA.B.Cr­ …r® }r¯ (hTUhUj© ubahbhçubhyX© (using the conventional ordering on version numbers, which is lexicographic on the sequence, but numeric on each component, so for example 1.2.0 is greater than 1.0.3).r° …r± }r² (hTX© (using the conventional ordering on version numbers, which is lexicographic on the sequence, but numeric on each component, so for example 1.2.0 is greater than 1.0.3).h`NhnNhohhUjs ubeubh})r³ }r´ (hTX¨Since version 1.20, the ``MIN_TOOL_VERSION_``\ *``tool``* family of macros lets you condition on the version of build tools used to build the program (e.g. ``hsc2hs``).hUj h`hahbhhd}rµ (hf]hg]hh]hi]hl]uhnMÉ hohhp]r¶ (hyXSince version 1.20, the r· …r¸ }r¹ (hTXSince version 1.20, the h`NhnNhohhUj³ ubhß)rº }r» (hTX``MIN_TOOL_VERSION_``hd}r¼ (hf]hg]hh]hi]hl]uhUj³ hp]r½ hyXMIN_TOOL_VERSION_r¾ …r¿ }rÀ (hTUhUjº ubahbhçubhyX…rÁ }r (hTX\ h`NhnNhohhUj³ ubh¿)rà }rÄ (hTX *``tool``*hd}rÅ (hf]hg]hh]hi]hl]uhUj³ hp]rÆ hyX``tool``rÇ …rÈ }rÉ (hTUhUjà ubahbhÇubhyXc family of macros lets you condition on the version of build tools used to build the program (e.g. rÊ …rË }rÌ (hTXc family of macros lets you condition on the version of build tools used to build the program (e.g. h`NhnNhohhUj³ ubhß)rÍ }rÎ (hTX ``hsc2hs``hd}rÏ (hf]hg]hh]hi]hl]uhUj³ hp]rÐ hyXhsc2hsrÑ …rÒ }rÓ (hTUhUjÍ ubahbhçubhyX).rÔ …rÕ }rÖ (hTX).h`NhnNhohhUj³ ubeubh})r× }rØ (hTX=Since version 1.24, the macro ``CURRENT_COMPONENT_ID``, which expands to the string of the component identifier that uniquely identifies this component. Furthermore, if the package is a library, the macro ``CURRENT_PACKAGE_KEY`` records the identifier that was passed to GHC for use in symbols and for type equality.hUj h`hahbhhd}rÙ (hf]hg]hh]hi]hl]uhnMÍ hohhp]rÚ (hyXSince version 1.24, the macro rÛ …rÜ }rÝ (hTXSince version 1.24, the macro h`NhnNhohhUj× ubhß)rÞ }rß (hTX``CURRENT_COMPONENT_ID``hd}rà (hf]hg]hh]hi]hl]uhUj× hp]rá hyXCURRENT_COMPONENT_IDrâ …rã }rä (hTUhUjÞ ubahbhçubhyX˜, which expands to the string of the component identifier that uniquely identifies this component. Furthermore, if the package is a library, the macro rå …ræ }rç (hTX˜, which expands to the string of the component identifier that uniquely identifies this component. Furthermore, if the package is a library, the macro h`NhnNhohhUj× ubhß)rè }ré (hTX``CURRENT_PACKAGE_KEY``hd}rê (hf]hg]hh]hi]hl]uhUj× hp]rë hyXCURRENT_PACKAGE_KEYrì …rí }rî (hTUhUjè ubahbhçubhyXX records the identifier that was passed to GHC for use in symbols and for type equality.rï …rð }rñ (hTXX records the identifier that was passed to GHC for use in symbols and for type equality.h`NhnNhohhUj× ubeubh})rò }ró (hTXuSince version 2.0, the macro ``CURRENT_PACKAGE_VERSION`` expands to the string version number of the current package.hUj h`hahbhhd}rô (hf]hg]hh]hi]hl]uhnMÓ hohhp]rõ (hyXSince version 2.0, the macro rö …r÷ }rø (hTXSince version 2.0, the macro h`NhnNhohhUjò ubhß)rù }rú (hTX``CURRENT_PACKAGE_VERSION``hd}rû (hf]hg]hh]hi]hl]uhUjò hp]rü hyXCURRENT_PACKAGE_VERSIONrý …rþ }rÿ (hTUhUjù ubahbhçubhyX= expands to the string version number of the current package.r …r }r (hTX= expands to the string version number of the current package.h`NhnNhohhUjò ubeubh})r }r (hTX¼Cabal places the definitions of these macros into an automatically-generated header file, which is included when preprocessing Haskell source code by passing options to the C preprocessor.r hUj h`hahbhhd}r (hf]hg]hh]hi]hl]uhnMÖ hohhp]r hyX¼Cabal places the definitions of these macros into an automatically-generated header file, which is included when preprocessing Haskell source code by passing options to the C preprocessor.r …r }r (hTj h`NhnNhohhUj ubaubh})r }r (hTX¾Cabal also allows to detect when the source code is being used for generating documentation. The ``__HADDOCK_VERSION__`` macro is defined only when compiling via Haddock_ instead of a normal Haskell compiler. The value of the ``__HADDOCK_VERSION__`` macro is defined as ``A*1000 + B*10 + C``, where ``A.B.C`` is the Haddock version. This can be useful for working around bugs in Haddock or generating prettier documentation in some special cases.hUj h`hahbhhd}r (hf]hg]hh]hi]hl]uhnMÛ hohhp]r (hyXaCabal also allows to detect when the source code is being used for generating documentation. The r …r }r (hTXaCabal also allows to detect when the source code is being used for generating documentation. The h`NhnNhohhUj ubhß)r }r (hTX``__HADDOCK_VERSION__``hd}r (hf]hg]hh]hi]hl]uhUj hp]r hyX__HADDOCK_VERSION__r …r }r (hTUhUj ubahbhçubhyX* macro is defined only when compiling via r …r }r (hTX* macro is defined only when compiling via h`NhnNhohhUj ubj?)r }r (hTXHaddock_jBKhUj hbjChd}r (UnameXHaddockj~Xhttp://www.haskell.org/haddock/r hi]hh]hf]hg]hl]uhp]r hyXHaddockr! …r" }r# (hTUhUj ubaubhyX8 instead of a normal Haskell compiler. The value of the r$ …r% }r& (hTX8 instead of a normal Haskell compiler. The value of the h`NhnNhohhUj ubhß)r' }r( (hTX``__HADDOCK_VERSION__``hd}r) (hf]hg]hh]hi]hl]uhUj hp]r* hyX__HADDOCK_VERSION__r+ …r, }r- (hTUhUj' ubahbhçubhyX macro is defined as r. …r/ }r0 (hTX macro is defined as h`NhnNhohhUj ubhß)r1 }r2 (hTX``A*1000 + B*10 + C``hd}r3 (hf]hg]hh]hi]hl]uhUj hp]r4 hyXA*1000 + B*10 + Cr5 …r6 }r7 (hTUhUj1 ubahbhçubhyX, where r8 …r9 }r: (hTX, where h`NhnNhohhUj ubhß)r; }r< (hTX ``A.B.C``hd}r= (hf]hg]hh]hi]hl]uhUj hp]r> hyXA.B.Cr? …r@ }rA (hTUhUj; ubahbhçubhyXŠ is the Haddock version. This can be useful for working around bugs in Haddock or generating prettier documentation in some special cases.rB …rC }rD (hTXŠ is the Haddock version. This can be useful for working around bugs in Haddock or generating prettier documentation in some special cases.h`NhnNhohhUj ubeubeubhV)rE }rF (hTUhYKhUh^h`hahbhchd}rG (hf]hg]hh]hi]rH Umore-complex-packagesrI ahl]rJ h5auhnMå hohhp]rK (hr)rL }rM (hTXMore complex packagesrN hUjE h`hahbhvhd}rO (hf]hg]hh]hi]hl]uhnMå hohhp]rP hyXMore complex packagesrQ …rR }rS (hTjN h`NhnNhohhUjL ubaubh})rT }rU (hTXWFor packages that don't fit the simple schemes described above, you have a few options:rV hUjE h`hahbhhd}rW (hf]hg]hh]hi]hl]uhnMç hohhp]rX hyXYFor packages that don’t fit the simple schemes described above, you have a few options:rY …rZ }r[ (hTjV h`NhnNhohhUjT ubaubh‡)r\ }r] (hTUhUjE h`hahbhŠhd}r^ (hŒX-hi]hh]hf]hg]hl]uhnMê hohhp]r_ (hŽ)r` }ra (hTXÇBy using the :pkg-field:`build-type` ``Custom``, you can supply your own ``Setup.hs`` file, and customize the simple build infrastructure using *hooks*. These allow you to perform additional actions before and after each command is run, and also to specify additional preprocessors. A typical ``Setup.hs`` may look like this: .. code-block:: haskell import Distribution.Simple main = defaultMainWithHooks simpleUserHooks { postHaddock = posthaddock } posthaddock args flags desc info = .... See ``UserHooks`` in `Distribution.Simple <../release/cabal-latest/doc/API/Cabal/Distribution-Simple.html>`__ for the details, but note that this interface is experimental, and likely to change in future releases. If you use a custom ``Setup.hs`` file you should strongly consider adding a :pkg-section:`custom-setup` stanza with a :pkg-field:`custom-setup:setup-depends` field to ensure that your setup script does not break with future dependency versions. hUj\ h`hahbh‘hd}rb (hf]hg]hh]hi]hl]uhnNhohhp]rc (h})rd }re (hTXEBy using the :pkg-field:`build-type` ``Custom``, you can supply your own ``Setup.hs`` file, and customize the simple build infrastructure using *hooks*. These allow you to perform additional actions before and after each command is run, and also to specify additional preprocessors. A typical ``Setup.hs`` may look like this:hUj` h`hahbhhd}rf (hf]hg]hh]hi]hl]uhnMê hp]rg (hyX By using the rh …ri }rj (hTX By using the hUjd ubjk)rk }rl (hTX:pkg-field:`build-type`rm hUjd h`hahbjohd}rn (UreftypeX pkg-fieldjqˆjrX build-typeU refdomainXcabalro hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnMê hp]rp hß)rq }rr (hTjm hd}rs (hf]hg]rt (j|jo Xcabal-pkg-fieldru ehh]hi]hl]uhUjk hp]rv hyX build-typerw …rx }ry (hTUhUjq ubahbhçubaubhyX …rz }r{ (hTX hUjd ubhß)r| }r} (hTX ``Custom``hd}r~ (hf]hg]hh]hi]hl]uhUjd hp]r hyXCustomr€ …r }r‚ (hTUhUj| ubahbhçubhyX, you can supply your own rƒ …r„ }r… (hTX, you can supply your own hUjd ubhß)r† }r‡ (hTX ``Setup.hs``hd}rˆ (hf]hg]hh]hi]hl]uhUjd hp]r‰ hyXSetup.hsrŠ …r‹ }rŒ (hTUhUj† ubahbhçubhyX; file, and customize the simple build infrastructure using r …rŽ }r (hTX; file, and customize the simple build infrastructure using hUjd ubh¿)r }r‘ (hTX*hooks*hd}r’ (hf]hg]hh]hi]hl]uhUjd hp]r“ hyXhooksr” …r• }r– (hTUhUj ubahbhÇubhyXŽ. These allow you to perform additional actions before and after each command is run, and also to specify additional preprocessors. A typical r— …r˜ }r™ (hTXŽ. These allow you to perform additional actions before and after each command is run, and also to specify additional preprocessors. A typical hUjd ubhß)rš }r› (hTX ``Setup.hs``hd}rœ (hf]hg]hh]hi]hl]uhUjd hp]r hyXSetup.hsrž …rŸ }r  (hTUhUjš ubahbhçubhyX may look like this:r¡ …r¢ }r£ (hTX may look like this:hUjd ubeubjÌ)r¤ }r¥ (hTXimport Distribution.Simple main = defaultMainWithHooks simpleUserHooks { postHaddock = posthaddock } posthaddock args flags desc info = ....hUj` h`hahbjÏhd}r¦ (j‰jXhaskelljÑjÒhi]hh]hf]j}hg]hl]uhnMð hp]r§ hyXimport Distribution.Simple main = defaultMainWithHooks simpleUserHooks { postHaddock = posthaddock } posthaddock args flags desc info = ....r¨ …r© }rª (hTUhUj¤ ubaubh})r« }r¬ (hTXÕSee ``UserHooks`` in `Distribution.Simple <../release/cabal-latest/doc/API/Cabal/Distribution-Simple.html>`__ for the details, but note that this interface is experimental, and likely to change in future releases.hUj` h`hahbhhd}r­ (hf]hg]hh]hi]hl]uhnM÷ hp]r® (hyXSee r¯ …r° }r± (hTXSee hUj« ubhß)r² }r³ (hTX ``UserHooks``hd}r´ (hf]hg]hh]hi]hl]uhUj« hp]rµ hyX UserHooksr¶ …r· }r¸ (hTUhUj² ubahbhçubhyX in r¹ …rº }r» (hTX in hUj« ubj?)r¼ }r½ (hTXX`Distribution.Simple <../release/cabal-latest/doc/API/Cabal/Distribution-Simple.html>`__hd}r¾ (UnameXDistribution.Simplej~X>../release/cabal-latest/doc/API/Cabal/Distribution-Simple.htmlhi]hh]hf]hg]hl]uhUj« hp]r¿ hyXDistribution.SimplerÀ …rÁ }r (hTUhUj¼ ubahbjCubhyXh for the details, but note that this interface is experimental, and likely to change in future releases.rà …rÄ }rÅ (hTXh for the details, but note that this interface is experimental, and likely to change in future releases.hUj« ubeubh})rÆ }rÇ (hTXôIf you use a custom ``Setup.hs`` file you should strongly consider adding a :pkg-section:`custom-setup` stanza with a :pkg-field:`custom-setup:setup-depends` field to ensure that your setup script does not break with future dependency versions.hUj` h`hahbhhd}rÈ (hf]hg]hh]hi]hl]uhnMü hp]rÉ (hyXIf you use a custom rÊ …rË }rÌ (hTXIf you use a custom hUjÆ ubhß)rÍ }rÎ (hTX ``Setup.hs``hd}rÏ (hf]hg]hh]hi]hl]uhUjÆ hp]rÐ hyXSetup.hsrÑ …rÒ }rÓ (hTUhUjÍ ubahbhçubhyX, file you should strongly consider adding a rÔ …rÕ }rÖ (hTX, file you should strongly consider adding a hUjÆ ubjk)r× }rØ (hTX:pkg-section:`custom-setup`rÙ hUjÆ h`hahbjohd}rÚ (UreftypeX pkg-sectionjqˆjrX custom-setupU refdomainXcabalrÛ hi]hh]U refexplicit‰hf]hg]hl]jtjuuhnMü hp]rÜ hß)rÝ }rÞ (hTjÙ hd}rß (hf]hg]rà (j|jÛ Xcabal-pkg-sectionrá ehh]hi]hl]uhUj× hp]râ hyX custom-setuprã …rä }rå (hTUhUjÝ ubahbhçubaubhyX stanza with a ræ …rç }rè (hTX stanza with a hUjÆ ubjk)ré }rê (hTX':pkg-field:`custom-setup:setup-depends`rë hUjÆ h`hahbjohd}rì (UreftypeX pkg-fieldjqˆjrX setup-dependsU refdomainXcabalrí hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹X custom-setupuhnMü hp]rî hß)rï }rð (hTjë hd}rñ (hf]hg]rò (j|jí Xcabal-pkg-fieldró ehh]hi]hl]uhUjé hp]rô hyXcustom-setup:setup-dependsrõ …rö }r÷ (hTUhUjï ubahbhçubaubhyXW field to ensure that your setup script does not break with future dependency versions.rø …rù }rú (hTXW field to ensure that your setup script does not break with future dependency versions.hUjÆ ubeubeubhŽ)rû }rü (hTX^You could delegate all the work to ``make``, though this is unlikely to be very portable. Cabal supports this with the :pkg-field:`build-type` ``Make`` and a trivial setup library `Distribution.Make <../release/cabal-latest/doc/API/Cabal/Distribution-Make.html>`__, which simply parses the command line arguments and invokes ``make``. Here ``Setup.hs`` should look like this: .. code-block:: haskell import Distribution.Make main = defaultMain The root directory of the package should contain a ``configure`` script, and, after that has run, a ``Makefile`` with a default target that builds the package, plus targets ``install``, ``register``, ``unregister``, ``clean``, ``dist`` and ``docs``. Some options to commands are passed through as follows: - The ``--with-hc-pkg``, ``--prefix``, ``--bindir``, ``--libdir``, ``--dynlibdir``, ``--datadir``, ``--libexecdir`` and ``--sysconfdir`` options to the ``configure`` command are passed on to the ``configure`` script. In addition the value of the ``--with-compiler`` option is passed in a ``--with-hc`` option and all options specified with ``--configure-option=`` are passed on. - The ``--destdir`` option to the ``copy`` command becomes a setting of a ``destdir`` variable on the invocation of ``make copy``. The supplied ``Makefile`` should provide a ``copy`` target, which will probably look like this: .. code-block:: make copy : $(MAKE) install prefix=$(destdir)/$(prefix) \ bindir=$(destdir)/$(bindir) \ libdir=$(destdir)/$(libdir) \ dynlibdir=$(destdir)/$(dynlibdir) \ datadir=$(destdir)/$(datadir) \ libexecdir=$(destdir)/$(libexecdir) \ sysconfdir=$(destdir)/$(sysconfdir) \ hUj\ h`Nhbh‘hd}rý (hf]hg]hh]hi]hl]uhnNhohhp]rþ (h})rÿ }r (hTXwYou could delegate all the work to ``make``, though this is unlikely to be very portable. Cabal supports this with the :pkg-field:`build-type` ``Make`` and a trivial setup library `Distribution.Make <../release/cabal-latest/doc/API/Cabal/Distribution-Make.html>`__, which simply parses the command line arguments and invokes ``make``. Here ``Setup.hs`` should look like this:hUjû h`hahbhhd}r (hf]hg]hh]hi]hl]uhnM hp]r (hyX#You could delegate all the work to r …r }r (hTX#You could delegate all the work to hUjÿ ubhß)r }r (hTX``make``hd}r (hf]hg]hh]hi]hl]uhUjÿ hp]r hyXmaker …r }r (hTUhUj ubahbhçubhyXL, though this is unlikely to be very portable. Cabal supports this with the r …r }r (hTXL, though this is unlikely to be very portable. Cabal supports this with the hUjÿ ubjk)r }r (hTX:pkg-field:`build-type`r hUjÿ h`hahbjohd}r (UreftypeX pkg-fieldjqˆjrX build-typeU refdomainXcabalr hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM hp]r hß)r }r (hTj hd}r (hf]hg]r (j|j Xcabal-pkg-fieldr ehh]hi]hl]uhUj hp]r hyX build-typer …r }r (hTUhUj ubahbhçubaubhyX …r }r (hTX hUjÿ ubhß)r! }r" (hTX``Make``hd}r# (hf]hg]hh]hi]hl]uhUjÿ hp]r$ hyXMaker% …r& }r' (hTUhUj! ubahbhçubhyX and a trivial setup library r( …r) }r* (hTX and a trivial setup library hUjÿ ubj?)r+ }r, (hTXT`Distribution.Make <../release/cabal-latest/doc/API/Cabal/Distribution-Make.html>`__hd}r- (UnameXDistribution.Makej~X<../release/cabal-latest/doc/API/Cabal/Distribution-Make.htmlhi]hh]hf]hg]hl]uhUjÿ hp]r. hyXDistribution.Maker/ …r0 }r1 (hTUhUj+ ubahbjCubhyX=, which simply parses the command line arguments and invokes r2 …r3 }r4 (hTX=, which simply parses the command line arguments and invokes hUjÿ ubhß)r5 }r6 (hTX``make``hd}r7 (hf]hg]hh]hi]hl]uhUjÿ hp]r8 hyXmaker9 …r: }r; (hTUhUj5 ubahbhçubhyX. Here r< …r= }r> (hTX. Here hUjÿ ubhß)r? }r@ (hTX ``Setup.hs``hd}rA (hf]hg]hh]hi]hl]uhUjÿ hp]rB hyXSetup.hsrC …rD }rE (hTUhUj? ubahbhçubhyX should look like this:rF …rG }rH (hTX should look like this:hUjÿ ubeubjÌ)rI }rJ (hTX+import Distribution.Make main = defaultMainhUjû h`hahbjÏhd}rK (j‰jXhaskelljÑjÒhi]hh]hf]j}hg]hl]uhnM hp]rL hyX+import Distribution.Make main = defaultMainrM …rN }rO (hTUhUjI ubaubh})rP }rQ (hTX1The root directory of the package should contain a ``configure`` script, and, after that has run, a ``Makefile`` with a default target that builds the package, plus targets ``install``, ``register``, ``unregister``, ``clean``, ``dist`` and ``docs``. Some options to commands are passed through as follows:hUjû h`hahbhhd}rR (hf]hg]hh]hi]hl]uhnM hp]rS (hyX3The root directory of the package should contain a rT …rU }rV (hTX3The root directory of the package should contain a hUjP ubhß)rW }rX (hTX ``configure``hd}rY (hf]hg]hh]hi]hl]uhUjP hp]rZ hyX configurer[ …r\ }r] (hTUhUjW ubahbhçubhyX$ script, and, after that has run, a r^ …r_ }r` (hTX$ script, and, after that has run, a hUjP ubhß)ra }rb (hTX ``Makefile``hd}rc (hf]hg]hh]hi]hl]uhUjP hp]rd hyXMakefilere …rf }rg (hTUhUja ubahbhçubhyX= with a default target that builds the package, plus targets rh …ri }rj (hTX= with a default target that builds the package, plus targets hUjP ubhß)rk }rl (hTX ``install``hd}rm (hf]hg]hh]hi]hl]uhUjP hp]rn hyXinstallro …rp }rq (hTUhUjk ubahbhçubhyX, rr …rs }rt (hTX, ru hUjP ubhß)rv }rw (hTX ``register``hd}rx (hf]hg]hh]hi]hl]uhUjP hp]ry hyXregisterrz …r{ }r| (hTUhUjv ubahbhçubhyX, r} …r~ }r (hTX, hUjP ubhß)r€ }r (hTX``unregister``hd}r‚ (hf]hg]hh]hi]hl]uhUjP hp]rƒ hyX unregisterr„ …r… }r† (hTUhUj€ ubahbhçubhyX, r‡ …rˆ }r‰ (hTX, hUjP ubhß)rŠ }r‹ (hTX ``clean``hd}rŒ (hf]hg]hh]hi]hl]uhUjP hp]r hyXcleanrŽ …r }r (hTUhUjŠ ubahbhçubhyX, r‘ …r’ }r“ (hTju hUjP ubhß)r” }r• (hTX``dist``hd}r– (hf]hg]hh]hi]hl]uhUjP hp]r— hyXdistr˜ …r™ }rš (hTUhUj” ubahbhçubhyX and r› …rœ }r (hTX and hUjP ubhß)rž }rŸ (hTX``docs``hd}r  (hf]hg]hh]hi]hl]uhUjP hp]r¡ hyXdocsr¢ …r£ }r¤ (hTUhUjž ubahbhçubhyX9. Some options to commands are passed through as follows:r¥ …r¦ }r§ (hTX9. Some options to commands are passed through as follows:hUjP ubeubh‡)r¨ }r© (hTUhUjû h`hahbhŠhd}rª (hŒX-hi]hh]hf]hg]hl]uhnM hp]r« (hŽ)r¬ }r­ (hTXyThe ``--with-hc-pkg``, ``--prefix``, ``--bindir``, ``--libdir``, ``--dynlibdir``, ``--datadir``, ``--libexecdir`` and ``--sysconfdir`` options to the ``configure`` command are passed on to the ``configure`` script. In addition the value of the ``--with-compiler`` option is passed in a ``--with-hc`` option and all options specified with ``--configure-option=`` are passed on. hd}r® (hf]hg]hh]hi]hl]uhUj¨ hp]r¯ h})r° }r± (hTXxThe ``--with-hc-pkg``, ``--prefix``, ``--bindir``, ``--libdir``, ``--dynlibdir``, ``--datadir``, ``--libexecdir`` and ``--sysconfdir`` options to the ``configure`` command are passed on to the ``configure`` script. In addition the value of the ``--with-compiler`` option is passed in a ``--with-hc`` option and all options specified with ``--configure-option=`` are passed on.hUj¬ h`hahbhhd}r² (hf]hg]hh]hi]hl]uhnM hp]r³ (hyXThe r´ …rµ }r¶ (hTXThe hUj° ubhß)r· }r¸ (hTX``--with-hc-pkg``hd}r¹ (hf]hg]hh]hi]hl]uhUj° hp]rº hyX --with-hc-pkgr» …r¼ }r½ (hTUhUj· ubahbhçubhyX, r¾ …r¿ }rÀ (hTX, rÁ hUj° ubhß)r }rà (hTX ``--prefix``hd}rÄ (hf]hg]hh]hi]hl]uhUj° hp]rÅ hyX--prefixrÆ …rÇ }rÈ (hTUhUj ubahbhçubhyX, rÉ …rÊ }rË (hTX, hUj° ubhß)rÌ }rÍ (hTX ``--bindir``hd}rÎ (hf]hg]hh]hi]hl]uhUj° hp]rÏ hyX--bindirrÐ …rÑ }rÒ (hTUhUjÌ ubahbhçubhyX, rÓ …rÔ }rÕ (hTX, hUj° ubhß)rÖ }r× (hTX ``--libdir``hd}rØ (hf]hg]hh]hi]hl]uhUj° hp]rÙ hyX--libdirrÚ …rÛ }rÜ (hTUhUjÖ ubahbhçubhyX, rÝ …rÞ }rß (hTX, hUj° ubhß)rà }rá (hTX``--dynlibdir``hd}râ (hf]hg]hh]hi]hl]uhUj° hp]rã hyX --dynlibdirrä …rå }ræ (hTUhUjà ubahbhçubhyX, rç …rè }ré (hTX, hUj° ubhß)rê }rë (hTX ``--datadir``hd}rì (hf]hg]hh]hi]hl]uhUj° hp]rí hyX --datadirrî …rï }rð (hTUhUjê ubahbhçubhyX, rñ …rò }ró (hTjÁ hUj° ubhß)rô }rõ (hTX``--libexecdir``hd}rö (hf]hg]hh]hi]hl]uhUj° hp]r÷ hyX --libexecdirrø …rù }rú (hTUhUjô ubahbhçubhyX and rû …rü }rý (hTX and hUj° ubhß)rþ }rÿ (hTX``--sysconfdir``hd}r (hf]hg]hh]hi]hl]uhUj° hp]r hyX --sysconfdirr …r }r (hTUhUjþ ubahbhçubhyX options to the r …r }r (hTX options to the hUj° ubhß)r }r (hTX ``configure``hd}r (hf]hg]hh]hi]hl]uhUj° hp]r hyX configurer …r }r (hTUhUj ubahbhçubhyX command are passed on to the r …r }r (hTX command are passed on to the hUj° ubhß)r }r (hTX ``configure``hd}r (hf]hg]hh]hi]hl]uhUj° hp]r hyX configurer …r }r (hTUhUj ubahbhçubhyX& script. In addition the value of the r …r }r (hTX& script. In addition the value of the hUj° ubhß)r }r (hTX``--with-compiler``hd}r (hf]hg]hh]hi]hl]uhUj° hp]r hyX--with-compilerr …r! }r" (hTUhUj ubahbhçubhyX option is passed in a r# …r$ }r% (hTX option is passed in a hUj° ubhß)r& }r' (hTX ``--with-hc``hd}r( (hf]hg]hh]hi]hl]uhUj° hp]r) hyX --with-hcr* …r+ }r, (hTUhUj& ubahbhçubhyX' option and all options specified with r- …r. }r/ (hTX' option and all options specified with hUj° ubhß)r0 }r1 (hTX``--configure-option=``hd}r2 (hf]hg]hh]hi]hl]uhUj° hp]r3 hyX--configure-option=r4 …r5 }r6 (hTUhUj0 ubahbhçubhyX are passed on.r7 …r8 }r9 (hTX are passed on.hUj° ubeubahbh‘ubhŽ)r: }r; (hTX±The ``--destdir`` option to the ``copy`` command becomes a setting of a ``destdir`` variable on the invocation of ``make copy``. The supplied ``Makefile`` should provide a ``copy`` target, which will probably look like this: .. code-block:: make copy : $(MAKE) install prefix=$(destdir)/$(prefix) \ bindir=$(destdir)/$(bindir) \ libdir=$(destdir)/$(libdir) \ dynlibdir=$(destdir)/$(dynlibdir) \ datadir=$(destdir)/$(datadir) \ libexecdir=$(destdir)/$(libexecdir) \ sysconfdir=$(destdir)/$(sysconfdir) \ hd}r< (hf]hg]hh]hi]hl]uhUj¨ hp]r= (h})r> }r? (hTXàThe ``--destdir`` option to the ``copy`` command becomes a setting of a ``destdir`` variable on the invocation of ``make copy``. The supplied ``Makefile`` should provide a ``copy`` target, which will probably look like this:hUj: h`hahbhhd}r@ (hf]hg]hh]hi]hl]uhnM hp]rA (hyXThe rB …rC }rD (hTXThe hUj> ubhß)rE }rF (hTX ``--destdir``hd}rG (hf]hg]hh]hi]hl]uhUj> hp]rH hyX --destdirrI …rJ }rK (hTUhUjE ubahbhçubhyX option to the rL …rM }rN (hTX option to the hUj> ubhß)rO }rP (hTX``copy``hd}rQ (hf]hg]hh]hi]hl]uhUj> hp]rR hyXcopyrS …rT }rU (hTUhUjO ubahbhçubhyX command becomes a setting of a rV …rW }rX (hTX command becomes a setting of a hUj> ubhß)rY }rZ (hTX ``destdir``hd}r[ (hf]hg]hh]hi]hl]uhUj> hp]r\ hyXdestdirr] …r^ }r_ (hTUhUjY ubahbhçubhyX variable on the invocation of r` …ra }rb (hTX variable on the invocation of hUj> ubhß)rc }rd (hTX ``make copy``hd}re (hf]hg]hh]hi]hl]uhUj> hp]rf hyX make copyrg …rh }ri (hTUhUjc ubahbhçubhyX. The supplied rj …rk }rl (hTX. The supplied hUj> ubhß)rm }rn (hTX ``Makefile``hd}ro (hf]hg]hh]hi]hl]uhUj> hp]rp hyXMakefilerq …rr }rs (hTUhUjm ubahbhçubhyX should provide a rt …ru }rv (hTX should provide a hUj> ubhß)rw }rx (hTX``copy``hd}ry (hf]hg]hh]hi]hl]uhUj> hp]rz hyXcopyr{ …r| }r} (hTUhUjw ubahbhçubhyX, target, which will probably look like this:r~ …r }r€ (hTX, target, which will probably look like this:hUj> ubeubjÌ)r }r‚ (hTX˜copy : $(MAKE) install prefix=$(destdir)/$(prefix) \ bindir=$(destdir)/$(bindir) \ libdir=$(destdir)/$(libdir) \ dynlibdir=$(destdir)/$(dynlibdir) \ datadir=$(destdir)/$(datadir) \ libexecdir=$(destdir)/$(libexecdir) \ sysconfdir=$(destdir)/$(sysconfdir) \hUj: h`hahbjÏhd}rƒ (j‰jXmakejÑjÒhi]hh]hf]j}hg]hl]uhnM hp]r„ hyX˜copy : $(MAKE) install prefix=$(destdir)/$(prefix) \ bindir=$(destdir)/$(bindir) \ libdir=$(destdir)/$(libdir) \ dynlibdir=$(destdir)/$(dynlibdir) \ datadir=$(destdir)/$(datadir) \ libexecdir=$(destdir)/$(libexecdir) \ sysconfdir=$(destdir)/$(sysconfdir) \r… …r† }r‡ (hTUhUj ubaubehbh‘ubeubeubhŽ)rˆ }r‰ (hTXFinally, with the :pkg-field:`build-type` ``Custom``, you can also write your own setup script from scratch. It must conform to the interface described in the section on `building and installing packages `__, and you may use the Cabal library for all or part of the work. One option is to copy the source of ``Distribution.Simple``, and alter it for your needs. Good luck. hUj\ h`hahbh‘hd}rŠ (hf]hg]hh]hi]hl]uhnNhohhp]r‹ h})rŒ }r (hTXŽFinally, with the :pkg-field:`build-type` ``Custom``, you can also write your own setup script from scratch. It must conform to the interface described in the section on `building and installing packages `__, and you may use the Cabal library for all or part of the work. One option is to copy the source of ``Distribution.Simple``, and alter it for your needs. Good luck.hUjˆ h`hahbhhd}rŽ (hf]hg]hh]hi]hl]uhnM* hp]r (hyXFinally, with the r …r‘ }r’ (hTXFinally, with the hUjŒ ubjk)r“ }r” (hTX:pkg-field:`build-type`r• hUjŒ h`hahbjohd}r– (UreftypeX pkg-fieldjqˆjrX build-typeU refdomainXcabalr— hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹jÌuhnM* hp]r˜ hß)r™ }rš (hTj• hd}r› (hf]hg]rœ (j|j— Xcabal-pkg-fieldr ehh]hi]hl]uhUj“ hp]rž hyX build-typerŸ …r  }r¡ (hTUhUj™ ubahbhçubaubhyX …r¢ }r£ (hTX hUjŒ ubhß)r¤ }r¥ (hTX ``Custom``hd}r¦ (hf]hg]hh]hi]hl]uhUjŒ hp]r§ hyXCustomr¨ …r© }rª (hTUhUj¤ ubahbhçubhyXv, you can also write your own setup script from scratch. It must conform to the interface described in the section on r« …r¬ }r­ (hTXv, you can also write your own setup script from scratch. It must conform to the interface described in the section on hUjŒ ubj?)r® }r¯ (hTX?`building and installing packages `__hd}r° (UnameX building and installing packagesj~Xinstalling-packages.htmlhi]hh]hf]hg]hl]uhUjŒ hp]r± hyX building and installing packagesr² …r³ }r´ (hTUhUj® ubahbjCubhyXe, and you may use the Cabal library for all or part of the work. One option is to copy the source of rµ …r¶ }r· (hTXe, and you may use the Cabal library for all or part of the work. One option is to copy the source of hUjŒ ubhß)r¸ }r¹ (hTX``Distribution.Simple``hd}rº (hf]hg]hh]hi]hl]uhUjŒ hp]r» hyXDistribution.Simpler¼ …r½ }r¾ (hTUhUj¸ ubahbhçubhyX), and alter it for your needs. Good luck.r¿ …rÀ }rÁ (hTX), and alter it for your needs. Good luck.hUjŒ ubeubaubeubjP)r }rà (hTX[-*- rst -*- This file contains commonly used link-references See also "extlinks" in conf.pyhUjE h`cdocutils.nodes reprunicode rÄ Xdoc/references.incrÅ …rÆ }rÇ bhbjShd}rÈ (jÑjÒhi]hh]hf]hg]hl]uhnKhohhp]rÉ hyX[-*- rst -*- This file contains commonly used link-references See also "extlinks" in conf.pyrÊ …rË }rÌ (hTUhUj ubaubj )rÍ }rÎ (hTX .. _`Package Versioning Policy`:hYKhUjE h`jÆ hbj£hd}rÏ (hi]hh]hf]hg]hl]jEUpackage-versioning-policyrÐ uhnM8 hohhp]ubj )rÑ }rÒ (hTX .. _PVP: http://pvp.haskell.org/hYKhUjE h`jÆ Uexpect_referenced_by_namerÓ }rÔ hjÍ shbj£hd}rÕ (j~Xhttp://pvp.haskell.org/rÖ hi]r× (UpvprØ jÐ ehh]hf]hg]hl]rÙ (hheuhnM9 hohUexpect_referenced_by_idrÚ }rÛ jÐ jÍ shp]ubj )rÜ }rÝ (hTX(.. _Hackage: http://hackage.haskell.org/hYKhUjE h`jÆ hbj£hd}rÞ (j~Xhttp://hackage.haskell.org/rß hi]rà Uhackagerá ahh]hf]hg]hl]râ hauhnM; hohhp]ubj )rã }rä (hTX$.. _Haskell: http://www.haskell.org/hUjE h`jÆ hbj£hd}rå (j~Xhttp://www.haskell.org/hi]ræ Uhaskellrç ahh]hf]hg]hl]rè hEauhnM= hohhp]ubj )ré }rê (hTX,.. _Haddock: http://www.haskell.org/haddock/hYKhUjE h`jÆ hbj£hd}rë (j~j hi]rì Uhaddockrí ahh]hf]hg]hl]rî hauhnM? hohhp]ubj )rï }rð (hTX&.. _Alex: http://www.haskell.org/alex/hYKhUjE h`jÆ hbj£hd}rñ (j~Xhttp://www.haskell.org/alex/rò hi]ró Ualexrô ahh]hf]hg]hl]rõ h$auhnMA hohhp]ubj )rö }r÷ (hTX(.. _Happy: http://www.haskell.org/happy/hYKhUjE h`jÆ hbj£hd}rø (j~Xhttp://www.haskell.org/happy/rù hi]rú Uhappyrû ahh]hf]hg]hl]rü h*auhnMC hohhp]ubj )rý }rþ (hTX*.. _Hoogle: http://www.haskell.org/hoogle/hUjE h`jÆ hbj£hd}rÿ (j~Xhttp://www.haskell.org/hoogle/hi]r Uhoogler ahh]hf]hg]hl]r hauhnME hohhp]ubj )r }r (hTX9.. _HsColour: http://www.cs.york.ac.uk/fp/darcs/hscolour/hUjE h`jÆ hbj£hd}r (j~X+http://www.cs.york.ac.uk/fp/darcs/hscolour/hi]r Uhscolourr ahh]hf]hg]hl]r hauhnMG hohhp]ubj )r }r (hTX-.. _cpphs: http://projects.haskell.org/cpphs/hYKhUjE h`jÆ hbj£hd}r (j~X"http://projects.haskell.org/cpphs/r hi]r Ucpphsr ahh]hf]hg]hl]r h)auhnMI hohhp]ubeubeubh`hahbhchd}r (hf]hg]hh]hi]r jFahl]r hauhnM‡hohhp]r (hr)r }r (hTXPackage descriptionsr hUh\h`hahbhvhd}r (hf]hg]hh]hi]hl]uhnM‡hohhp]r hyXPackage descriptionsr …r }r (hTj h`NhnNhohhUj ubaubh})r }r (hTX0The package description file must have a name ending in "``.cabal``". It must be a Unicode text file encoded using valid UTF-8. There must be exactly one such file in the directory. The first part of the name is usually the package name, and some of the tools that operate on Cabal packages require this.hUh\h`hahbhhd}r (hf]hg]hh]hi]hl]uhnM‰hohhp]r (hyX;The package description file must have a name ending in “r …r! }r" (hTX9The package description file must have a name ending in "h`NhnNhohhUj ubhß)r# }r$ (hTX ``.cabal``hd}r% (hf]hg]hh]hi]hl]uhUj hp]r& hyX.cabalr' …r( }r) (hTUhUj# ubahbhçubhyXïâ€. It must be a Unicode text file encoded using valid UTF-8. There must be exactly one such file in the directory. The first part of the name is usually the package name, and some of the tools that operate on Cabal packages require this.r* …r+ }r, (hTXí". It must be a Unicode text file encoded using valid UTF-8. There must be exactly one such file in the directory. The first part of the name is usually the package name, and some of the tools that operate on Cabal packages require this.h`NhnNhohhUj ubeubh})r- }r. (hTX~In the package description file, lines whose first non-whitespace characters are "``--``" are treated as comments and ignored.hUh\h`hahbhhd}r/ (hf]hg]hh]hi]hl]uhnMhohhp]r0 (hyXTIn the package description file, lines whose first non-whitespace characters are “r1 …r2 }r3 (hTXRIn the package description file, lines whose first non-whitespace characters are "h`NhnNhohhUj- ubhß)r4 }r5 (hTX``--``hd}r6 (hf]hg]hh]hi]hl]uhUj- hp]r7 hyX--r8 …r9 }r: (hTUhUj4 ubahbhçubhyX(†are treated as comments and ignored.r; …r< }r= (hTX&" are treated as comments and ignored.h`NhnNhohhUj- ubeubh})r> }r? (hTXWThis file should contain of a number global property descriptions and several sections.r@ hUh\h`hahbhhd}rA (hf]hg]hh]hi]hl]uhnM’hohhp]rB hyXWThis file should contain of a number global property descriptions and several sections.rC …rD }rE (hTj@ h`NhnNhohhUj> ubaubh‡)rF }rG (hTUhUh\h`hahbhŠhd}rH (hŒX-hi]hh]hf]hg]hl]uhnM•hohhp]rI (hŽ)rJ }rK (hTX_The `package properties`_ describe the package as a whole, such as name, license, author, etc. hUjF h`hahbh‘hd}rL (hf]hg]hh]hi]hl]uhnNhohhp]rM h})rN }rO (hTX^The `package properties`_ describe the package as a whole, such as name, license, author, etc.hUjJ h`hahbhhd}rP (hf]hg]hh]hi]hl]uhnM•hp]rQ (hyXThe rR …rS }rT (hTXThe hUjN ubj?)rU }rV (hTX`package properties`_jBKhUjN hbjChd}rW (UnameXpackage propertieshi]hh]hf]hg]hl]jEUpackage-propertiesrX uhp]rY hyXpackage propertiesrZ …r[ }r\ (hTUhUjU ubaubhyXE describe the package as a whole, such as name, license, author, etc.r] …r^ }r_ (hTXE describe the package as a whole, such as name, license, author, etc.hUjN ubeubaubhŽ)r` }ra (hTX­Optionally, a number of *configuration flags* can be declared. These can be used to enable or disable certain features of a package. (see the section on `configurations`_). hUjF h`hahbh‘hd}rb (hf]hg]hh]hi]hl]uhnNhohhp]rc h})rd }re (hTX¬Optionally, a number of *configuration flags* can be declared. These can be used to enable or disable certain features of a package. (see the section on `configurations`_).hUj` h`hahbhhd}rf (hf]hg]hh]hi]hl]uhnM˜hp]rg (hyXOptionally, a number of rh …ri }rj (hTXOptionally, a number of hUjd ubh¿)rk }rl (hTX*configuration flags*hd}rm (hf]hg]hh]hi]hl]uhUjd hp]rn hyXconfiguration flagsro …rp }rq (hTUhUjk ubahbhÇubhyXl can be declared. These can be used to enable or disable certain features of a package. (see the section on rr …rs }rt (hTXl can be declared. These can be used to enable or disable certain features of a package. (see the section on hUjd ubj?)ru }rv (hTX`configurations`_jBKhUjd hbjChd}rw (UnameXconfigurationsrx hi]hh]hf]hg]hl]jEjœuhp]ry hyXconfigurationsrz …r{ }r| (hTUhUju ubaubhyX).r} …r~ }r (hTX).hUjd ubeubaubhŽ)r€ }r (hTXfThe (optional) library section specifies the `library`_ properties and relevant `build information`_. hUjF h`hahbh‘hd}r‚ (hf]hg]hh]hi]hl]uhnNhohhp]rƒ h})r„ }r… (hTXeThe (optional) library section specifies the `library`_ properties and relevant `build information`_.hUj€ h`hahbhhd}r† (hf]hg]hh]hi]hl]uhnMœhp]r‡ (hyX-The (optional) library section specifies the rˆ …r‰ }rŠ (hTX-The (optional) library section specifies the hUj„ ubj?)r‹ }rŒ (hTX `library`_jBKhUj„ hbjChd}r (UnameXlibraryrŽ hi]hh]hf]hg]hl]jEUlibraryr uhp]r hyXlibraryr‘ …r’ }r“ (hTUhUj‹ ubaubhyX properties and relevant r” …r• }r– (hTX properties and relevant hUj„ ubj?)r— }r˜ (hTX`build information`_jBKhUj„ hbjChd}r™ (UnameXbuild informationhi]hh]hf]hg]hl]jEj(uhp]rš hyXbuild informationr› …rœ }r (hTUhUj— ubaubhyX.…rž }rŸ (hTX.hUj„ ubeubaubhŽ)r  }r¡ (hTX€Following is an arbitrary number of executable sections which describe an executable program and relevant `build information`_. hUjF h`hahbh‘hd}r¢ (hf]hg]hh]hi]hl]uhnNhohhp]r£ h})r¤ }r¥ (hTXFollowing is an arbitrary number of executable sections which describe an executable program and relevant `build information`_.hUj  h`hahbhhd}r¦ (hf]hg]hh]hi]hl]uhnMŸhp]r§ (hyXjFollowing is an arbitrary number of executable sections which describe an executable program and relevant r¨ …r© }rª (hTXjFollowing is an arbitrary number of executable sections which describe an executable program and relevant hUj¤ ubj?)r« }r¬ (hTX`build information`_jBKhUj¤ hbjChd}r­ (UnameXbuild informationhi]hh]hf]hg]hl]jEj(uhp]r® hyXbuild informationr¯ …r° }r± (hTUhUj« ubaubhyX.…r² }r³ (hTX.hUj¤ ubeubaubeubh})r´ }rµ (hTXEach section consists of a number of property descriptions in the form of field/value pairs, with a syntax roughly like mail message headers.r¶ hUh\h`hahbhhd}r· (hf]hg]hh]hi]hl]uhnM¢hohhp]r¸ hyXEach section consists of a number of property descriptions in the form of field/value pairs, with a syntax roughly like mail message headers.r¹ …rº }r» (hTj¶ h`NhnNhohhUj´ ubaubh‡)r¼ }r½ (hTUhUh\h`hahbhŠhd}r¾ (hŒX-hi]hh]hf]hg]hl]uhnM¥hohhp]r¿ (hŽ)rÀ }rÁ (hTXLCase is not significant in field names, but is significant in field values. hUj¼ h`hahbh‘hd}r (hf]hg]hh]hi]hl]uhnNhohhp]rà h})rÄ }rÅ (hTXKCase is not significant in field names, but is significant in field values.rÆ hUjÀ h`hahbhhd}rÇ (hf]hg]hh]hi]hl]uhnM¥hp]rÈ hyXKCase is not significant in field names, but is significant in field values.rÉ …rÊ }rË (hTjÆ hUjÄ ubaubaubhŽ)rÌ }rÍ (hTXLTo continue a field value, indent the next line relative to the field name. hUj¼ h`hahbh‘hd}rÎ (hf]hg]hh]hi]hl]uhnNhohhp]rÏ h})rÐ }rÑ (hTXKTo continue a field value, indent the next line relative to the field name.rÒ hUjÌ h`hahbhhd}rÓ (hf]hg]hh]hi]hl]uhnM¨hp]rÔ hyXKTo continue a field value, indent the next line relative to the field name.rÕ …rÖ }r× (hTjÒ hUjÐ ubaubaubhŽ)rØ }rÙ (hTXeField names may be indented, but all field values in the same section must use the same indentation. hUj¼ h`hahbh‘hd}rÚ (hf]hg]hh]hi]hl]uhnNhohhp]rÛ h})rÜ }rÝ (hTXdField names may be indented, but all field values in the same section must use the same indentation.rÞ hUjØ h`hahbhhd}rß (hf]hg]hh]hi]hl]uhnM«hp]rà hyXdField names may be indented, but all field values in the same section must use the same indentation.rá …râ }rã (hTjÞ hUjÜ ubaubaubhŽ)rä }rå (hTXhTabs are *not* allowed as indentation characters due to a missing standard interpretation of tab width. hUj¼ h`hahbh‘hd}ræ (hf]hg]hh]hi]hl]uhnNhohhp]rç h})rè }ré (hTXgTabs are *not* allowed as indentation characters due to a missing standard interpretation of tab width.hUjä h`hahbhhd}rê (hf]hg]hh]hi]hl]uhnM®hp]rë (hyX Tabs are rì …rí }rî (hTX Tabs are hUjè ubh¿)rï }rð (hTX*not*hd}rñ (hf]hg]hh]hi]hl]uhUjè hp]rò hyXnotró …rô }rõ (hTUhUjï ubahbhÇubhyXY allowed as indentation characters due to a missing standard interpretation of tab width.rö …r÷ }rø (hTXY allowed as indentation characters due to a missing standard interpretation of tab width.hUjè ubeubaubhŽ)rù }rú (hTX>To get a blank line in a field value, use an indented "``.``" hUj¼ h`hahbh‘hd}rû (hf]hg]hh]hi]hl]uhnNhohhp]rü h})rý }rþ (hTX=To get a blank line in a field value, use an indented "``.``"hUjù h`hahbhhd}rÿ (hf]hg]hh]hi]hl]uhnM±hp]r(hyX9To get a blank line in a field value, use an indented “r…r}r(hTX7To get a blank line in a field value, use an indented "hUjý ubhß)r}r(hTX``.``hd}r(hf]hg]hh]hi]hl]uhUjý hp]rhyX.…r}r (hTUhUjubahbhçubhyX r }r (hTX"hUjý ubeubaubeubh})r }r (hTXBThe syntax of the value depends on the field. Field types include:rhUh\h`hahbhhd}r(hf]hg]hh]hi]hl]uhnM³hohhp]rhyXBThe syntax of the value depends on the field. Field types include:r…r}r(hTjh`NhnNhohhUj ubaubj)r}r(hTUhUh\h`hahbjhd}r(hf]hg]hh]hi]hl]uhnNhohhp]r(j)r}r(hTXk*token*, *filename*, *directory* Either a sequence of one or more non-space non-comma characters, or a quoted string in Haskell 98 lexical syntax. The latter can be used for escaping whitespace, for example: ``ghc-options: -Wall "-with-rtsopts=-T -I1"``. Unless otherwise stated, relative filenames and directories are interpreted from the package root directory.hUjh`hahbjhd}r(hf]hg]hh]hi]hl]uhnMºhp]r(j)r}r(hTX *token*, *filename*, *directory*rhUjh`hahbj hd}r(hf]hg]hh]hi]hl]uhnMºhp]r (h¿)r!}r"(hTX*token*hd}r#(hf]hg]hh]hi]hl]uhUjhp]r$hyXtokenr%…r&}r'(hTUhUj!ubahbhÇubhyX, r(…r)}r*(hTX, r+hUjubh¿)r,}r-(hTX *filename*hd}r.(hf]hg]hh]hi]hl]uhUjhp]r/hyXfilenamer0…r1}r2(hTUhUj,ubahbhÇubhyX, r3…r4}r5(hTj+hUjubh¿)r6}r7(hTX *directory*hd}r8(hf]hg]hh]hi]hl]uhUjhp]r9hyX directoryr:…r;}r<(hTUhUj6ubahbhÇubeubj3)r=}r>(hTUhd}r?(hf]hg]hh]hi]hl]uhUjhp]r@h})rA}rB(hTXJEither a sequence of one or more non-space non-comma characters, or a quoted string in Haskell 98 lexical syntax. The latter can be used for escaping whitespace, for example: ``ghc-options: -Wall "-with-rtsopts=-T -I1"``. Unless otherwise stated, relative filenames and directories are interpreted from the package root directory.hUj=h`hahbhhd}rC(hf]hg]hh]hi]hl]uhnM¶hp]rD(hyX¯Either a sequence of one or more non-space non-comma characters, or a quoted string in Haskell 98 lexical syntax. The latter can be used for escaping whitespace, for example: rE…rF}rG(hTX¯Either a sequence of one or more non-space non-comma characters, or a quoted string in Haskell 98 lexical syntax. The latter can be used for escaping whitespace, for example: hUjAubhß)rH}rI(hTX-``ghc-options: -Wall "-with-rtsopts=-T -I1"``hd}rJ(hf]hg]hh]hi]hl]uhUjAhp]rKhyX)ghc-options: -Wall "-with-rtsopts=-T -I1"rL…rM}rN(hTUhUjHubahbhçubhyXn. Unless otherwise stated, relative filenames and directories are interpreted from the package root directory.rO…rP}rQ(hTXn. Unless otherwise stated, relative filenames and directories are interpreted from the package root directory.hUjAubeubahbjMubeubj)rR}rS(hTX@*freeform*, *URL*, *address* An arbitrary, uninterpreted string.hUjh`hahbjhd}rT(hf]hg]hh]hi]hl]uhnM¼hohhp]rU(j)rV}rW(hTX*freeform*, *URL*, *address*rXhUjRh`hahbj hd}rY(hf]hg]hh]hi]hl]uhnM¼hp]rZ(h¿)r[}r\(hTX *freeform*hd}r](hf]hg]hh]hi]hl]uhUjVhp]r^hyXfreeformr_…r`}ra(hTUhUj[ubahbhÇubhyX, rb…rc}rd(hTX, rehUjVubh¿)rf}rg(hTX*URL*hd}rh(hf]hg]hh]hi]hl]uhUjVhp]rihyXURLrj…rk}rl(hTUhUjfubahbhÇubhyX, rm…rn}ro(hTjehUjVubh¿)rp}rq(hTX *address*hd}rr(hf]hg]hh]hi]hl]uhUjVhp]rshyXaddressrt…ru}rv(hTUhUjpubahbhÇubeubj3)rw}rx(hTUhd}ry(hf]hg]hh]hi]hl]uhUjRhp]rzh})r{}r|(hTX#An arbitrary, uninterpreted string.r}hUjwh`hahbhhd}r~(hf]hg]hh]hi]hl]uhnM½hp]rhyX#An arbitrary, uninterpreted string.r€…r}r‚(hTj}hUj{ubaubahbjMubeubj)rƒ}r„(hTXL*identifier* A letter followed by zero or more alphanumerics or underscores.hUjh`hahbjhd}r…(hf]hg]hh]hi]hl]uhnM¾hohhp]r†(j)r‡}rˆ(hTX *identifier*r‰hUjƒh`hahbj hd}rŠ(hf]hg]hh]hi]hl]uhnM¾hp]r‹h¿)rŒ}r(hTj‰hd}rŽ(hf]hg]hh]hi]hl]uhUj‡hp]rhyX identifierr…r‘}r’(hTUhUjŒubahbhÇubaubj3)r“}r”(hTUhd}r•(hf]hg]hh]hi]hl]uhUjƒhp]r–h})r—}r˜(hTX?A letter followed by zero or more alphanumerics or underscores.r™hUj“h`hahbhhd}rš(hf]hg]hh]hi]hl]uhnM¿hp]r›hyX?A letter followed by zero or more alphanumerics or underscores.rœ…r}rž(hTj™hUj—ubaubahbjMubeubj)rŸ}r (hTX¢*compiler* A compiler flavor (one of: ``GHC``, ``JHC``, ``UHC`` or ``LHC``) followed by a version range. For example, ``GHC ==6.10.3``, or ``LHC >=0.6 && <0.8``. hUjh`hahbjhd}r¡(hf]hg]hh]hi]hl]uhnMÃhohhp]r¢(j)r£}r¤(hTX *compiler*r¥hUjŸh`hahbj hd}r¦(hf]hg]hh]hi]hl]uhnMÃhp]r§h¿)r¨}r©(hTj¥hd}rª(hf]hg]hh]hi]hl]uhUj£hp]r«hyXcompilerr¬…r­}r®(hTUhUj¨ubahbhÇubaubj3)r¯}r°(hTUhd}r±(hf]hg]hh]hi]hl]uhUjŸhp]r²h})r³}r´(hTX–A compiler flavor (one of: ``GHC``, ``JHC``, ``UHC`` or ``LHC``) followed by a version range. For example, ``GHC ==6.10.3``, or ``LHC >=0.6 && <0.8``.hUj¯h`hahbhhd}rµ(hf]hg]hh]hi]hl]uhnMÁhp]r¶(hyXA compiler flavor (one of: r·…r¸}r¹(hTXA compiler flavor (one of: hUj³ubhß)rº}r»(hTX``GHC``hd}r¼(hf]hg]hh]hi]hl]uhUj³hp]r½hyXGHCr¾…r¿}rÀ(hTUhUjºubahbhçubhyX, rÁ…rÂ}rÃ(hTX, rÄhUj³ubhß)rÅ}rÆ(hTX``JHC``hd}rÇ(hf]hg]hh]hi]hl]uhUj³hp]rÈhyXJHCrÉ…rÊ}rË(hTUhUjÅubahbhçubhyX, rÌ…rÍ}rÎ(hTjÄhUj³ubhß)rÏ}rÐ(hTX``UHC``hd}rÑ(hf]hg]hh]hi]hl]uhUj³hp]rÒhyXUHCrÓ…rÔ}rÕ(hTUhUjÏubahbhçubhyX or rÖ…r×}rØ(hTX or hUj³ubhß)rÙ}rÚ(hTX``LHC``hd}rÛ(hf]hg]hh]hi]hl]uhUj³hp]rÜhyXLHCrÝ…rÞ}rß(hTUhUjÙubahbhçubhyX,) followed by a version range. For example, rà…rá}râ(hTX,) followed by a version range. For example, hUj³ubhß)rã}rä(hTX``GHC ==6.10.3``hd}rå(hf]hg]hh]hi]hl]uhUj³hp]ræhyX GHC ==6.10.3rç…rè}ré(hTUhUjãubahbhçubhyX, or rê…rë}rì(hTX, or hUj³ubhß)rí}rî(hTX``LHC >=0.6 && <0.8``hd}rï(hf]hg]hh]hi]hl]uhUj³hp]rðhyXLHC >=0.6 && <0.8rñ…rò}ró(hTUhUjíubahbhçubhyX.…rô}rõ(hTX.hUj³ubeubahbjMubeubeubhV)rö}r÷(hTUhUh\h`hahbhchd}rø(hf]hg]hh]hi]rùUmodules-and-preprocessorsrúahl]rûh9auhnMÆhohhp]rü(hr)rý}rþ(hTXModules and preprocessorsrÿhUjöh`hahbhvhd}r(hf]hg]hh]hi]hl]uhnMÆhohhp]rhyXModules and preprocessorsr…r}r(hTjÿh`NhnNhohhUjýubaubh})r}r(hTX<Haskell module names listed in the :pkg-field:`library:exposed-modules` and :pkg-field:`library:other-modules` fields may correspond to Haskell source files, i.e. with names ending in "``.hs``" or "``.lhs``", or to inputs for various Haskell preprocessors. The simple build infrastructure understands the extensions:hUjöh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMÈhohhp]r(hyX#Haskell module names listed in the r …r }r (hTX#Haskell module names listed in the h`NhnNhohhUjubjk)r }r (hTX$:pkg-field:`library:exposed-modules`rhUjh`hahbjohd}r(UreftypeX pkg-fieldjqˆjrXexposed-modulesU refdomainXcabalrhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹XlibraryuhnMÈhp]rhß)r}r(hTjhd}r(hf]hg]r(j|jXcabal-pkg-fieldrehh]hi]hl]uhUj hp]rhyXlibrary:exposed-modulesr…r}r(hTUhUjubahbhçubaubhyX and r…r}r(hTX and h`NhnNhohhUjubjk)r}r(hTX":pkg-field:`library:other-modules`r hUjh`hahbjohd}r!(UreftypeX pkg-fieldjqˆjrX other-modulesU refdomainXcabalr"hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹XlibraryuhnMÈhp]r#hß)r$}r%(hTj hd}r&(hf]hg]r'(j|j"Xcabal-pkg-fieldr(ehh]hi]hl]uhUjhp]r)hyXlibrary:other-modulesr*…r+}r,(hTUhUj$ubahbhçubaubhyXM fields may correspond to Haskell source files, i.e. with names ending in “r-…r.}r/(hTXK fields may correspond to Haskell source files, i.e. with names ending in "h`NhnNhohhUjubhß)r0}r1(hTX``.hs``hd}r2(hf]hg]hh]hi]hl]uhUjhp]r3hyX.hsr4…r5}r6(hTUhUj0ubahbhçubhyX †or “r7…r8}r9(hTX" or "h`NhnNhohhUjubhß)r:}r;(hTX``.lhs``hd}r<(hf]hg]hh]hi]hl]uhUjhp]r=hyX.lhsr>…r?}r@(hTUhUj:ubahbhçubhyXpâ€, or to inputs for various Haskell preprocessors. The simple build infrastructure understands the extensions:rA…rB}rC(hTXn", or to inputs for various Haskell preprocessors. The simple build infrastructure understands the extensions:h`NhnNhohhUjubeubh‡)rD}rE(hTUhUjöh`hahbhŠhd}rF(hŒX-hi]hh]hf]hg]hl]uhnMÎhohhp]rG(hŽ)rH}rI(hTX"``.gc`` (:hackage-pkg:`greencard`)rJhUjDh`hahbh‘hd}rK(hf]hg]hh]hi]hl]uhnNhohhp]rLh})rM}rN(hTjJhUjHh`hahbhhd}rO(hf]hg]hh]hi]hl]uhnMÎhp]rP(hß)rQ}rR(hTX``.gc``hd}rS(hf]hg]hh]hi]hl]uhUjMhp]rThyX.gcrU…rV}rW(hTUhUjQubahbhçubhyX (rX…rY}rZ(hTX (hUjMubj?)r[}r\(hTX greencardhd}r](UrefuriX,http://hackage.haskell.org/package/greencardhi]hh]hf]hg]hl]Uinternal‰uhUjMhp]r^hyX greencardr_…r`}ra(hTUhUj[ubahbjCubhyX)…rb}rc(hTX)hUjMubeubaubhŽ)rd}re(hTX``.chs`` (:hackage-pkg:`c2hs`)rfhUjDh`hahbh‘hd}rg(hf]hg]hh]hi]hl]uhnNhohhp]rhh})ri}rj(hTjfhUjdh`hahbhhd}rk(hf]hg]hh]hi]hl]uhnMÏhp]rl(hß)rm}rn(hTX``.chs``hd}ro(hf]hg]hh]hi]hl]uhUjihp]rphyX.chsrq…rr}rs(hTUhUjmubahbhçubhyX (rt…ru}rv(hTX (hUjiubj?)rw}rx(hTXc2hshd}ry(UrefuriX'http://hackage.haskell.org/package/c2hshi]hh]hf]hg]hl]Uinternal‰uhUjihp]rzhyXc2hsr{…r|}r}(hTUhUjwubahbjCubhyX)…r~}r(hTX)hUjiubeubaubhŽ)r€}r(hTX ``.hsc`` (:hackage-pkg:`hsc2hs`)r‚hUjDh`hahbh‘hd}rƒ(hf]hg]hh]hi]hl]uhnNhohhp]r„h})r…}r†(hTj‚hUj€h`hahbhhd}r‡(hf]hg]hh]hi]hl]uhnMÐhp]rˆ(hß)r‰}rŠ(hTX``.hsc``hd}r‹(hf]hg]hh]hi]hl]uhUj…hp]rŒhyX.hscr…rŽ}r(hTUhUj‰ubahbhçubhyX (r…r‘}r’(hTX (hUj…ubj?)r“}r”(hTXhsc2hshd}r•(UrefuriX)http://hackage.haskell.org/package/hsc2hshi]hh]hf]hg]hl]Uinternal‰uhUj…hp]r–hyXhsc2hsr—…r˜}r™(hTUhUj“ubahbjCubhyX)…rš}r›(hTX)hUj…ubeubaubhŽ)rœ}r(hTX``.y`` and ``.ly`` (happy_)ržhUjDh`hahbh‘hd}rŸ(hf]hg]hh]hi]hl]uhnNhohhp]r h})r¡}r¢(hTjžhUjœh`hahbhhd}r£(hf]hg]hh]hi]hl]uhnMÑhp]r¤(hß)r¥}r¦(hTX``.y``hd}r§(hf]hg]hh]hi]hl]uhUj¡hp]r¨hyX.yr©…rª}r«(hTUhUj¥ubahbhçubhyX and r¬…r­}r®(hTX and hUj¡ubhß)r¯}r°(hTX``.ly``hd}r±(hf]hg]hh]hi]hl]uhUj¡hp]r²hyX.lyr³…r´}rµ(hTUhUj¯ubahbhçubhyX (r¶…r·}r¸(hTX (hUj¡ubj?)r¹}rº(hTXhappy_jBKhUj¡hbjChd}r»(UnameXhappyr¼j~jù hi]hh]hf]hg]hl]uhp]r½hyXhappyr¾…r¿}rÀ(hTUhUj¹ubaubhyX)…rÁ}rÂ(hTX)hUj¡ubeubaubhŽ)rÃ}rÄ(hTX``.x`` (alex_)rÅhUjDh`hahbh‘hd}rÆ(hf]hg]hh]hi]hl]uhnNhohhp]rÇh})rÈ}rÉ(hTjÅhUjÃh`hahbhhd}rÊ(hf]hg]hh]hi]hl]uhnMÒhp]rË(hß)rÌ}rÍ(hTX``.x``hd}rÎ(hf]hg]hh]hi]hl]uhUjÈhp]rÏhyX.xrÐ…rÑ}rÒ(hTUhUjÌubahbhçubhyX (rÓ…rÔ}rÕ(hTX (hUjÈubj?)rÖ}r×(hTXalex_jBKhUjÈhbjChd}rØ(UnameXalexrÙj~jò hi]hh]hf]hg]hl]uhp]rÚhyXalexrÛ…rÜ}rÝ(hTUhUjÖubaubhyX)…rÞ}rß(hTX)hUjÈubeubaubhŽ)rà}rá(hTX``.cpphs`` (cpphs_) hUjDh`hahbh‘hd}râ(hf]hg]hh]hi]hl]uhnNhohhp]rãh})rä}rå(hTX``.cpphs`` (cpphs_)hUjàh`hahbhhd}ræ(hf]hg]hh]hi]hl]uhnMÓhp]rç(hß)rè}ré(hTX ``.cpphs``hd}rê(hf]hg]hh]hi]hl]uhUjähp]rëhyX.cpphsrì…rí}rî(hTUhUjèubahbhçubhyX (rï…rð}rñ(hTX (hUjäubj?)rò}ró(hTXcpphs_jBKhUjähbjChd}rô(UnameXcpphsrõj~j hi]hh]hf]hg]hl]uhp]röhyXcpphsr÷…rø}rù(hTUhUjòubaubhyX)…rú}rû(hTX)hUjäubeubaubeubh})rü}rý(hTX_When building, Cabal will automatically run the appropriate preprocessor and compile the Haskell module it produces. For the ``c2hs`` and ``hsc2hs`` preprocessors, Cabal will also automatically add, compile and link any C sources generated by the preprocessor (produced by ``hsc2hs``'s ``#def`` feature or ``c2hs``'s auto-generated wrapper functions).hUjöh`hahbhhd}rþ(hf]hg]hh]hi]hl]uhnMÕhohhp]rÿ(hyX}When building, Cabal will automatically run the appropriate preprocessor and compile the Haskell module it produces. For the r…r}r(hTX}When building, Cabal will automatically run the appropriate preprocessor and compile the Haskell module it produces. For the h`NhnNhohhUjüubhß)r}r(hTX``c2hs``hd}r(hf]hg]hh]hi]hl]uhUjühp]rhyXc2hsr…r}r (hTUhUjubahbhçubhyX and r …r }r (hTX and h`NhnNhohhUjüubhß)r }r(hTX ``hsc2hs``hd}r(hf]hg]hh]hi]hl]uhUjühp]rhyXhsc2hsr…r}r(hTUhUj ubahbhçubhyX} preprocessors, Cabal will also automatically add, compile and link any C sources generated by the preprocessor (produced by r…r}r(hTX} preprocessors, Cabal will also automatically add, compile and link any C sources generated by the preprocessor (produced by h`NhnNhohhUjüubhß)r}r(hTX ``hsc2hs``hd}r(hf]hg]hh]hi]hl]uhUjühp]rhyXhsc2hsr…r}r(hTUhUjubahbhçubhyX’s r…r}r (hTX's h`NhnNhohhUjüubhß)r!}r"(hTX``#def``hd}r#(hf]hg]hh]hi]hl]uhUjühp]r$hyX#defr%…r&}r'(hTUhUj!ubahbhçubhyX feature or r(…r)}r*(hTX feature or h`NhnNhohhUjüubhß)r+}r,(hTX``c2hs``hd}r-(hf]hg]hh]hi]hl]uhUjühp]r.hyXc2hsr/…r0}r1(hTUhUj+ubahbhçubhyX'’s auto-generated wrapper functions).r2…r3}r4(hTX%'s auto-generated wrapper functions).h`NhnNhohhUjüubeubh})r5}r6(hTXœSome fields take lists of values, which are optionally separated by commas, except for the :pkg-field:`build-depends` field, where the commas are mandatory.hUjöh`hahbhhd}r7(hf]hg]hh]hi]hl]uhnMÜhohhp]r8(hyX[Some fields take lists of values, which are optionally separated by commas, except for the r9…r:}r;(hTX[Some fields take lists of values, which are optionally separated by commas, except for the h`NhnNhohhUj5ubjk)r<}r=(hTX:pkg-field:`build-depends`r>hUj5h`hahbjohd}r?(UreftypeX pkg-fieldjqˆjrX build-dependsU refdomainXcabalr@hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMÜhp]rAhß)rB}rC(hTj>hd}rD(hf]hg]rE(j|j@Xcabal-pkg-fieldrFehh]hi]hl]uhUj<hp]rGhyX build-dependsrH…rI}rJ(hTUhUjBubahbhçubaubhyX' field, where the commas are mandatory.rK…rL}rM(hTX' field, where the commas are mandatory.h`NhnNhohhUj5ubeubh})rN}rO(hTXvSome fields are marked as required. All others are optional, and unless otherwise specified have empty default values.rPhUjöh`hahbhhd}rQ(hf]hg]hh]hi]hl]uhnMàhohhp]rRhyXvSome fields are marked as required. All others are optional, and unless otherwise specified have empty default values.rS…rT}rU(hTjPh`NhnNhohhUjNubaubeubhV)rV}rW(hTUhYKhUh\h`hahbhchd}rX(hf]hg]hh]hi]rYjX ahl]rZh.auhnMähohhp]r[(hr)r\}r](hTXPackage propertiesr^hUjVh`hahbhvhd}r_(hf]hg]hh]hi]hl]uhnMähohhp]r`hyXPackage propertiesra…rb}rc(hTj^h`NhnNhohhUj\ubaubh})rd}re(hTXeThese fields may occur in the first top-level properties section and describe the package as a whole:rfhUjVh`hahbhhd}rg(hf]hg]hh]hi]hl]uhnMæhohhp]rhhyXeThese fields may occur in the first top-level properties section and describe the package as a whole:ri…rj}rk(hTjfh`NhnNhohhUjdubaubj¹)rl}rm(hTUhUjVh`hahbj¼hd}rn(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)ro}rp(hTUhUjVh`hahbjÁhd}rq(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrrjÇjruhnNhohhp]rs(jÉ)rt}ru(hTXname: package-name (required)hUjoh`hahbjÍhd}rv(hi]rwXpkg-field-namerxahh]hf]hg]hl]jщuhnMìhohhp]ry(j¹)rz}r{(hTUhUjth`hahbj¼hd}r|(hi]hh]hf]hg]hl]Uentries]r}(j×Xname; package.cabal fieldjxUNtr~auhnMìhohhp]ubjÙ)r}r€(hTXnamerhUjth`hahbjÜhd}r‚(jÑjÒhi]hh]hf]hg]hl]uhnMìhohhp]rƒhyXnamer„…r…}r†(hTUh`NhnNhohhUjubaubjâ)r‡}rˆ(hTj[hUjth`hahbjåhd}r‰(jÑjÒhi]hh]hf]hg]hl]uhnMìhohhp]rŠhyX: r‹…rŒ}r(hTUh`NhnNhohhUj‡ubaubja)rŽ}r(hTXpackage-name (required)hUjth`hahbjdhd}r(jÑjÒhi]hh]hf]hg]hl]uhnMìhohhp]r‘hyXpackage-name (required)r’…r“}r”(hTUh`NhnNhohhUjŽubaubeubjê)r•}r–(hTUhUjoh`hahbjíhd}r—(hf]hg]hh]hi]hl]uhnMìhohhp]r˜h})r™}rš(hTX;The unique name of the package, without the version number.r›hUj•h`hahbhhd}rœ(hf]hg]hh]hi]hl]uhnMëhohhp]rhyX;The unique name of the package, without the version number.rž…rŸ}r (hTj›h`NhnNhohhUj™ubaubaubeubj¹)r¡}r¢(hTUhUjVh`hahbj¼hd}r£(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r¤}r¥(hTUhUjVh`hahbjÁhd}r¦(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr§jÇj§uhnNhohhp]r¨(jÉ)r©}rª(hTXversion: numbers (required)hUj¤h`hahbjÍhd}r«(hi]r¬Xpkg-field-versionr­ahh]hf]hg]hl]jщuhnMñhohhp]r®(j¹)r¯}r°(hTUhUj©h`hahbj¼hd}r±(hi]hh]hf]hg]hl]Uentries]r²(j×Xversion; package.cabal fieldj­UNtr³auhnMñhohhp]ubjÙ)r´}rµ(hTXversionr¶hUj©h`hahbjÜhd}r·(jÑjÒhi]hh]hf]hg]hl]uhnMñhohhp]r¸hyXversionr¹…rº}r»(hTUh`NhnNhohhUj´ubaubjâ)r¼}r½(hTj[hUj©h`hahbjåhd}r¾(jÑjÒhi]hh]hf]hg]hl]uhnMñhohhp]r¿hyX: rÀ…rÁ}rÂ(hTUh`NhnNhohhUj¼ubaubja)rÃ}rÄ(hTXnumbers (required)hUj©h`hahbjdhd}rÅ(jÑjÒhi]hh]hf]hg]hl]uhnMñhohhp]rÆhyXnumbers (required)rÇ…rÈ}rÉ(hTUh`NhnNhohhUjÃubaubeubjê)rÊ}rË(hTUhUj¤h`hahbjíhd}rÌ(hf]hg]hh]hi]hl]uhnMñhohhp]rÍh})rÎ}rÏ(hTXbThe package version number, usually consisting of a sequence of natural numbers separated by dots.rÐhUjÊh`hahbhhd}rÑ(hf]hg]hh]hi]hl]uhnMïhohhp]rÒhyXbThe package version number, usually consisting of a sequence of natural numbers separated by dots.rÓ…rÔ}rÕ(hTjÐh`NhnNhohhUjÎubaubaubeubj¹)rÖ}r×(hTUhUjVh`hahbj¼hd}rØ(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÙ}rÚ(hTUhUjVh`hahbjÁhd}rÛ(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrÜjÇjÜuhnNhohhp]rÝ(jÉ)rÞ}rß(hTXcabal-version: >= x.yhUjÙh`hahbjÍhd}rà(hi]ráXpkg-field-cabal-versionrâahh]hf]hg]hl]jщuhnMhohhp]rã(j¹)rä}rå(hTUhUjÞh`hahbj¼hd}ræ(hi]hh]hf]hg]hl]Uentries]rç(j×X"cabal-version; package.cabal fieldjâUNtrèauhnMhohhp]ubjÙ)ré}rê(hTX cabal-versionrëhUjÞh`hahbjÜhd}rì(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]ríhyX cabal-versionrî…rï}rð(hTUh`NhnNhohhUjéubaubjâ)rñ}rò(hTj[hUjÞh`hahbjåhd}ró(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]rôhyX: rõ…rö}r÷(hTUh`NhnNhohhUjñubaubja)rø}rù(hTX>= x.yhUjÞh`hahbjdhd}rú(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]rûhyX>= x.yrü…rý}rþ(hTUh`NhnNhohhUjøubaubeubjê)rÿ}r(hTUhUjÙh`hahbjíhd}r(hf]hg]hh]hi]hl]uhnMhohhp]r(h})r}r(hTXsThe version of the Cabal specification that this package description uses. The Cabal specification does slowly evolve, introducing new features and occasionally changing the meaning of existing features. By specifying which version of the spec you are using it enables programs which process the package description to know what syntax to expect and what each part means.rhUjÿh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMôhohhp]rhyXsThe version of the Cabal specification that this package description uses. The Cabal specification does slowly evolve, introducing new features and occasionally changing the meaning of existing features. By specifying which version of the spec you are using it enables programs which process the package description to know what syntax to expect and what each part means.r…r }r (hTjh`NhnNhohhUjubaubh})r }r (hTXFor historical reasons this is always expressed using *>=* version range syntax. No other kinds of version range make sense, in particular upper bounds do not make sense. In future this field will specify just a version number, rather than a version range.hUjÿh`hahbhhd}r (hf]hg]hh]hi]hl]uhnMûhohhp]r(hyX6For historical reasons this is always expressed using r…r}r(hTX6For historical reasons this is always expressed using h`NhnNhohhUj ubh¿)r}r(hTX*>=*hd}r(hf]hg]hh]hi]hl]uhUj hp]rhyX>=r…r}r(hTUhUjubahbhÇubhyXÆ version range syntax. No other kinds of version range make sense, in particular upper bounds do not make sense. In future this field will specify just a version number, rather than a version range.r…r}r(hTXÆ version range syntax. No other kinds of version range make sense, in particular upper bounds do not make sense. In future this field will specify just a version number, rather than a version range.h`NhnNhohhUj ubeubh})r}r(hTXThe version number you specify will affect both compatibility and behaviour. Most tools (including the Cabal library and cabal program) understand a range of versions of the Cabal specification. Older tools will of course only work with older versions of the Cabal specification. Most of the time, tools that are too old will recognise this fact and produce a suitable error message.rhUjÿh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMhohhp]r hyXThe version number you specify will affect both compatibility and behaviour. Most tools (including the Cabal library and cabal program) understand a range of versions of the Cabal specification. Older tools will of course only work with older versions of the Cabal specification. Most of the time, tools that are too old will recognise this fact and produce a suitable error message.r!…r"}r#(hTjh`NhnNhohhUjubaubh})r$}r%(hTXDAs for behaviour, new versions of the Cabal spec can change the meaning of existing syntax. This means if you want to take advantage of the new meaning or behaviour then you must specify the newer Cabal version. Tools are expected to use the meaning and behaviour appropriate to the version given in the package description.r&hUjÿh`hahbhhd}r'(hf]hg]hh]hi]hl]uhnMhohhp]r(hyXDAs for behaviour, new versions of the Cabal spec can change the meaning of existing syntax. This means if you want to take advantage of the new meaning or behaviour then you must specify the newer Cabal version. Tools are expected to use the meaning and behaviour appropriate to the version given in the package description.r)…r*}r+(hTj&h`NhnNhohhUj$ubaubh})r,}r-(hTX®In particular, the syntax of package descriptions changed significantly with Cabal version 1.2 and the :pkg-field:`cabal-version` field is now required. Files written in the old syntax are still recognized, so if you require compatibility with very old Cabal versions then you may write your package description file using the old syntax. Please consult the user's guide of an older Cabal version for a description of that syntax.hUjÿh`hahbhhd}r.(hf]hg]hh]hi]hl]uhnM hohhp]r/(hyXgIn particular, the syntax of package descriptions changed significantly with Cabal version 1.2 and the r0…r1}r2(hTXgIn particular, the syntax of package descriptions changed significantly with Cabal version 1.2 and the h`NhnNhohhUj,ubjk)r3}r4(hTX:pkg-field:`cabal-version`r5hUj,h`hahbjohd}r6(UreftypeX pkg-fieldjqˆjrX cabal-versionU refdomainXcabalr7hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnM hp]r8hß)r9}r:(hTj5hd}r;(hf]hg]r<(j|j7Xcabal-pkg-fieldr=ehh]hi]hl]uhUj3hp]r>hyX cabal-versionr?…r@}rA(hTUhUj9ubahbhçubaubhyX/ field is now required. Files written in the old syntax are still recognized, so if you require compatibility with very old Cabal versions then you may write your package description file using the old syntax. Please consult the user’s guide of an older Cabal version for a description of that syntax.rB…rC}rD(hTX- field is now required. Files written in the old syntax are still recognized, so if you require compatibility with very old Cabal versions then you may write your package description file using the old syntax. Please consult the user's guide of an older Cabal version for a description of that syntax.h`NhnNhohhUj,ubeubeubeubj¹)rE}rF(hTUhUjVh`hahbj¼hd}rG(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rH}rI(hTUhUjVh`hahbjÁhd}rJ(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrKjÇjKuhnNhohhp]rL(jÉ)rM}rN(hTXbuild-type: identifierhUjHh`hahbjÍhd}rO(hi]rPXpkg-field-build-typerQahh]hf]hg]hl]jщuhnMAhohhp]rR(j¹)rS}rT(hTUhUjMh`hahbj¼hd}rU(hi]hh]hf]hg]hl]Uentries]rV(j×Xbuild-type; package.cabal fieldjQUNtrWauhnMAhohhp]ubjÙ)rX}rY(hTX build-typerZhUjMh`hahbjÜhd}r[(jÑjÒhi]hh]hf]hg]hl]uhnMAhohhp]r\hyX build-typer]…r^}r_(hTUh`NhnNhohhUjXubaubjâ)r`}ra(hTj[hUjMh`hahbjåhd}rb(jÑjÒhi]hh]hf]hg]hl]uhnMAhohhp]rchyX: rd…re}rf(hTUh`NhnNhohhUj`ubaubja)rg}rh(hTX identifierhUjMh`hahbjdhd}ri(jÑjÒhi]hh]hf]hg]hl]uhnMAhohhp]rjhyX identifierrk…rl}rm(hTUh`NhnNhohhUjgubaubeubjê)rn}ro(hTUhUjHh`hahbjíhd}rp(hf]hg]hh]hi]hl]uhnMAhohhp]rq(jð)rr}rs(hTUhUjnh`hahbjóhd}rt(hf]hg]hh]hi]hl]uhnNhohhp]rujö)rv}rw(hTUhd}rx(hf]hg]hh]hi]hl]uhUjrhp]ry(jü)rz}r{(hTX Default valuehUjvh`hahbjhd}r|(hf]hg]hh]hi]hl]uhnKhp]r}hyX Default valuer~…r}r€(hTUhUjzubaubj)r}r‚(hTUhd}rƒ(hf]hg]hh]hi]hl]uhUjvhp]r„h})r…}r†(hTXCustomhd}r‡(hf]hg]hh]hi]hl]uhUjhp]rˆhß)r‰}rŠ(hTX ``Custom``r‹hUj…h`hahbhçhd}rŒ(hf]hg]hh]hi]hl]uhnNhohhp]rhyXCustomrŽ…r}r(hTUh`NhnNhohhUj‰ubaubahbhubahbjubehbjùubaubh})r‘}r’(hTXÖThe type of build used by this package. Build types are the constructors of the `BuildType <../release/cabal-latest/doc/API/Cabal/Distribution-PackageDescription.html#t:BuildType>`__ type, defaulting to ``Custom``.hUjnh`hahbhhd}r“(hf]hg]hh]hi]hl]uhnMhohhp]r”(hyXPThe type of build used by this package. Build types are the constructors of the r•…r–}r—(hTXPThe type of build used by this package. Build types are the constructors of the h`NhnNhohhUj‘ubj?)r˜}r™(hTXf`BuildType <../release/cabal-latest/doc/API/Cabal/Distribution-PackageDescription.html#t:BuildType>`__hd}rš(UnameX BuildTypej~XV../release/cabal-latest/doc/API/Cabal/Distribution-PackageDescription.html#t:BuildTypehi]hh]hf]hg]hl]uhUj‘hp]r›hyX BuildTyperœ…r}rž(hTUhUj˜ubahbjCubhyX type, defaulting to rŸ…r }r¡(hTX type, defaulting to h`NhnNhohhUj‘ubhß)r¢}r£(hTX ``Custom``hd}r¤(hf]hg]hh]hi]hl]uhUj‘hp]r¥hyXCustomr¦…r§}r¨(hTUhUj¢ubahbhçubhyX.…r©}rª(hTX.h`NhnNhohhUj‘ubeubh})r«}r¬(hTX\If the build type is anything other than ``Custom``, then the ``Setup.hs`` file *must* be exactly the standardized content discussed below. This is because in these cases, ``cabal`` will ignore the ``Setup.hs`` file completely, whereas other methods of package management, such as ``runhaskell Setup.hs [CMD]``, still rely on the ``Setup.hs`` file.hUjnh`hahbhhd}r­(hf]hg]hh]hi]hl]uhnMhohhp]r®(hyX)If the build type is anything other than r¯…r°}r±(hTX)If the build type is anything other than h`NhnNhohhUj«ubhß)r²}r³(hTX ``Custom``hd}r´(hf]hg]hh]hi]hl]uhUj«hp]rµhyXCustomr¶…r·}r¸(hTUhUj²ubahbhçubhyX , then the r¹…rº}r»(hTX , then the h`NhnNhohhUj«ubhß)r¼}r½(hTX ``Setup.hs``hd}r¾(hf]hg]hh]hi]hl]uhUj«hp]r¿hyXSetup.hsrÀ…rÁ}rÂ(hTUhUj¼ubahbhçubhyX file rÃ…rÄ}rÅ(hTX file h`NhnNhohhUj«ubh¿)rÆ}rÇ(hTX*must*hd}rÈ(hf]hg]hh]hi]hl]uhUj«hp]rÉhyXmustrÊ…rË}rÌ(hTUhUjÆubahbhÇubhyXV be exactly the standardized content discussed below. This is because in these cases, rÍ…rÎ}rÏ(hTXV be exactly the standardized content discussed below. This is because in these cases, h`NhnNhohhUj«ubhß)rÐ}rÑ(hTX ``cabal``hd}rÒ(hf]hg]hh]hi]hl]uhUj«hp]rÓhyXcabalrÔ…rÕ}rÖ(hTUhUjÐubahbhçubhyX will ignore the r×…rØ}rÙ(hTX will ignore the h`NhnNhohhUj«ubhß)rÚ}rÛ(hTX ``Setup.hs``hd}rÜ(hf]hg]hh]hi]hl]uhUj«hp]rÝhyXSetup.hsrÞ…rß}rà(hTUhUjÚubahbhçubhyXG file completely, whereas other methods of package management, such as rá…râ}rã(hTXG file completely, whereas other methods of package management, such as h`NhnNhohhUj«ubhß)rä}rå(hTX``runhaskell Setup.hs [CMD]``hd}ræ(hf]hg]hh]hi]hl]uhUj«hp]rçhyXrunhaskell Setup.hs [CMD]rè…ré}rê(hTUhUjäubahbhçubhyX, still rely on the rë…rì}rí(hTX, still rely on the h`NhnNhohhUj«ubhß)rî}rï(hTX ``Setup.hs``hd}rð(hf]hg]hh]hi]hl]uhUj«hp]rñhyXSetup.hsrò…ró}rô(hTUhUjîubahbhçubhyX file.rõ…rö}r÷(hTX file.h`NhnNhohhUj«ubeubh})rø}rù(hTX@For build type ``Simple``, the contents of ``Setup.hs`` must be:hUjnh`hahbhhd}rú(hf]hg]hh]hi]hl]uhnM%hohhp]rû(hyXFor build type rü…rý}rþ(hTXFor build type h`NhnNhohhUjøubhß)rÿ}r(hTX ``Simple``hd}r(hf]hg]hh]hi]hl]uhUjøhp]rhyXSimpler…r}r(hTUhUjÿubahbhçubhyX, the contents of r…r}r(hTX, the contents of h`NhnNhohhUjøubhß)r }r (hTX ``Setup.hs``hd}r (hf]hg]hh]hi]hl]uhUjøhp]r hyXSetup.hsr …r}r(hTUhUj ubahbhçubhyX must be:r…r}r(hTX must be:h`NhnNhohhUjøubeubjÌ)r}r(hTX-import Distribution.Simple main = defaultMainhUjnh`hahbjÏhd}r(j‰jXhaskelljÑjÒhi]hh]hf]j}hg]hl]uhnM'hohhp]rhyX-import Distribution.Simple main = defaultMainr…r}r(hTUhUjubaubh})r}r(hTX}For build type ``Configure`` (see the section on `system-dependent parameters`_ below), the contents of ``Setup.hs`` must be:hUjnh`hahbhhd}r(hf]hg]hh]hi]hl]uhnM,hohhp]r(hyXFor build type r…r}r (hTXFor build type h`NhnNhohhUjubhß)r!}r"(hTX ``Configure``hd}r#(hf]hg]hh]hi]hl]uhUjhp]r$hyX Configurer%…r&}r'(hTUhUj!ubahbhçubhyX (see the section on r(…r)}r*(hTX (see the section on h`NhnNhohhUjubj?)r+}r,(hTX`system-dependent parameters`_jBKhUjhbjChd}r-(UnameXsystem-dependent parametershi]hh]hf]hg]hl]jEjuhp]r.hyXsystem-dependent parametersr/…r0}r1(hTUhUj+ubaubhyX below), the contents of r2…r3}r4(hTX below), the contents of h`NhnNhohhUjubhß)r5}r6(hTX ``Setup.hs``hd}r7(hf]hg]hh]hi]hl]uhUjhp]r8hyXSetup.hsr9…r:}r;(hTUhUj5ubahbhçubhyX must be:r<…r=}r>(hTX must be:h`NhnNhohhUjubeubjÌ)r?}r@(hTXHimport Distribution.Simple main = defaultMainWithHooks autoconfUserHookshUjnh`hahbjÏhd}rA(j‰jXhaskelljÑjÒhi]hh]hf]j}hg]hl]uhnM0hohhp]rBhyXHimport Distribution.Simple main = defaultMainWithHooks autoconfUserHooksrC…rD}rE(hTUhUj?ubaubh})rF}rG(hTXrFor build type ``Make`` (see the section on `more complex packages`_ below), the contents of ``Setup.hs`` must be:hUjnh`hahbhhd}rH(hf]hg]hh]hi]hl]uhnM5hohhp]rI(hyXFor build type rJ…rK}rL(hTXFor build type h`NhnNhohhUjFubhß)rM}rN(hTX``Make``hd}rO(hf]hg]hh]hi]hl]uhUjFhp]rPhyXMakerQ…rR}rS(hTUhUjMubahbhçubhyX (see the section on rT…rU}rV(hTX (see the section on h`NhnNhohhUjFubj?)rW}rX(hTX`more complex packages`_jBKhUjFhbjChd}rY(UnameXmore complex packageshi]hh]hf]hg]hl]jEjI uhp]rZhyXmore complex packagesr[…r\}r](hTUhUjWubaubhyX below), the contents of r^…r_}r`(hTX below), the contents of h`NhnNhohhUjFubhß)ra}rb(hTX ``Setup.hs``hd}rc(hf]hg]hh]hi]hl]uhUjFhp]rdhyXSetup.hsre…rf}rg(hTUhUjaubahbhçubhyX must be:rh…ri}rj(hTX must be:h`NhnNhohhUjFubeubjÌ)rk}rl(hTX+import Distribution.Make main = defaultMainhUjnh`hahbjÏhd}rm(j‰jXhaskelljÑjÒhi]hh]hf]j}hg]hl]uhnM8hohhp]rnhyX+import Distribution.Make main = defaultMainro…rp}rq(hTUhUjkubaubh})rr}rs(hTXwFor build type ``Custom``, the file ``Setup.hs`` can be customized, and will be used both by ``cabal`` and other tools.hUjnh`hahbhhd}rt(hf]hg]hh]hi]hl]uhnM=hohhp]ru(hyXFor build type rv…rw}rx(hTXFor build type h`NhnNhohhUjrubhß)ry}rz(hTX ``Custom``hd}r{(hf]hg]hh]hi]hl]uhUjrhp]r|hyXCustomr}…r~}r(hTUhUjyubahbhçubhyX , the file r€…r}r‚(hTX , the file h`NhnNhohhUjrubhß)rƒ}r„(hTX ``Setup.hs``hd}r…(hf]hg]hh]hi]hl]uhUjrhp]r†hyXSetup.hsr‡…rˆ}r‰(hTUhUjƒubahbhçubhyX- can be customized, and will be used both by rŠ…r‹}rŒ(hTX- can be customized, and will be used both by h`NhnNhohhUjrubhß)r}rŽ(hTX ``cabal``hd}r(hf]hg]hh]hi]hl]uhUjrhp]rhyXcabalr‘…r’}r“(hTUhUjubahbhçubhyX and other tools.r”…r•}r–(hTX and other tools.h`NhnNhohhUjrubeubh})r—}r˜(hTX;For most packages, the build type ``Simple`` is sufficient.hUjnh`hahbhhd}r™(hf]hg]hh]hi]hl]uhnM@hohhp]rš(hyX"For most packages, the build type r›…rœ}r(hTX"For most packages, the build type h`NhnNhohhUj—ubhß)rž}rŸ(hTX ``Simple``hd}r (hf]hg]hh]hi]hl]uhUj—hp]r¡hyXSimpler¢…r£}r¤(hTUhUjžubahbhçubhyX is sufficient.r¥…r¦}r§(hTX is sufficient.h`NhnNhohhUj—ubeubeubeubj¹)r¨}r©(hTUhUjVh`hahbj¼hd}rª(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r«}r¬(hTUhUjVh`hahbjÁhd}r­(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr®jÇj®uhnNhohhp]r¯(jÉ)r°}r±(hTXlicense: identifierhUj«h`hahbjÍhd}r²(hi]r³Xpkg-field-licenser´ahh]hf]hg]hl]jщuhnMJhohhp]rµ(j¹)r¶}r·(hTUhUj°h`hahbj¼hd}r¸(hi]hh]hf]hg]hl]Uentries]r¹(j×Xlicense; package.cabal fieldj´UNtrºauhnMJhohhp]ubjÙ)r»}r¼(hTXlicenser½hUj°h`hahbjÜhd}r¾(jÑjÒhi]hh]hf]hg]hl]uhnMJhohhp]r¿hyXlicenserÀ…rÁ}rÂ(hTUh`NhnNhohhUj»ubaubjâ)rÃ}rÄ(hTj[hUj°h`hahbjåhd}rÅ(jÑjÒhi]hh]hf]hg]hl]uhnMJhohhp]rÆhyX: rÇ…rÈ}rÉ(hTUh`NhnNhohhUjÃubaubja)rÊ}rË(hTX identifierhUj°h`hahbjdhd}rÌ(jÑjÒhi]hh]hf]hg]hl]uhnMJhohhp]rÍhyX identifierrÎ…rÏ}rÐ(hTUh`NhnNhohhUjÊubaubeubjê)rÑ}rÒ(hTUhUj«h`hahbjíhd}rÓ(hf]hg]hh]hi]hl]uhnMJhohhp]rÔ(jð)rÕ}rÖ(hTUhUjÑh`hahbjóhd}r×(hf]hg]hh]hi]hl]uhnNhohhp]rØjö)rÙ}rÚ(hTUhd}rÛ(hf]hg]hh]hi]hl]uhUjÕhp]rÜ(jü)rÝ}rÞ(hTX Default valuehUjÙh`hahbjhd}rß(hf]hg]hh]hi]hl]uhnKhp]ràhyX Default valuerá…râ}rã(hTUhUjÝubaubj)rä}rå(hTUhd}ræ(hf]hg]hh]hi]hl]uhUjÙhp]rçh})rè}ré(hTXAllRightsReservedhd}rê(hf]hg]hh]hi]hl]uhUjähp]rëhß)rì}rí(hTX``AllRightsReserved``hUjèh`hahbhçhd}rî(hf]hg]hh]hi]hl]uhnNhohhp]rïhyXAllRightsReservedrð…rñ}rò(hTUh`NhnNhohhUjìubaubahbhubahbjubehbjùubaubh})ró}rô(hTXÁThe type of license under which this package is distributed. License names are the constants of the `License <../release/cabal-latest/doc/API/Cabal/Distribution-License.html#t:License>`__ type.hUjÑh`hahbhhd}rõ(hf]hg]hh]hi]hl]uhnMFhohhp]rö(hyXdThe type of license under which this package is distributed. License names are the constants of the r÷…rø}rù(hTXdThe type of license under which this package is distributed. License names are the constants of the h`NhnNhohhUjóubj?)rú}rû(hTXW`License <../release/cabal-latest/doc/API/Cabal/Distribution-License.html#t:License>`__hd}rü(UnameXLicensej~XI../release/cabal-latest/doc/API/Cabal/Distribution-License.html#t:Licensehi]hh]hf]hg]hl]uhUjóhp]rýhyXLicenserþ…rÿ}r(hTUhUjúubahbjCubhyX type.r…r}r(hTX type.h`NhnNhohhUjóubeubeubeubj¹)r}r(hTUhUjVh`Nhbj¼hd}r(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r}r(hTUhUjVh`NhbjÁhd}r (jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr jÇj uhnNhohhp]r (jÉ)r }r (hTXlicense-file: filenamehUjh`hahbjÍhd}r(hi]rXpkg-field-license-filerahh]hf]hg]hl]jщuhnMKhohhp]r(j¹)r}r(hTUhUj h`hahbj¼hd}r(hi]hh]hf]hg]hl]Uentries]r(j×X!license-file; package.cabal fieldjUNtrauhnMKhohhp]ubjÙ)r}r(hTX license-filerhUj h`hahbjÜhd}r(jÑjÒhi]hh]hf]hg]hl]uhnMKhohhp]rhyX license-filer…r}r(hTUh`NhnNhohhUjubaubjâ)r}r (hTj[hUj h`hahbjåhd}r!(jÑjÒhi]hh]hf]hg]hl]uhnMKhohhp]r"hyX: r#…r$}r%(hTUh`NhnNhohhUjubaubja)r&}r'(hTXfilenamehUj h`hahbjdhd}r((jÑjÒhi]hh]hf]hg]hl]uhnMKhohhp]r)hyXfilenamer*…r+}r,(hTUh`NhnNhohhUj&ubaubeubjê)r-}r.(hTUhUjh`hahbjíhd}r/(hf]hg]hh]hi]hl]uhnMKhohhp]ubeubj¹)r0}r1(hTUhUjVh`hahbj¼hd}r2(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r3}r4(hTUhUjVh`hahbjÁhd}r5(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr6jÇj6uhnNhohhp]r7(jÉ)r8}r9(hTXlicense-files: filename listhUj3h`hahbjÍhd}r:(hi]r;Xpkg-field-license-filesr<ahh]hf]hg]hl]jщuhnMThohhp]r=(j¹)r>}r?(hTUhUj8h`hahbj¼hd}r@(hi]hh]hf]hg]hl]Uentries]rA(j×X"license-files; package.cabal fieldj<UNtrBauhnMThohhp]ubjÙ)rC}rD(hTX license-filesrEhUj8h`hahbjÜhd}rF(jÑjÒhi]hh]hf]hg]hl]uhnMThohhp]rGhyX license-filesrH…rI}rJ(hTUh`NhnNhohhUjCubaubjâ)rK}rL(hTj[hUj8h`hahbjåhd}rM(jÑjÒhi]hh]hf]hg]hl]uhnMThohhp]rNhyX: rO…rP}rQ(hTUh`NhnNhohhUjKubaubja)rR}rS(hTX filename listhUj8h`hahbjdhd}rT(jÑjÒhi]hh]hf]hg]hl]uhnMThohhp]rUhyX filename listrV…rW}rX(hTUh`NhnNhohhUjRubaubeubjê)rY}rZ(hTUhUj3h`hahbjíhd}r[(hf]hg]hh]hi]hl]uhnMThohhp]r\(h})r]}r^(hTXˆThe name of a file(s) containing the precise copyright license for this package. The license file(s) will be installed with the package.r_hUjYh`hahbhhd}r`(hf]hg]hh]hi]hl]uhnMNhohhp]rahyXˆThe name of a file(s) containing the precise copyright license for this package. The license file(s) will be installed with the package.rb…rc}rd(hTj_h`NhnNhohhUj]ubaubh})re}rf(hTX”If you have multiple license files then use the :pkg-field:`license-files` field instead of (or in addition to) the :pkg-field:`license-file` field.hUjYh`hahbhhd}rg(hf]hg]hh]hi]hl]uhnMRhohhp]rh(hyX0If you have multiple license files then use the ri…rj}rk(hTX0If you have multiple license files then use the h`NhnNhohhUjeubjk)rl}rm(hTX:pkg-field:`license-files`rnhUjeh`hahbjohd}ro(UreftypeX pkg-fieldjqˆjrX license-filesU refdomainXcabalrphi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMRhp]rqhß)rr}rs(hTjnhd}rt(hf]hg]ru(j|jpXcabal-pkg-fieldrvehh]hi]hl]uhUjlhp]rwhyX license-filesrx…ry}rz(hTUhUjrubahbhçubaubhyX* field instead of (or in addition to) the r{…r|}r}(hTX* field instead of (or in addition to) the h`NhnNhohhUjeubjk)r~}r(hTX:pkg-field:`license-file`r€hUjeh`hahbjohd}r(UreftypeX pkg-fieldjqˆjrX license-fileU refdomainXcabalr‚hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMRhp]rƒhß)r„}r…(hTj€hd}r†(hf]hg]r‡(j|j‚Xcabal-pkg-fieldrˆehh]hi]hl]uhUj~hp]r‰hyX license-filerŠ…r‹}rŒ(hTUhUj„ubahbhçubaubhyX field.r…rŽ}r(hTX field.h`NhnNhohhUjeubeubeubeubj¹)r}r‘(hTUhUjVh`hahbj¼hd}r’(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r“}r”(hTUhUjVh`hahbjÁhd}r•(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr–jÇj–uhnNhohhp]r—(jÉ)r˜}r™(hTXcopyright: freeformhUj“h`hahbjÍhd}rš(hi]r›Xpkg-field-copyrightrœahh]hf]hg]hl]jщuhnM\hohhp]r(j¹)rž}rŸ(hTUhUj˜h`hahbj¼hd}r (hi]hh]hf]hg]hl]Uentries]r¡(j×Xcopyright; package.cabal fieldjœUNtr¢auhnM\hohhp]ubjÙ)r£}r¤(hTX copyrightr¥hUj˜h`hahbjÜhd}r¦(jÑjÒhi]hh]hf]hg]hl]uhnM\hohhp]r§hyX copyrightr¨…r©}rª(hTUh`NhnNhohhUj£ubaubjâ)r«}r¬(hTj[hUj˜h`hahbjåhd}r­(jÑjÒhi]hh]hf]hg]hl]uhnM\hohhp]r®hyX: r¯…r°}r±(hTUh`NhnNhohhUj«ubaubja)r²}r³(hTXfreeformhUj˜h`hahbjdhd}r´(jÑjÒhi]hh]hf]hg]hl]uhnM\hohhp]rµhyXfreeformr¶…r·}r¸(hTUh`NhnNhohhUj²ubaubeubjê)r¹}rº(hTUhUj“h`hahbjíhd}r»(hf]hg]hh]hi]hl]uhnM\hohhp]r¼(h})r½}r¾(hTX¢The content of a copyright notice, typically the name of the holder of the copyright on the package and the year(s) from which copyright is claimed. For example::hUj¹h`hahbhhd}r¿(hf]hg]hh]hi]hl]uhnMWhohhp]rÀhyX¡The content of a copyright notice, typically the name of the holder of the copyright on the package and the year(s) from which copyright is claimed. For example:rÁ…rÂ}rÃ(hTX¡The content of a copyright notice, typically the name of the holder of the copyright on the package and the year(s) from which copyright is claimed. For example:h`NhnNhohhUj½ubaubjÌ)rÄ}rÅ(hTX#copyright: (c) 2006-2007 Joe BloggshUj¹h`hahbjÏhd}rÆ(jÑjÒhi]hh]hf]hg]hl]uhnM[hohhp]rÇhyX#copyright: (c) 2006-2007 Joe BloggsrÈ…rÉ}rÊ(hTUhUjÄubaubeubeubj¹)rË}rÌ(hTUhUjVh`hahbj¼hd}rÍ(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÎ}rÏ(hTUhUjVh`hahbjÁhd}rÐ(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrÑjÇjÑuhnNhohhp]rÒ(jÉ)rÓ}rÔ(hTXauthor: freeformhUjÎh`hahbjÍhd}rÕ(hi]rÖXpkg-field-authorr×ahh]hf]hg]hl]jщuhnMchohhp]rØ(j¹)rÙ}rÚ(hTUhUjÓh`hahbj¼hd}rÛ(hi]hh]hf]hg]hl]Uentries]rÜ(j×Xauthor; package.cabal fieldj×UNtrÝauhnMchohhp]ubjÙ)rÞ}rß(hTXauthorràhUjÓh`hahbjÜhd}rá(jÑjÒhi]hh]hf]hg]hl]uhnMchohhp]râhyXauthorrã…rä}rå(hTUh`NhnNhohhUjÞubaubjâ)ræ}rç(hTj[hUjÓh`hahbjåhd}rè(jÑjÒhi]hh]hf]hg]hl]uhnMchohhp]réhyX: rê…rë}rì(hTUh`NhnNhohhUjæubaubja)rí}rî(hTXfreeformhUjÓh`hahbjdhd}rï(jÑjÒhi]hh]hf]hg]hl]uhnMchohhp]rðhyXfreeformrñ…rò}ró(hTUh`NhnNhohhUjíubaubeubjê)rô}rõ(hTUhUjÎh`hahbjíhd}rö(hf]hg]hh]hi]hl]uhnMchohhp]r÷(h})rø}rù(hTX#The original author of the package.rúhUjôh`hahbhhd}rû(hf]hg]hh]hi]hl]uhnM_hohhp]rühyX#The original author of the package.rý…rþ}rÿ(hTjúh`NhnNhohhUjøubaubh})r}r(hTXERemember that ``.cabal`` files are Unicode, using the UTF-8 encoding.hUjôh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMahohhp]r(hyXRemember that r…r}r(hTXRemember that h`NhnNhohhUjubhß)r}r(hTX ``.cabal``hd}r (hf]hg]hh]hi]hl]uhUjhp]r hyX.cabalr …r }r (hTUhUjubahbhçubhyX- files are Unicode, using the UTF-8 encoding.r…r}r(hTX- files are Unicode, using the UTF-8 encoding.h`NhnNhohhUjubeubeubeubj¹)r}r(hTUhUjVh`hahbj¼hd}r(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r}r(hTUhUjVh`hahbjÁhd}r(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrjÇjuhnNhohhp]r(jÉ)r}r(hTXmaintainer: addresshUjh`hahbjÍhd}r(hi]rXpkg-field-maintainerrahh]hf]hg]hl]jщuhnMihohhp]r(j¹)r}r (hTUhUjh`hahbj¼hd}r!(hi]hh]hf]hg]hl]Uentries]r"(j×Xmaintainer; package.cabal fieldjUNtr#auhnMihohhp]ubjÙ)r$}r%(hTX maintainerr&hUjh`hahbjÜhd}r'(jÑjÒhi]hh]hf]hg]hl]uhnMihohhp]r(hyX maintainerr)…r*}r+(hTUh`NhnNhohhUj$ubaubjâ)r,}r-(hTj[hUjh`hahbjåhd}r.(jÑjÒhi]hh]hf]hg]hl]uhnMihohhp]r/hyX: r0…r1}r2(hTUh`NhnNhohhUj,ubaubja)r3}r4(hTXaddresshUjh`hahbjdhd}r5(jÑjÒhi]hh]hf]hg]hl]uhnMihohhp]r6hyXaddressr7…r8}r9(hTUh`NhnNhohhUj3ubaubeubjê)r:}r;(hTUhUjh`hahbjíhd}r<(hf]hg]hh]hi]hl]uhnMihohhp]r=h})r>}r?(hTX•The current maintainer or maintainers of the package. This is an e-mail address to which users should send bug reports, feature requests and patches.r@hUj:h`hahbhhd}rA(hf]hg]hh]hi]hl]uhnMfhohhp]rBhyX•The current maintainer or maintainers of the package. This is an e-mail address to which users should send bug reports, feature requests and patches.rC…rD}rE(hTj@h`NhnNhohhUj>ubaubaubeubj¹)rF}rG(hTUhUjVh`hahbj¼hd}rH(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rI}rJ(hTUhUjVh`hahbjÁhd}rK(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrLjÇjLuhnNhohhp]rM(jÉ)rN}rO(hTXstability: freeformhUjIh`hahbjÍhd}rP(hi]rQXpkg-field-stabilityrRahh]hf]hg]hl]jщuhnMnhohhp]rS(j¹)rT}rU(hTUhUjNh`hahbj¼hd}rV(hi]hh]hf]hg]hl]Uentries]rW(j×Xstability; package.cabal fieldjRUNtrXauhnMnhohhp]ubjÙ)rY}rZ(hTX stabilityr[hUjNh`hahbjÜhd}r\(jÑjÒhi]hh]hf]hg]hl]uhnMnhohhp]r]hyX stabilityr^…r_}r`(hTUh`NhnNhohhUjYubaubjâ)ra}rb(hTj[hUjNh`hahbjåhd}rc(jÑjÒhi]hh]hf]hg]hl]uhnMnhohhp]rdhyX: re…rf}rg(hTUh`NhnNhohhUjaubaubja)rh}ri(hTXfreeformhUjNh`hahbjdhd}rj(jÑjÒhi]hh]hf]hg]hl]uhnMnhohhp]rkhyXfreeformrl…rm}rn(hTUh`NhnNhohhUjhubaubeubjê)ro}rp(hTUhUjIh`hahbjíhd}rq(hf]hg]hh]hi]hl]uhnMnhohhp]rrh})rs}rt(hTXbThe stability level of the package, e.g. ``alpha``, ``experimental``, ``provisional``, ``stable``.hUjoh`hahbhhd}ru(hf]hg]hh]hi]hl]uhnMlhohhp]rv(hyX)The stability level of the package, e.g. rw…rx}ry(hTX)The stability level of the package, e.g. h`NhnNhohhUjsubhß)rz}r{(hTX ``alpha``hd}r|(hf]hg]hh]hi]hl]uhUjshp]r}hyXalphar~…r}r€(hTUhUjzubahbhçubhyX, r…r‚}rƒ(hTX, h`NhnNhohhUjsubhß)r„}r…(hTX``experimental``hd}r†(hf]hg]hh]hi]hl]uhUjshp]r‡hyX experimentalrˆ…r‰}rŠ(hTUhUj„ubahbhçubhyX, r‹…rŒ}r(hTX, rŽh`NhnNhohhUjsubhß)r}r(hTX``provisional``hd}r‘(hf]hg]hh]hi]hl]uhUjshp]r’hyX provisionalr“…r”}r•(hTUhUjubahbhçubhyX, r–…r—}r˜(hTjŽhUjsubhß)r™}rš(hTX ``stable``hd}r›(hf]hg]hh]hi]hl]uhUjshp]rœhyXstabler…rž}rŸ(hTUhUj™ubahbhçubhyX.…r }r¡(hTX.h`NhnNhohhUjsubeubaubeubj¹)r¢}r£(hTUhUjVh`hahbj¼hd}r¤(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r¥}r¦(hTUhUjVh`hahbjÁhd}r§(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr¨jÇj¨uhnNhohhp]r©(jÉ)rª}r«(hTX homepage: URLhUj¥h`hahbjÍhd}r¬(hi]r­Xpkg-field-homepager®ahh]hf]hg]hl]jщuhnMrhohhp]r¯(j¹)r°}r±(hTUhUjªh`hahbj¼hd}r²(hi]hh]hf]hg]hl]Uentries]r³(j×Xhomepage; package.cabal fieldj®UNtr´auhnMrhohhp]ubjÙ)rµ}r¶(hTXhomepager·hUjªh`hahbjÜhd}r¸(jÑjÒhi]hh]hf]hg]hl]uhnMrhohhp]r¹hyXhomepagerº…r»}r¼(hTUh`NhnNhohhUjµubaubjâ)r½}r¾(hTj[hUjªh`hahbjåhd}r¿(jÑjÒhi]hh]hf]hg]hl]uhnMrhohhp]rÀhyX: rÁ…rÂ}rÃ(hTUh`NhnNhohhUj½ubaubja)rÄ}rÅ(hTXURLhUjªh`hahbjdhd}rÆ(jÑjÒhi]hh]hf]hg]hl]uhnMrhohhp]rÇhyXURLrÈ…rÉ}rÊ(hTUh`NhnNhohhUjÄubaubeubjê)rË}rÌ(hTUhUj¥h`hahbjíhd}rÍ(hf]hg]hh]hi]hl]uhnMrhohhp]rÎh})rÏ}rÐ(hTXThe package homepage.rÑhUjËh`hahbhhd}rÒ(hf]hg]hh]hi]hl]uhnMqhohhp]rÓhyXThe package homepage.rÔ…rÕ}rÖ(hTjÑh`NhnNhohhUjÏubaubaubeubj¹)r×}rØ(hTUhUjVh`hahbj¼hd}rÙ(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÚ}rÛ(hTUhUjVh`hahbjÁhd}rÜ(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrÝjÇjÝuhnNhohhp]rÞ(jÉ)rß}rà(hTXbug-reports: URLhUjÚh`hahbjÍhd}rá(hi]râXpkg-field-bug-reportsrãahh]hf]hg]hl]jщuhnM‚hohhp]rä(j¹)rå}ræ(hTUhUjßh`hahbj¼hd}rç(hi]hh]hf]hg]hl]Uentries]rè(j×X bug-reports; package.cabal fieldjãUNtréauhnM‚hohhp]ubjÙ)rê}rë(hTX bug-reportsrìhUjßh`hahbjÜhd}rí(jÑjÒhi]hh]hf]hg]hl]uhnM‚hohhp]rîhyX bug-reportsrï…rð}rñ(hTUh`NhnNhohhUjêubaubjâ)rò}ró(hTj[hUjßh`hahbjåhd}rô(jÑjÒhi]hh]hf]hg]hl]uhnM‚hohhp]rõhyX: rö…r÷}rø(hTUh`NhnNhohhUjòubaubja)rù}rú(hTXURLhUjßh`hahbjdhd}rû(jÑjÒhi]hh]hf]hg]hl]uhnM‚hohhp]rühyXURLrý…rþ}rÿ(hTUh`NhnNhohhUjùubaubeubjê)r}r(hTUhUjÚh`hahbjíhd}r(hf]hg]hh]hi]hl]uhnM‚hohhp]r(h})r}r(hTXMThe URL where users should direct bug reports. This would normally be either:rhUjh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMuhohhp]rhyXMThe URL where users should direct bug reports. This would normally be either:r …r }r (hTjh`NhnNhohhUjubaubh‡)r }r (hTUhUjh`hahbhŠhd}r(hŒX-hi]hh]hf]hg]hl]uhnMxhohhp]r(hŽ)r}r(hTX8A ``mailto:`` URL, e.g. for a person or a mailing list. hUj h`hahbh‘hd}r(hf]hg]hh]hi]hl]uhnNhohhp]rh})r}r(hTX7A ``mailto:`` URL, e.g. for a person or a mailing list.hUjh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMxhp]r(hyXA r…r}r(hTXA hUjubhß)r}r(hTX ``mailto:``hd}r(hf]hg]hh]hi]hl]uhUjhp]rhyXmailto:r…r }r!(hTUhUjubahbhçubhyX* URL, e.g. for a person or a mailing list.r"…r#}r$(hTX* URL, e.g. for a person or a mailing list.hUjubeubaubhŽ)r%}r&(hTXDAn ``http:`` (or ``https:``) URL for an online bug tracking system. hUj h`hahbh‘hd}r'(hf]hg]hh]hi]hl]uhnNhohhp]r(h})r)}r*(hTXCAn ``http:`` (or ``https:``) URL for an online bug tracking system.hUj%h`hahbhhd}r+(hf]hg]hh]hi]hl]uhnMzhp]r,(hyXAn r-…r.}r/(hTXAn hUj)ubhß)r0}r1(hTX ``http:``hd}r2(hf]hg]hh]hi]hl]uhUj)hp]r3hyXhttp:r4…r5}r6(hTUhUj0ubahbhçubhyX (or r7…r8}r9(hTX (or hUj)ubhß)r:}r;(hTX ``https:``hd}r<(hf]hg]hh]hi]hl]uhUj)hp]r=hyXhttps:r>…r?}r@(hTUhUj:ubahbhçubhyX() URL for an online bug tracking system.rA…rB}rC(hTX() URL for an online bug tracking system.hUj)ubeubaubeubh})rD}rE(hTX=For example Cabal itself uses a web-based bug tracking systemrFhUjh`hahbhhd}rG(hf]hg]hh]hi]hl]uhnM}hohhp]rHhyX=For example Cabal itself uses a web-based bug tracking systemrI…rJ}rK(hTjFh`NhnNhohhUjDubaubjÌ)rL}rM(hTX4bug-reports: https://github.com/haskell/cabal/issueshUjh`hahbjÏhd}rN(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]rOhyX4bug-reports: https://github.com/haskell/cabal/issuesrP…rQ}rR(hTUhUjLubaubeubeubj¹)rS}rT(hTUhUjVh`hahbj¼hd}rU(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rV}rW(hTUhUjVh`hahbjÁhd}rX(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrYjÇjYuhnNhohhp]rZ(jÉ)r[}r\(hTXpackage-url: URLhUjVh`hahbjÍhd}r](hi]r^Xpkg-field-package-urlr_ahh]hf]hg]hl]jщuhnM‡hohhp]r`(j¹)ra}rb(hTUhUj[h`hahbj¼hd}rc(hi]hh]hf]hg]hl]Uentries]rd(j×X package-url; package.cabal fieldj_UNtreauhnM‡hohhp]ubjÙ)rf}rg(hTX package-urlrhhUj[h`hahbjÜhd}ri(jÑjÒhi]hh]hf]hg]hl]uhnM‡hohhp]rjhyX package-urlrk…rl}rm(hTUh`NhnNhohhUjfubaubjâ)rn}ro(hTj[hUj[h`hahbjåhd}rp(jÑjÒhi]hh]hf]hg]hl]uhnM‡hohhp]rqhyX: rr…rs}rt(hTUh`NhnNhohhUjnubaubja)ru}rv(hTXURLhUj[h`hahbjdhd}rw(jÑjÒhi]hh]hf]hg]hl]uhnM‡hohhp]rxhyXURLry…rz}r{(hTUh`NhnNhohhUjuubaubeubjê)r|}r}(hTUhUjVh`hahbjíhd}r~(hf]hg]hh]hi]hl]uhnM‡hohhp]rh})r€}r(hTX\The location of a source bundle for the package. The distribution should be a Cabal package.r‚hUj|h`hahbhhd}rƒ(hf]hg]hh]hi]hl]uhnM…hohhp]r„hyX\The location of a source bundle for the package. The distribution should be a Cabal package.r……r†}r‡(hTj‚h`NhnNhohhUj€ubaubaubeubj¹)rˆ}r‰(hTUhUjVh`hahbj¼hd}rŠ(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r‹}rŒ(hTUhUjVh`hahbjÁhd}r(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrŽjÇjŽuhnNhohhp]r(jÉ)r}r‘(hTXsynopsis: freeformhUj‹h`hahbjÍhd}r’(hi]r“Xpkg-field-synopsisr”ahh]hf]hg]hl]jщuhnMŽhohhp]r•(j¹)r–}r—(hTUhUjh`hahbj¼hd}r˜(hi]hh]hf]hg]hl]Uentries]r™(j×Xsynopsis; package.cabal fieldj”UNtršauhnMŽhohhp]ubjÙ)r›}rœ(hTXsynopsisrhUjh`hahbjÜhd}rž(jÑjÒhi]hh]hf]hg]hl]uhnMŽhohhp]rŸhyXsynopsisr …r¡}r¢(hTUh`NhnNhohhUj›ubaubjâ)r£}r¤(hTj[hUjh`hahbjåhd}r¥(jÑjÒhi]hh]hf]hg]hl]uhnMŽhohhp]r¦hyX: r§…r¨}r©(hTUh`NhnNhohhUj£ubaubja)rª}r«(hTXfreeformhUjh`hahbjdhd}r¬(jÑjÒhi]hh]hf]hg]hl]uhnMŽhohhp]r­hyXfreeformr®…r¯}r°(hTUh`NhnNhohhUjªubaubeubjê)r±}r²(hTUhUj‹h`hahbjíhd}r³(hf]hg]hh]hi]hl]uhnMŽhohhp]r´h})rµ}r¶(hTXëA very short description of the package, for use in a table of packages. This is your headline, so keep it short (one line) but as informative as possible. Save space by not including the package name or saying it's written in Haskell.r·hUj±h`hahbhhd}r¸(hf]hg]hh]hi]hl]uhnMŠhohhp]r¹hyXíA very short description of the package, for use in a table of packages. This is your headline, so keep it short (one line) but as informative as possible. Save space by not including the package name or saying it’s written in Haskell.rº…r»}r¼(hTj·h`NhnNhohhUjµubaubaubeubj¹)r½}r¾(hTUhUjVh`hahbj¼hd}r¿(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÀ}rÁ(hTUhUjVh`hahbjÁhd}rÂ(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrÃjÇjÃuhnNhohhp]rÄ(jÉ)rÅ}rÆ(hTXdescription: freeformhUjÀh`hahbjÍhd}rÇ(hi]rÈXpkg-field-descriptionrÉahh]hf]hg]hl]jщuhnM˜hohhp]rÊ(j¹)rË}rÌ(hTUhUjÅh`hahbj¼hd}rÍ(hi]hh]hf]hg]hl]Uentries]rÎ(j×X description; package.cabal fieldjÉUNtrÏauhnM˜hohhp]ubjÙ)rÐ}rÑ(hTX descriptionrÒhUjÅh`hahbjÜhd}rÓ(jÑjÒhi]hh]hf]hg]hl]uhnM˜hohhp]rÔhyX descriptionrÕ…rÖ}r×(hTUh`NhnNhohhUjÐubaubjâ)rØ}rÙ(hTj[hUjÅh`hahbjåhd}rÚ(jÑjÒhi]hh]hf]hg]hl]uhnM˜hohhp]rÛhyX: rÜ…rÝ}rÞ(hTUh`NhnNhohhUjØubaubja)rß}rà(hTXfreeformhUjÅh`hahbjdhd}rá(jÑjÒhi]hh]hf]hg]hl]uhnM˜hohhp]râhyXfreeformrã…rä}rå(hTUh`NhnNhohhUjßubaubeubjê)ræ}rç(hTUhUjÀh`hahbjíhd}rè(hf]hg]hh]hi]hl]uhnM˜hohhp]ré(h})rê}rë(hTX“Description of the package. This may be several paragraphs, and should be aimed at a Haskell programmer who has never heard of your package before.rìhUjæh`hahbhhd}rí(hf]hg]hh]hi]hl]uhnM‘hohhp]rîhyX“Description of the package. This may be several paragraphs, and should be aimed at a Haskell programmer who has never heard of your package before.rï…rð}rñ(hTjìh`NhnNhohhUjêubaubh})rò}ró(hTXšFor library packages, this field is used as prologue text by :ref:`setup-haddock` and thus may contain the same markup as Haddock_ documentation comments.hUjæh`hahbhhd}rô(hf]hg]hh]hi]hl]uhnM•hohhp]rõ(hyX=For library packages, this field is used as prologue text by rö…r÷}rø(hTX=For library packages, this field is used as prologue text by h`NhnNhohhUjòubjk)rù}rú(hTX:ref:`setup-haddock`rûhUjòh`hahbjohd}rü(UreftypeXrefjqˆjrX setup-haddockU refdomainXstdrýhi]hh]U refexplicit‰hf]hg]hl]jtjuuhnM•hp]rþjw)rÿ}r(hTjûhd}r(hf]hg]r(j|jýXstd-refrehh]hi]hl]uhUjùhp]rhyX setup-haddockr…r}r(hTUhUjÿubahbj‚ubaubhyX) and thus may contain the same markup as r…r }r (hTX) and thus may contain the same markup as h`NhnNhohhUjòubj?)r }r (hTXHaddock_jBKhUjòhbjChd}r (UnameXHaddockj~j hi]hh]hf]hg]hl]uhp]rhyXHaddockr…r}r(hTUhUj ubaubhyX documentation comments.r…r}r(hTX documentation comments.h`NhnNhohhUjòubeubeubeubj¹)r}r(hTUhUjVh`hahbj¼hd}r(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r}r(hTUhUjVh`hahbjÁhd}r(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrjÇjuhnNhohhp]r(jÉ)r}r(hTXcategory: freeformhUjh`hahbjÍhd}r(hi]r Xpkg-field-categoryr!ahh]hf]hg]hl]jщuhnMŸhohhp]r"(j¹)r#}r$(hTUhUjh`hahbj¼hd}r%(hi]hh]hf]hg]hl]Uentries]r&(j×Xcategory; package.cabal fieldj!UNtr'auhnMŸhohhp]ubjÙ)r(}r)(hTXcategoryr*hUjh`hahbjÜhd}r+(jÑjÒhi]hh]hf]hg]hl]uhnMŸhohhp]r,hyXcategoryr-…r.}r/(hTUh`NhnNhohhUj(ubaubjâ)r0}r1(hTj[hUjh`hahbjåhd}r2(jÑjÒhi]hh]hf]hg]hl]uhnMŸhohhp]r3hyX: r4…r5}r6(hTUh`NhnNhohhUj0ubaubja)r7}r8(hTXfreeformhUjh`hahbjdhd}r9(jÑjÒhi]hh]hf]hg]hl]uhnMŸhohhp]r:hyXfreeformr;…r<}r=(hTUh`NhnNhohhUj7ubaubeubjê)r>}r?(hTUhUjh`hahbjíhd}r@(hf]hg]hh]hi]hl]uhnMŸhohhp]rAh})rB}rC(hTX¹A classification category for future use by the package catalogue Hackage_. These categories have not yet been specified, but the upper levels of the module hierarchy make a good start.hUj>h`hahbhhd}rD(hf]hg]hh]hi]hl]uhnM›hohhp]rE(hyXBA classification category for future use by the package catalogue rF…rG}rH(hTXBA classification category for future use by the package catalogue h`NhnNhohhUjBubj?)rI}rJ(hTXHackage_jBKhUjBhbjChd}rK(UnameXHackagej~jß hi]hh]hf]hg]hl]uhp]rLhyXHackagerM…rN}rO(hTUhUjIubaubhyXo. These categories have not yet been specified, but the upper levels of the module hierarchy make a good start.rP…rQ}rR(hTXo. These categories have not yet been specified, but the upper levels of the module hierarchy make a good start.h`NhnNhohhUjBubeubaubeubj¹)rS}rT(hTUhUjVh`hahbj¼hd}rU(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rV}rW(hTUhUjVh`hahbjÁhd}rX(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrYjÇjYuhnNhohhp]rZ(jÉ)r[}r\(hTXtested-with: compiler listhUjVh`hahbjÍhd}r](hi]r^Xpkg-field-tested-withr_ahh]hf]hg]hl]jщuhnM¤hohhp]r`(j¹)ra}rb(hTUhUj[h`hahbj¼hd}rc(hi]hh]hf]hg]hl]Uentries]rd(j×X tested-with; package.cabal fieldj_UNtreauhnM¤hohhp]ubjÙ)rf}rg(hTX tested-withrhhUj[h`hahbjÜhd}ri(jÑjÒhi]hh]hf]hg]hl]uhnM¤hohhp]rjhyX tested-withrk…rl}rm(hTUh`NhnNhohhUjfubaubjâ)rn}ro(hTj[hUj[h`hahbjåhd}rp(jÑjÒhi]hh]hf]hg]hl]uhnM¤hohhp]rqhyX: rr…rs}rt(hTUh`NhnNhohhUjnubaubja)ru}rv(hTX compiler listhUj[h`hahbjdhd}rw(jÑjÒhi]hh]hf]hg]hl]uhnM¤hohhp]rxhyX compiler listry…rz}r{(hTUh`NhnNhohhUjuubaubeubjê)r|}r}(hTUhUjVh`hahbjíhd}r~(hf]hg]hh]hi]hl]uhnM¤hohhp]rh})r€}r(hTX_A list of compilers and versions against which the package has been tested (or at least built).r‚hUj|h`hahbhhd}rƒ(hf]hg]hh]hi]hl]uhnM¢hohhp]r„hyX_A list of compilers and versions against which the package has been tested (or at least built).r……r†}r‡(hTj‚h`NhnNhohhUj€ubaubaubeubj¹)rˆ}r‰(hTUhUjVh`hahbj¼hd}rŠ(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r‹}rŒ(hTUhUjVh`hahbjÁhd}r(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrŽjÇjŽuhnNhohhp]r(jÉ)r}r‘(hTXdata-files: filename listhUj‹h`hahbjÍhd}r’(hi]r“Xpkg-field-data-filesr”ahh]hf]hg]hl]jщuhnM¾hohhp]r•(j¹)r–}r—(hTUhUjh`hahbj¼hd}r˜(hi]hh]hf]hg]hl]Uentries]r™(j×Xdata-files; package.cabal fieldj”UNtršauhnM¾hohhp]ubjÙ)r›}rœ(hTX data-filesrhUjh`hahbjÜhd}rž(jÑjÒhi]hh]hf]hg]hl]uhnM¾hohhp]rŸhyX data-filesr …r¡}r¢(hTUh`NhnNhohhUj›ubaubjâ)r£}r¤(hTj[hUjh`hahbjåhd}r¥(jÑjÒhi]hh]hf]hg]hl]uhnM¾hohhp]r¦hyX: r§…r¨}r©(hTUh`NhnNhohhUj£ubaubja)rª}r«(hTX filename listhUjh`hahbjdhd}r¬(jÑjÒhi]hh]hf]hg]hl]uhnM¾hohhp]r­hyX filename listr®…r¯}r°(hTUh`NhnNhohhUjªubaubeubjê)r±}r²(hTUhUj‹h`hahbjíhd}r³(hf]hg]hh]hi]hl]uhnM¾hohhp]r´(h})rµ}r¶(hTXA list of files to be installed for run-time use by the package. This is useful for packages that use a large amount of static data, such as tables of values or code templates. Cabal provides a way to `find these files at run-time `_.hUj±h`hahbhhd}r·(hf]hg]hh]hi]hl]uhnM§hohhp]r¸(hyXÉA list of files to be installed for run-time use by the package. This is useful for packages that use a large amount of static data, such as tables of values or code templates. Cabal provides a way to r¹…rº}r»(hTXÉA list of files to be installed for run-time use by the package. This is useful for packages that use a large amount of static data, such as tables of values or code templates. Cabal provides a way to h`NhnNhohhUjµubj?)r¼}r½(hTXH`find these files at run-time `_hd}r¾(UnameXfind these files at run-timej~X!accessingdatafilesfrompackagecoder¿hi]hh]hf]hg]hl]uhUjµhp]rÀhyXfind these files at run-timerÁ…rÂ}rÃ(hTUhUj¼ubahbjCubj )rÄ}rÅ(hTX) hYKhUjµhbj£hd}rÆ(Urefurij¿hi]rÇUfind-these-files-at-run-timerÈahh]hf]hg]hl]rÉhJauhp]ubhyX.…rÊ}rË(hTX.h`NhnNhohhUjµubeubh})rÌ}rÍ(hTX•A limited form of ``*`` wildcards in file names, for example ``data-files: images/*.png`` matches all the ``.png`` files in the ``images`` directory.hUj±h`hahbhhd}rÎ(hf]hg]hh]hi]hl]uhnM¬hohhp]rÏ(hyXA limited form of rÐ…rÑ}rÒ(hTXA limited form of h`NhnNhohhUjÌubhß)rÓ}rÔ(hTX``*``hd}rÕ(hf]hg]hh]hi]hl]uhUjÌhp]rÖhyX*…r×}rØ(hTUhUjÓubahbhçubhyX& wildcards in file names, for example rÙ…rÚ}rÛ(hTX& wildcards in file names, for example h`NhnNhohhUjÌubhß)rÜ}rÝ(hTX``data-files: images/*.png``hd}rÞ(hf]hg]hh]hi]hl]uhUjÌhp]rßhyXdata-files: images/*.pngrà…rá}râ(hTUhUjÜubahbhçubhyX matches all the rã…rä}rå(hTX matches all the h`NhnNhohhUjÌubhß)ræ}rç(hTX``.png``hd}rè(hf]hg]hh]hi]hl]uhUjÌhp]réhyX.pngrê…rë}rì(hTUhUjæubahbhçubhyX files in the rí…rî}rï(hTX files in the h`NhnNhohhUjÌubhß)rð}rñ(hTX ``images``hd}rò(hf]hg]hh]hi]hl]uhUjÌhp]róhyXimagesrô…rõ}rö(hTUhUjðubahbhçubhyX directory.r÷…rø}rù(hTX directory.h`NhnNhohhUjÌubeubh})rú}rû(hTXûThe limitation is that ``*`` wildcards are only allowed in place of the file name, not in the directory name or file extension. In particular, wildcards do not include directories contents recursively. Furthermore, if a wildcard is used it must be used with an extension, so ``data-files: data/*`` is not allowed. When matching a wildcard plus extension, a file's full extension must match exactly, so ``*.gz`` matches ``foo.gz`` but not ``foo.tar.gz``. A wildcard that does not match any files is an error.hUj±h`hahbhhd}rü(hf]hg]hh]hi]hl]uhnM°hohhp]rý(hyXThe limitation is that rþ…rÿ}r(hTXThe limitation is that h`NhnNhohhUjúubhß)r}r(hTX``*``hd}r(hf]hg]hh]hi]hl]uhUjúhp]rhyX*…r}r(hTUhUjubahbhçubhyX÷ wildcards are only allowed in place of the file name, not in the directory name or file extension. In particular, wildcards do not include directories contents recursively. Furthermore, if a wildcard is used it must be used with an extension, so r…r}r (hTX÷ wildcards are only allowed in place of the file name, not in the directory name or file extension. In particular, wildcards do not include directories contents recursively. Furthermore, if a wildcard is used it must be used with an extension, so h`NhnNhohhUjúubhß)r }r (hTX``data-files: data/*``hd}r (hf]hg]hh]hi]hl]uhUjúhp]r hyXdata-files: data/*r…r}r(hTUhUj ubahbhçubhyXk is not allowed. When matching a wildcard plus extension, a file’s full extension must match exactly, so r…r}r(hTXi is not allowed. When matching a wildcard plus extension, a file's full extension must match exactly, so h`NhnNhohhUjúubhß)r}r(hTX``*.gz``hd}r(hf]hg]hh]hi]hl]uhUjúhp]rhyX*.gzr…r}r(hTUhUjubahbhçubhyX matches r…r}r(hTX matches h`NhnNhohhUjúubhß)r}r(hTX ``foo.gz``hd}r (hf]hg]hh]hi]hl]uhUjúhp]r!hyXfoo.gzr"…r#}r$(hTUhUjubahbhçubhyX but not r%…r&}r'(hTX but not h`NhnNhohhUjúubhß)r(}r)(hTX``foo.tar.gz``hd}r*(hf]hg]hh]hi]hl]uhUjúhp]r+hyX foo.tar.gzr,…r-}r.(hTUhUj(ubahbhçubhyX7. A wildcard that does not match any files is an error.r/…r0}r1(hTX7. A wildcard that does not match any files is an error.h`NhnNhohhUjúubeubh})r2}r3(hTXáThe reason for providing only a very limited form of wildcard is to concisely express the common case of a large number of related files of the same file type without making it too easy to accidentally include unwanted files.r4hUj±h`hahbhhd}r5(hf]hg]hh]hi]hl]uhnMºhohhp]r6hyXáThe reason for providing only a very limited form of wildcard is to concisely express the common case of a large number of related files of the same file type without making it too easy to accidentally include unwanted files.r7…r8}r9(hTj4h`NhnNhohhUj2ubaubeubeubj¹)r:}r;(hTUhUjVh`hahbj¼hd}r<(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r=}r>(hTUhUjVh`hahbjÁhd}r?(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr@jÇj@uhnNhohhp]rA(jÉ)rB}rC(hTXdata-dir: directoryhUj=h`hahbjÍhd}rD(hi]rEXpkg-field-data-dirrFahh]hf]hg]hl]jщuhnMÄhohhp]rG(j¹)rH}rI(hTUhUjBh`hahbj¼hd}rJ(hi]hh]hf]hg]hl]Uentries]rK(j×Xdata-dir; package.cabal fieldjFUNtrLauhnMÄhohhp]ubjÙ)rM}rN(hTXdata-dirrOhUjBh`hahbjÜhd}rP(jÑjÒhi]hh]hf]hg]hl]uhnMÄhohhp]rQhyXdata-dirrR…rS}rT(hTUh`NhnNhohhUjMubaubjâ)rU}rV(hTj[hUjBh`hahbjåhd}rW(jÑjÒhi]hh]hf]hg]hl]uhnMÄhohhp]rXhyX: rY…rZ}r[(hTUh`NhnNhohhUjUubaubja)r\}r](hTX directoryhUjBh`hahbjdhd}r^(jÑjÒhi]hh]hf]hg]hl]uhnMÄhohhp]r_hyX directoryr`…ra}rb(hTUh`NhnNhohhUj\ubaubeubjê)rc}rd(hTUhUj=h`hahbjíhd}re(hf]hg]hh]hi]hl]uhnMÄhohhp]rfh})rg}rh(hTX˜The directory where Cabal looks for data files to install, relative to the source directory. By default, Cabal will look in the source directory itself.rihUjch`hahbhhd}rj(hf]hg]hh]hi]hl]uhnMÁhohhp]rkhyX˜The directory where Cabal looks for data files to install, relative to the source directory. By default, Cabal will look in the source directory itself.rl…rm}rn(hTjih`NhnNhohhUjgubaubaubeubj¹)ro}rp(hTUhUjVh`hahbj¼hd}rq(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rr}rs(hTUhUjVh`hahbjÁhd}rt(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrujÇjuuhnNhohhp]rv(jÉ)rw}rx(hTX!extra-source-files: filename listhUjrh`hahbjÍhd}ry(hi]rzXpkg-field-extra-source-filesr{ahh]hf]hg]hl]jщuhnMÊhohhp]r|(j¹)r}}r~(hTUhUjwh`hahbj¼hd}r(hi]hh]hf]hg]hl]Uentries]r€(j×X'extra-source-files; package.cabal fieldj{UNtrauhnMÊhohhp]ubjÙ)r‚}rƒ(hTXextra-source-filesr„hUjwh`hahbjÜhd}r…(jÑjÒhi]hh]hf]hg]hl]uhnMÊhohhp]r†hyXextra-source-filesr‡…rˆ}r‰(hTUh`NhnNhohhUj‚ubaubjâ)rŠ}r‹(hTj[hUjwh`hahbjåhd}rŒ(jÑjÒhi]hh]hf]hg]hl]uhnMÊhohhp]rhyX: rŽ…r}r(hTUh`NhnNhohhUjŠubaubja)r‘}r’(hTX filename listhUjwh`hahbjdhd}r“(jÑjÒhi]hh]hf]hg]hl]uhnMÊhohhp]r”hyX filename listr•…r–}r—(hTUh`NhnNhohhUj‘ubaubeubjê)r˜}r™(hTUhUjrh`hahbjíhd}rš(hf]hg]hh]hi]hl]uhnMÊhohhp]r›h})rœ}r(hTX¼A list of additional files to be included in source distributions built with :ref:`setup-sdist`. As with :pkg-field:`data-files` it can use a limited form of ``*`` wildcards in file names.hUj˜h`hahbhhd}rž(hf]hg]hh]hi]hl]uhnMÇhohhp]rŸ(hyXMA list of additional files to be included in source distributions built with r …r¡}r¢(hTXMA list of additional files to be included in source distributions built with h`NhnNhohhUjœubjk)r£}r¤(hTX:ref:`setup-sdist`r¥hUjœh`hahbjohd}r¦(UreftypeXrefjqˆjrX setup-sdistU refdomainXstdr§hi]hh]U refexplicit‰hf]hg]hl]jtjuuhnMÇhp]r¨jw)r©}rª(hTj¥hd}r«(hf]hg]r¬(j|j§Xstd-refr­ehh]hi]hl]uhUj£hp]r®hyX setup-sdistr¯…r°}r±(hTUhUj©ubahbj‚ubaubhyX . As with r²…r³}r´(hTX . As with h`NhnNhohhUjœubjk)rµ}r¶(hTX:pkg-field:`data-files`r·hUjœh`hahbjohd}r¸(UreftypeX pkg-fieldjqˆjrX data-filesU refdomainXcabalr¹hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMÇhp]rºhß)r»}r¼(hTj·hd}r½(hf]hg]r¾(j|j¹Xcabal-pkg-fieldr¿ehh]hi]hl]uhUjµhp]rÀhyX data-filesrÁ…rÂ}rÃ(hTUhUj»ubahbhçubaubhyX it can use a limited form of rÄ…rÅ}rÆ(hTX it can use a limited form of h`NhnNhohhUjœubhß)rÇ}rÈ(hTX``*``hd}rÉ(hf]hg]hh]hi]hl]uhUjœhp]rÊhyX*…rË}rÌ(hTUhUjÇubahbhçubhyX wildcards in file names.rÍ…rÎ}rÏ(hTX wildcards in file names.h`NhnNhohhUjœubeubaubeubj¹)rÐ}rÑ(hTUhUjVh`hahbj¼hd}rÒ(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÓ}rÔ(hTUhUjVh`hahbjÁhd}rÕ(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrÖjÇjÖuhnNhohhp]r×(jÉ)rØ}rÙ(hTXextra-doc-files: filename listhUjÓh`hahbjÍhd}rÚ(hi]rÛXpkg-field-extra-doc-filesrÜahh]hf]hg]hl]jщuhnMÑhohhp]rÝ(j¹)rÞ}rß(hTUhUjØh`hahbj¼hd}rà(hi]hh]hf]hg]hl]Uentries]rá(j×X$extra-doc-files; package.cabal fieldjÜUNtrâauhnMÑhohhp]ubjÙ)rã}rä(hTXextra-doc-filesråhUjØh`hahbjÜhd}ræ(jÑjÒhi]hh]hf]hg]hl]uhnMÑhohhp]rçhyXextra-doc-filesrè…ré}rê(hTUh`NhnNhohhUjãubaubjâ)rë}rì(hTj[hUjØh`hahbjåhd}rí(jÑjÒhi]hh]hf]hg]hl]uhnMÑhohhp]rîhyX: rï…rð}rñ(hTUh`NhnNhohhUjëubaubja)rò}ró(hTX filename listhUjØh`hahbjdhd}rô(jÑjÒhi]hh]hf]hg]hl]uhnMÑhohhp]rõhyX filename liströ…r÷}rø(hTUh`NhnNhohhUjòubaubeubjê)rù}rú(hTUhUjÓh`hahbjíhd}rû(hf]hg]hh]hi]hl]uhnMÑhohhp]rüh})rý}rþ(hTXíA list of additional files to be included in source distributions, and also copied to the html directory when Haddock documentation is generated. As with :pkg-field:`data-files` it can use a limited form of ``*`` wildcards in file names.hUjùh`hahbhhd}rÿ(hf]hg]hh]hi]hl]uhnMÍhohhp]r(hyXšA list of additional files to be included in source distributions, and also copied to the html directory when Haddock documentation is generated. As with r…r}r(hTXšA list of additional files to be included in source distributions, and also copied to the html directory when Haddock documentation is generated. As with h`NhnNhohhUjýubjk)r}r(hTX:pkg-field:`data-files`rhUjýh`hahbjohd}r(UreftypeX pkg-fieldjqˆjrX data-filesU refdomainXcabalrhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMÍhp]r hß)r }r (hTjhd}r (hf]hg]r (j|jXcabal-pkg-fieldrehh]hi]hl]uhUjhp]rhyX data-filesr…r}r(hTUhUj ubahbhçubaubhyX it can use a limited form of r…r}r(hTX it can use a limited form of h`NhnNhohhUjýubhß)r}r(hTX``*``hd}r(hf]hg]hh]hi]hl]uhUjýhp]rhyX*…r}r(hTUhUjubahbhçubhyX wildcards in file names.r…r}r(hTX wildcards in file names.h`NhnNhohhUjýubeubaubeubj¹)r}r (hTUhUjVh`hahbj¼hd}r!(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r"}r#(hTUhUjVh`hahbjÁhd}r$(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr%jÇj%uhnNhohhp]r&(jÉ)r'}r((hTXextra-tmp-files: filename listhUj"h`hahbjÍhd}r)(hi]r*Xpkg-field-extra-tmp-filesr+ahh]hf]hg]hl]jщuhnMØhohhp]r,(j¹)r-}r.(hTUhUj'h`hahbj¼hd}r/(hi]hh]hf]hg]hl]Uentries]r0(j×X$extra-tmp-files; package.cabal fieldj+UNtr1auhnMØhohhp]ubjÙ)r2}r3(hTXextra-tmp-filesr4hUj'h`hahbjÜhd}r5(jÑjÒhi]hh]hf]hg]hl]uhnMØhohhp]r6hyXextra-tmp-filesr7…r8}r9(hTUh`NhnNhohhUj2ubaubjâ)r:}r;(hTj[hUj'h`hahbjåhd}r<(jÑjÒhi]hh]hf]hg]hl]uhnMØhohhp]r=hyX: r>…r?}r@(hTUh`NhnNhohhUj:ubaubja)rA}rB(hTX filename listhUj'h`hahbjdhd}rC(jÑjÒhi]hh]hf]hg]hl]uhnMØhohhp]rDhyX filename listrE…rF}rG(hTUh`NhnNhohhUjAubaubeubjê)rH}rI(hTUhUj"h`hahbjíhd}rJ(hf]hg]hh]hi]hl]uhnMØhohhp]rKh})rL}rM(hTXäA list of additional files or directories to be removed by :ref:`setup-clean`. These would typically be additional files created by additional hooks, such as the scheme described in the section on `system-dependent parameters`_hUjHh`hahbhhd}rN(hf]hg]hh]hi]hl]uhnMÔhohhp]rO(hyX;A list of additional files or directories to be removed by rP…rQ}rR(hTX;A list of additional files or directories to be removed by h`NhnNhohhUjLubjk)rS}rT(hTX:ref:`setup-clean`rUhUjLh`hahbjohd}rV(UreftypeXrefjqˆjrX setup-cleanU refdomainXstdrWhi]hh]U refexplicit‰hf]hg]hl]jtjuuhnMÔhp]rXjw)rY}rZ(hTjUhd}r[(hf]hg]r\(j|jWXstd-refr]ehh]hi]hl]uhUjShp]r^hyX setup-cleanr_…r`}ra(hTUhUjYubahbj‚ubaubhyXy. These would typically be additional files created by additional hooks, such as the scheme described in the section on rb…rc}rd(hTXy. These would typically be additional files created by additional hooks, such as the scheme described in the section on h`NhnNhohhUjLubj?)re}rf(hTX`system-dependent parameters`_jBKhUjLhbjChd}rg(UnameXsystem-dependent parametershi]hh]hf]hg]hl]jEjuhp]rhhyXsystem-dependent parametersri…rj}rk(hTUhUjeubaubeubaubeubeubhV)rl}rm(hTUhYKhUh\h`hahbhchd}rn(hf]hg]hh]hi]roj ahl]rphauhnMÚhohhp]rq(hr)rr}rs(hTXLibraryrthUjlh`hahbhvhd}ru(hf]hg]hh]hi]hl]uhnMÚhohhp]rvhyXLibraryrw…rx}ry(hTjth`NhnNhohhUjrubaubj¹)rz}r{(hTUhUjlh`hahbj¼hd}r|(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r}}r~(hTUhUjlh`hahbjÁhd}r(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-sectionr€jÇj€uhnNhohhp]r(jÉ)r‚}rƒ(hTXlibraryr„hUj}h`hahbjÍhd}r…(hi]r†Xpkg-section-library-libraryr‡ahh]hf]hg]hl]jщuhnNhohhp]rˆ(j¹)r‰}rŠ(hTUhUj‚h`hahbj¼hd}r‹(hi]hh]hf]hg]hl]Uentries]rŒ(j×X&library:library; package.cabal sectionj‡UNtrauhnNhohhp]ubjÙ)rŽ}r(hTj„hUj‚h`hahbjÜhd}r(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]r‘hyXlibraryr’…r“}r”(hTUh`NhnNhohhUjŽubaubjâ)r•}r–(hTU hUj‚h`hahbjåhd}r—(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]r˜hyX …r™}rš(hTUh`NhnNhohhUj•ubaubeubjê)r›}rœ(hTUhUj}h`hahbjíhd}r(hf]hg]hh]hi]hl]uhnNhohhp]ržh})rŸ}r (hTXBuild information for libraries. There can be only one library in a package, and it's name is the same as package name set by global :pkg-field:`name` field.hUj›h`hahbhhd}r¡(hf]hg]hh]hi]hl]uhnMßhohhp]r¢(hyX‡Build information for libraries. There can be only one library in a package, and it’s name is the same as package name set by global r£…r¤}r¥(hTX…Build information for libraries. There can be only one library in a package, and it's name is the same as package name set by global h`NhnNhohhUjŸubjk)r¦}r§(hTX:pkg-field:`name`r¨hUjŸh`hahbjohd}r©(UreftypeX pkg-fieldjqˆjrXnameU refdomainXcabalrªhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹j„uhnMßhp]r«hß)r¬}r­(hTj¨hd}r®(hf]hg]r¯(j|jªXcabal-pkg-fieldr°ehh]hi]hl]uhUj¦hp]r±hyXnamer²…r³}r´(hTUhUj¬ubahbhçubaubhyX field.rµ…r¶}r·(hTX field.h`NhnNhohhUjŸubeubaubeubh})r¸}r¹(hTX8The library section should contain the following fields:rºhUjlh`hahbhhd}r»(hf]hg]hh]hi]hl]uhnMãhohhp]r¼hyX8The library section should contain the following fields:r½…r¾}r¿(hTjºh`NhnNhohhUj¸ubaubj¹)rÀ}rÁ(hTUhUjlh`hahbj¼hd}rÂ(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÃ}rÄ(hTUhUjlh`hahbjÁhd}rÅ(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrÆjÇjÆuhnNhohhp]rÇ(jÉ)rÈ}rÉ(hTX exposed-modules: identifier listhUjÃh`hahbjÍhd}rÊ(hi]rËX!pkg-field-library-exposed-modulesrÌahh]hf]hg]hl]jщuhnMêhohhp]rÍ(j¹)rÎ}rÏ(hTUhUjÈh`hahbj¼hd}rÐ(hi]hh]hf]hg]hl]Uentries]rÑ(j×X,library:exposed-modules; package.cabal fieldjÌUNtrÒauhnMêhohhp]ubjÙ)rÓ}rÔ(hTXexposed-modulesrÕhUjÈh`hahbjÜhd}rÖ(jÑjÒhi]hh]hf]hg]hl]uhnMêhohhp]r×hyXexposed-modulesrØ…rÙ}rÚ(hTUh`NhnNhohhUjÓubaubjâ)rÛ}rÜ(hTj[hUjÈh`hahbjåhd}rÝ(jÑjÒhi]hh]hf]hg]hl]uhnMêhohhp]rÞhyX: rß…rà}rá(hTUh`NhnNhohhUjÛubaubja)râ}rã(hTXidentifier listhUjÈh`hahbjdhd}rä(jÑjÒhi]hh]hf]hg]hl]uhnMêhohhp]råhyXidentifier listræ…rç}rè(hTUh`NhnNhohhUjâubaubeubjê)ré}rê(hTUhUjÃh`hahbjíhd}rë(hf]hg]hh]hi]hl]uhnMêhohhp]rì(jð)rí}rî(hTUhUjéh`hahbjóhd}rï(hf]hg]hh]hi]hl]uhnNhohhp]rðjö)rñ}rò(hTUhUjíh`hahbjùhd}ró(hf]hg]hh]hi]hl]uhnMçhohhp]rô(jü)rõ}rö(hTXrequiredhUjñh`hahbjhd}r÷(hf]hg]hh]hi]hl]uhnKhp]røhyXRequiredrù…rú}rû(hTUhUjõubaubj)rü}rý(hTX#if this package contains a library hd}rþ(hf]hg]hh]hi]hl]uhUjñhp]rÿh})r}r(hTX"if this package contains a libraryrhUjüh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMçhp]rhyX"if this package contains a libraryr…r}r(hTjhUjubaubahbjubeubaubh})r}r (hTX(A list of modules added by this package.r hUjéh`hahbhhd}r (hf]hg]hh]hi]hl]uhnMéhohhp]r hyX(A list of modules added by this package.r …r}r(hTj h`NhnNhohhUjubaubeubeubj¹)r}r(hTUhUjlh`hahbj¼hd}r(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r}r(hTUhUjlh`hahbjÁhd}r(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrjÇjuhnNhohhp]r(jÉ)r}r(hTXexposed: booleanhUjh`hahbjÍhd}r(hi]rXpkg-field-library-exposedrahh]hf]hg]hl]jщuhnMûhohhp]r(j¹)r}r(hTUhUjh`hahbj¼hd}r (hi]hh]hf]hg]hl]Uentries]r!(j×X$library:exposed; package.cabal fieldjUNtr"auhnMûhohhp]ubjÙ)r#}r$(hTXexposedr%hUjh`hahbjÜhd}r&(jÑjÒhi]hh]hf]hg]hl]uhnMûhohhp]r'hyXexposedr(…r)}r*(hTUh`NhnNhohhUj#ubaubjâ)r+}r,(hTj[hUjh`hahbjåhd}r-(jÑjÒhi]hh]hf]hg]hl]uhnMûhohhp]r.hyX: r/…r0}r1(hTUh`NhnNhohhUj+ubaubja)r2}r3(hTXbooleanhUjh`hahbjdhd}r4(jÑjÒhi]hh]hf]hg]hl]uhnMûhohhp]r5hyXbooleanr6…r7}r8(hTUh`NhnNhohhUj2ubaubeubjê)r9}r:(hTUhUjh`hahbjíhd}r;(hf]hg]hh]hi]hl]uhnMûhohhp]r<(jð)r=}r>(hTUhUj9h`hahbjóhd}r?(hf]hg]hh]hi]hl]uhnNhohhp]r@jö)rA}rB(hTUhd}rC(hf]hg]hh]hi]hl]uhUj=hp]rD(jü)rE}rF(hTX Default valuehUjAh`hahbjhd}rG(hf]hg]hh]hi]hl]uhnKhp]rHhyX Default valuerI…rJ}rK(hTUhUjEubaubj)rL}rM(hTUhd}rN(hf]hg]hh]hi]hl]uhUjAhp]rOh})rP}rQ(hTXTruehd}rR(hf]hg]hh]hi]hl]uhUjLhp]rShß)rT}rU(hTX``True``hUjPh`hahbhçhd}rV(hf]hg]hh]hi]hl]uhnNhohhp]rWhyXTruerX…rY}rZ(hTUh`NhnNhohhUjTubaubahbhubahbjubehbjùubaubh})r[}r\(hTXmSome Haskell compilers (notably GHC) support the notion of packages being "exposed" or "hidden" which means the modules they provide can be easily imported without always having to specify which package they come from. However this only works effectively if the modules provided by all exposed packages do not overlap (otherwise a module import would be ambiguous).r]hUj9h`hahbhhd}r^(hf]hg]hh]hi]hl]uhnMïhohhp]r_hyXuSome Haskell compilers (notably GHC) support the notion of packages being “exposed†or “hidden†which means the modules they provide can be easily imported without always having to specify which package they come from. However this only works effectively if the modules provided by all exposed packages do not overlap (otherwise a module import would be ambiguous).r`…ra}rb(hTj]h`NhnNhohhUj[ubaubh})rc}rd(hTX>Almost all new libraries use hierarchical module names that do not clash, so it is very uncommon to have to use this field. However it may be necessary to set ``exposed: False`` for some old libraries that use a flat module namespace or where it is known that the exposed modules would clash with other common modules.hUj9h`hahbhhd}re(hf]hg]hh]hi]hl]uhnMöhohhp]rf(hyXŸAlmost all new libraries use hierarchical module names that do not clash, so it is very uncommon to have to use this field. However it may be necessary to set rg…rh}ri(hTXŸAlmost all new libraries use hierarchical module names that do not clash, so it is very uncommon to have to use this field. However it may be necessary to set h`NhnNhohhUjcubhß)rj}rk(hTX``exposed: False``hd}rl(hf]hg]hh]hi]hl]uhUjchp]rmhyXexposed: Falsern…ro}rp(hTUhUjjubahbhçubhyX for some old libraries that use a flat module namespace or where it is known that the exposed modules would clash with other common modules.rq…rr}rs(hTX for some old libraries that use a flat module namespace or where it is known that the exposed modules would clash with other common modules.h`NhnNhohhUjcubeubeubeubj¹)rt}ru(hTUhUjlh`hahbj¼hd}rv(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rw}rx(hTUhUjlh`hahbjÁhd}ry(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrzjÇjzuhnNhohhp]r{(jÉ)r|}r}(hTXreexported-modules: exportlisthUjwh`hahbjÍhd}r~(hi]rX$pkg-field-library-reexported-modulesr€ahh]hf]hg]hl]jщuhnM hohhp]r(j¹)r‚}rƒ(hTUhUj|h`hahbj¼hd}r„(hi]hh]hf]hg]hl]Uentries]r…(j×X/library:reexported-modules; package.cabal fieldj€UNtr†auhnM hohhp]ubjÙ)r‡}rˆ(hTXreexported-modulesr‰hUj|h`hahbjÜhd}rŠ(jÑjÒhi]hh]hf]hg]hl]uhnM hohhp]r‹hyXreexported-modulesrŒ…r}rŽ(hTUh`NhnNhohhUj‡ubaubjâ)r}r(hTj[hUj|h`hahbjåhd}r‘(jÑjÒhi]hh]hf]hg]hl]uhnM hohhp]r’hyX: r“…r”}r•(hTUh`NhnNhohhUjubaubja)r–}r—(hTX exportlisthUj|h`hahbjdhd}r˜(jÑjÒhi]hh]hf]hg]hl]uhnM hohhp]r™hyX exportlistrš…r›}rœ(hTUh`NhnNhohhUj–ubaubeubjê)r}rž(hTUhUjwh`hahbjíhd}rŸ(hf]hg]hh]hi]hl]uhnM hohhp]r (h})r¡}r¢(hTXÄSupported only in GHC 7.10 and later. A list of modules to *reexport* from this package. The syntax of this field is ``orig-pkg:Name as NewName`` to reexport module ``Name`` from ``orig-pkg`` with the new name ``NewName``. We also support abbreviated versions of the syntax: if you omit ``as NewName``, we'll reexport without renaming; if you omit ``orig-pkg``, then we will automatically figure out which package to reexport from, if it's unambiguous.hUjh`hahbhhd}r£(hf]hg]hh]hi]hl]uhnMþhohhp]r¤(hyX;Supported only in GHC 7.10 and later. A list of modules to r¥…r¦}r§(hTX;Supported only in GHC 7.10 and later. A list of modules to h`NhnNhohhUj¡ubh¿)r¨}r©(hTX *reexport*hd}rª(hf]hg]hh]hi]hl]uhUj¡hp]r«hyXreexportr¬…r­}r®(hTUhUj¨ubahbhÇubhyX0 from this package. The syntax of this field is r¯…r°}r±(hTX0 from this package. The syntax of this field is h`NhnNhohhUj¡ubhß)r²}r³(hTX``orig-pkg:Name as NewName``hd}r´(hf]hg]hh]hi]hl]uhUj¡hp]rµhyXorig-pkg:Name as NewNamer¶…r·}r¸(hTUhUj²ubahbhçubhyX to reexport module r¹…rº}r»(hTX to reexport module h`NhnNhohhUj¡ubhß)r¼}r½(hTX``Name``hd}r¾(hf]hg]hh]hi]hl]uhUj¡hp]r¿hyXNamerÀ…rÁ}rÂ(hTUhUj¼ubahbhçubhyX from rÃ…rÄ}rÅ(hTX from h`NhnNhohhUj¡ubhß)rÆ}rÇ(hTX ``orig-pkg``hd}rÈ(hf]hg]hh]hi]hl]uhUj¡hp]rÉhyXorig-pkgrÊ…rË}rÌ(hTUhUjÆubahbhçubhyX with the new name rÍ…rÎ}rÏ(hTX with the new name h`NhnNhohhUj¡ubhß)rÐ}rÑ(hTX ``NewName``hd}rÒ(hf]hg]hh]hi]hl]uhUj¡hp]rÓhyXNewNamerÔ…rÕ}rÖ(hTUhUjÐubahbhçubhyXB. We also support abbreviated versions of the syntax: if you omit r×…rØ}rÙ(hTXB. We also support abbreviated versions of the syntax: if you omit h`NhnNhohhUj¡ubhß)rÚ}rÛ(hTX``as NewName``hd}rÜ(hf]hg]hh]hi]hl]uhUj¡hp]rÝhyX as NewNamerÞ…rß}rà(hTUhUjÚubahbhçubhyX1, we’ll reexport without renaming; if you omit rá…râ}rã(hTX/, we'll reexport without renaming; if you omit h`NhnNhohhUj¡ubhß)rä}rå(hTX ``orig-pkg``hd}ræ(hf]hg]hh]hi]hl]uhUj¡hp]rçhyXorig-pkgrè…ré}rê(hTUhUjäubahbhçubhyX^, then we will automatically figure out which package to reexport from, if it’s unambiguous.rë…rì}rí(hTX\, then we will automatically figure out which package to reexport from, if it's unambiguous.h`NhnNhohhUj¡ubeubh})rî}rï(hTXhReexported modules are useful for compatibility shims when a package has been split into multiple packages, and they have the useful property that if a package provides a module, and another package reexports it under the same name, these are not considered a conflict (as would be the case with a stub module.) They can also be used to resolve name conflicts.rðhUjh`hahbhhd}rñ(hf]hg]hh]hi]hl]uhnMhohhp]ròhyXhReexported modules are useful for compatibility shims when a package has been split into multiple packages, and they have the useful property that if a package provides a module, and another package reexports it under the same name, these are not considered a conflict (as would be the case with a stub module.) They can also be used to resolve name conflicts.ró…rô}rõ(hTjðh`NhnNhohhUjîubaubeubeubh})rö}r÷(hTXhThe library section may also contain build information fields (see the section on `build information`_).hUjlh`hahbhhd}rø(hf]hg]hh]hi]hl]uhnMhohhp]rù(hyXRThe library section may also contain build information fields (see the section on rú…rû}rü(hTXRThe library section may also contain build information fields (see the section on h`NhnNhohhUjöubj?)rý}rþ(hTX`build information`_jBKhUjöhbjChd}rÿ(UnameXbuild informationhi]hh]hf]hg]hl]jEj(uhp]rhyXbuild informationr…r}r(hTUhUjýubaubhyX).r…r}r(hTX).h`NhnNhohhUjöubeubh})r}r(hTXÄCabal 2.0 and later support "internal libraries", which are extra named libraries (as opposed to the usual unnamed library section). For example, suppose that your test suite needs access to some internal modules in your library, which you do not otherwise want to export. You could put these modules in an internal library, which the main library and the test suite :pkg-field:`build-depends` upon. Then your Cabal file might look something like this:hUjlh`hahbhhd}r (hf]hg]hh]hi]hl]uhnMhohhp]r (hyXsCabal 2.0 and later support “internal librariesâ€, which are extra named libraries (as opposed to the usual unnamed library section). For example, suppose that your test suite needs access to some internal modules in your library, which you do not otherwise want to export. You could put these modules in an internal library, which the main library and the test suite r …r }r (hTXoCabal 2.0 and later support "internal libraries", which are extra named libraries (as opposed to the usual unnamed library section). For example, suppose that your test suite needs access to some internal modules in your library, which you do not otherwise want to export. You could put these modules in an internal library, which the main library and the test suite h`NhnNhohhUjubjk)r}r(hTX:pkg-field:`build-depends`rhUjh`hahbjohd}r(UreftypeX pkg-fieldjqˆjrX build-dependsU refdomainXcabalrhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹j„uhnMhp]rhß)r}r(hTjhd}r(hf]hg]r(j|jXcabal-pkg-fieldrehh]hi]hl]uhUjhp]rhyX build-dependsr…r}r(hTUhUjubahbhçubaubhyX; upon. Then your Cabal file might look something like this:r…r}r(hTX; upon. Then your Cabal file might look something like this:h`NhnNhohhUjubeubjÌ)r }r!(hTX„name: foo version: 1.0 license: BSD3 cabal-version: >= 1.23 build-type: Simple library foo-internal exposed-modules: Foo.Internal build-depends: base library exposed-modules: Foo.Public build-depends: foo-internal, base test-suite test-foo type: exitcode-stdio-1.0 main-is: test-foo.hs build-depends: foo-internal, basehUjlh`hahbjÏhd}r"(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]r#hyX„name: foo version: 1.0 license: BSD3 cabal-version: >= 1.23 build-type: Simple library foo-internal exposed-modules: Foo.Internal build-depends: base library exposed-modules: Foo.Public build-depends: foo-internal, base test-suite test-foo type: exitcode-stdio-1.0 main-is: test-foo.hs build-depends: foo-internal, baser$…r%}r&(hTUhUj ubaubh})r'}r((hTXÔInternal libraries are also useful for packages that define multiple executables, but do not define a publically accessible library. Internal libraries are only visible internally in the package (so they can only be added to the :pkg-field:`build-depends` of same-package libraries, executables, test suites, etc.) Internal libraries locally shadow any packages which have the same name (so don't name an internal library with the same name as an external dependency.)hUjlh`hahbhhd}r)(hf]hg]hh]hi]hl]uhnM.hohhp]r*(hyXåInternal libraries are also useful for packages that define multiple executables, but do not define a publically accessible library. Internal libraries are only visible internally in the package (so they can only be added to the r+…r,}r-(hTXåInternal libraries are also useful for packages that define multiple executables, but do not define a publically accessible library. Internal libraries are only visible internally in the package (so they can only be added to the h`NhnNhohhUj'ubjk)r.}r/(hTX:pkg-field:`build-depends`r0hUj'h`hahbjohd}r1(UreftypeX pkg-fieldjqˆjrX build-dependsU refdomainXcabalr2hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹j„uhnM.hp]r3hß)r4}r5(hTj0hd}r6(hf]hg]r7(j|j2Xcabal-pkg-fieldr8ehh]hi]hl]uhUj.hp]r9hyX build-dependsr:…r;}r<(hTUhUj4ubahbhçubaubhyX× of same-package libraries, executables, test suites, etc.) Internal libraries locally shadow any packages which have the same name (so don’t name an internal library with the same name as an external dependency.)r=…r>}r?(hTXÕ of same-package libraries, executables, test suites, etc.) Internal libraries locally shadow any packages which have the same name (so don't name an internal library with the same name as an external dependency.)h`NhnNhohhUj'ubeubeubhV)r@}rA(hTUhUh\h`hahbhchd}rB(hf]hg]hh]hi]rCUopening-an-interpreter-sessionrDahl]rEhFauhnM7hohhp]rF(hr)rG}rH(hTXOpening an interpreter sessionrIhUj@h`hahbhvhd}rJ(hf]hg]hh]hi]hl]uhnM7hohhp]rKhyXOpening an interpreter sessionrL…rM}rN(hTjIh`NhnNhohhUjGubaubh})rO}rP(hTX”While developing a package, it is often useful to make its code available inside an interpreter session. This can be done with the ``repl`` command:hUj@h`hahbhhd}rQ(hf]hg]hh]hi]hl]uhnM9hohhp]rR(hyXƒWhile developing a package, it is often useful to make its code available inside an interpreter session. This can be done with the rS…rT}rU(hTXƒWhile developing a package, it is often useful to make its code available inside an interpreter session. This can be done with the h`NhnNhohhUjOubhß)rV}rW(hTX``repl``hd}rX(hf]hg]hh]hi]hl]uhUjOhp]rYhyXreplrZ…r[}r\(hTUhUjVubahbhçubhyX command:r]…r^}r_(hTX command:h`NhnNhohhUjOubeubjÌ)r`}ra(hTX $ cabal replhUj@h`hahbjÏhd}rb(j‰jXconsolejÑjÒhi]hh]hf]j}hg]hl]uhnM=hohhp]rchyX $ cabal replrd…re}rf(hTUhUj`ubaubh})rg}rh(hTX¥The name comes from the acronym `REPL `__, which stands for "read-eval-print-loop". By default ``cabal repl`` loads the first component in a package. If the package contains several named components, the name can be given as an argument to ``repl``. The name can be also optionally prefixed with the component's type for disambiguation purposes. Example:hUj@h`hahbhhd}ri(hf]hg]hh]hi]hl]uhnMAhohhp]rj(hyX The name comes from the acronym rk…rl}rm(hTX The name comes from the acronym h`NhnNhohhUjgubj?)rn}ro(hTXL`REPL `__hd}rp(UnameXREPLj~XAhttp://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loophi]hh]hf]hg]hl]uhUjghp]rqhyXREPLrr…rs}rt(hTUhUjnubahbjCubhyX:, which stands for “read-eval-print-loopâ€. By default ru…rv}rw(hTX6, which stands for "read-eval-print-loop". By default h`NhnNhohhUjgubhß)rx}ry(hTX``cabal repl``hd}rz(hf]hg]hh]hi]hl]uhUjghp]r{hyX cabal replr|…r}}r~(hTUhUjxubahbhçubhyXƒ loads the first component in a package. If the package contains several named components, the name can be given as an argument to r…r€}r(hTXƒ loads the first component in a package. If the package contains several named components, the name can be given as an argument to h`NhnNhohhUjgubhß)r‚}rƒ(hTX``repl``hd}r„(hf]hg]hh]hi]hl]uhUjghp]r…hyXreplr†…r‡}rˆ(hTUhUj‚ubahbhçubhyXl. The name can be also optionally prefixed with the component’s type for disambiguation purposes. Example:r‰…rŠ}r‹(hTXj. The name can be also optionally prefixed with the component's type for disambiguation purposes. Example:h`NhnNhohhUjgubeubjÌ)rŒ}r(hTXR$ cabal repl foo $ cabal repl exe:foo $ cabal repl test:bar $ cabal repl bench:bazhUj@h`hahbjÏhd}rŽ(j‰jXconsolejÑjÒhi]hh]hf]j}hg]hl]uhnMIhohhp]rhyXR$ cabal repl foo $ cabal repl exe:foo $ cabal repl test:bar $ cabal repl bench:bazr…r‘}r’(hTUhUjŒubaubhV)r“}r”(hTUhUj@h`hahbhchd}r•(hf]hg]hh]hi]r–Ufreezing-dependency-versionsr—ahl]r˜hauhnMQhohhp]r™(hr)rš}r›(hTXFreezing dependency versionsrœhUj“h`hahbhvhd}r(hf]hg]hh]hi]hl]uhnMQhohhp]ržhyXFreezing dependency versionsrŸ…r }r¡(hTjœh`NhnNhohhUjšubaubh})r¢}r£(hTX,If a package is built in several different environments, such as a development environment, a staging environment and a production environment, it may be necessary or desirable to ensure that the same dependency versions are selected in each environment. This can be done with the ``freeze`` command:hUj“h`hahbhhd}r¤(hf]hg]hh]hi]hl]uhnMShohhp]r¥(hyXIf a package is built in several different environments, such as a development environment, a staging environment and a production environment, it may be necessary or desirable to ensure that the same dependency versions are selected in each environment. This can be done with the r¦…r§}r¨(hTXIf a package is built in several different environments, such as a development environment, a staging environment and a production environment, it may be necessary or desirable to ensure that the same dependency versions are selected in each environment. This can be done with the h`NhnNhohhUj¢ubhß)r©}rª(hTX ``freeze``hd}r«(hf]hg]hh]hi]hl]uhUj¢hp]r¬hyXfreezer­…r®}r¯(hTUhUj©ubahbhçubhyX command:r°…r±}r²(hTX command:h`NhnNhohhUj¢ubeubjÌ)r³}r´(hTX$ cabal freezehUj“h`hahbjÏhd}rµ(j‰jXconsolejÑjÒhi]hh]hf]j}hg]hl]uhnMYhohhp]r¶hyX$ cabal freezer·…r¸}r¹(hTUhUj³ubaubh})rº}r»(hTX³The command writes the selected version for all dependencies to the ``cabal.config`` file. All environments which share this file will use the dependency versions specified in it.hUj“h`hahbhhd}r¼(hf]hg]hh]hi]hl]uhnM]hohhp]r½(hyXDThe command writes the selected version for all dependencies to the r¾…r¿}rÀ(hTXDThe command writes the selected version for all dependencies to the h`NhnNhohhUjºubhß)rÁ}rÂ(hTX``cabal.config``hd}rÃ(hf]hg]hh]hi]hl]uhUjºhp]rÄhyX cabal.configrÅ…rÆ}rÇ(hTUhUjÁubahbhçubhyX_ file. All environments which share this file will use the dependency versions specified in it.rÈ…rÉ}rÊ(hTX_ file. All environments which share this file will use the dependency versions specified in it.h`NhnNhohhUjºubeubeubhV)rË}rÌ(hTUhUj@h`hahbhchd}rÍ(hf]hg]hh]hi]rÎU$generating-dependency-version-boundsrÏahl]rÐhauhnMbhohhp]rÑ(hr)rÒ}rÓ(hTX$Generating dependency version boundsrÔhUjËh`hahbhvhd}rÕ(hf]hg]hh]hi]hl]uhnMbhohhp]rÖhyX$Generating dependency version boundsr×…rØ}rÙ(hTjÔh`NhnNhohhUjÒubaubh})rÚ}rÛ(hTXðCabal also has the ability to suggest dependency version bounds that conform to `Package Versioning Policy`_, which is a recommended versioning system for publicly released Cabal packages. This is done by running the ``gen-bounds`` command:hUjËh`hahbhhd}rÜ(hf]hg]hh]hi]hl]uhnMdhohhp]rÝ(hyXPCabal also has the ability to suggest dependency version bounds that conform to rÞ…rß}rà(hTXPCabal also has the ability to suggest dependency version bounds that conform to h`NhnNhohhUjÚubj?)rá}râ(hTX`Package Versioning Policy`_jBKhUjÚhbjChd}rã(UnameXPackage Versioning Policyj~jÖ hi]hh]hf]hg]hl]uhp]rähyXPackage Versioning Policyrå…ræ}rç(hTUhUjáubaubhyXm, which is a recommended versioning system for publicly released Cabal packages. This is done by running the rè…ré}rê(hTXm, which is a recommended versioning system for publicly released Cabal packages. This is done by running the h`NhnNhohhUjÚubhß)rë}rì(hTX``gen-bounds``hd}rí(hf]hg]hh]hi]hl]uhUjÚhp]rîhyX gen-boundsrï…rð}rñ(hTUhUjëubahbhçubhyX command:rò…ró}rô(hTX command:h`NhnNhohhUjÚubeubjÌ)rõ}rö(hTX$ cabal gen-boundshUjËh`hahbjÏhd}r÷(j‰jXconsolejÑjÒhi]hh]hf]j}hg]hl]uhnMihohhp]røhyX$ cabal gen-boundsrù…rú}rû(hTUhUjõubaubh})rü}rý(hTXVFor example, given the following dependencies specified in :pkg-field:`build-depends`:hUjËh`hahbhhd}rþ(hf]hg]hh]hi]hl]uhnMmhohhp]rÿ(hyX;For example, given the following dependencies specified in r…r}r(hTX;For example, given the following dependencies specified in h`NhnNhohhUjüubjk)r}r(hTX:pkg-field:`build-depends`rhUjüh`hahbjohd}r(UreftypeX pkg-fieldjqˆjrX build-dependsU refdomainXcabalrhi]hh]U refexplicit‰hf]hg]hl]jtjuj‹j„uhnMmhp]rhß)r }r (hTjhd}r (hf]hg]r (j|jXcabal-pkg-fieldr ehh]hi]hl]uhUjhp]rhyX build-dependsr…r}r(hTUhUj ubahbhçubaubhyX:…r}r(hTX:h`NhnNhohhUjüubeubjÌ)r}r(hTX*build-depends: foo == 0.5.2 bar == 1.1hUjËh`hahbjÏhd}r(jÑjÒhi]hh]hf]hg]hl]uhnMrhohhp]rhyX*build-depends: foo == 0.5.2 bar == 1.1r…r}r(hTUhUjubaubh})r}r(hTX;``gen-bounds`` will suggest changing them to the following:rhUjËh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMvhohhp]r(hß)r }r!(hTX``gen-bounds``hd}r"(hf]hg]hh]hi]hl]uhUjhp]r#hyX gen-boundsr$…r%}r&(hTUhUj ubahbhçubhyX- will suggest changing them to the following:r'…r(}r)(hTX- will suggest changing them to the following:h`NhnNhohhUjubeubjÌ)r*}r+(hTX<build-depends: foo >= 0.5.2 && < 0.6 bar >= 1.1 && < 1.2hUjËh`hahbjÏhd}r,(jÑjÒhi]hh]hf]hg]hl]uhnMzhohhp]r-hyX<build-depends: foo >= 0.5.2 && < 0.6 bar >= 1.1 && < 1.2r.…r/}r0(hTUhUj*ubaubeubhV)r1}r2(hTUhUj@h`hahbhchd}r3(hf]hg]hh]hi]r4U*listing-outdated-dependency-version-boundsr5ahl]r6hauhnMhohhp]r7(hr)r8}r9(hTX*Listing outdated dependency version boundsr:hUj1h`hahbhvhd}r;(hf]hg]hh]hi]hl]uhnMhohhp]r<hyX*Listing outdated dependency version boundsr=…r>}r?(hTj:h`NhnNhohhUj8ubaubh})r@}rA(hTXManually updating dependency version bounds in a ``.cabal`` file or a freeze file can be tedious, especially when there's a lot of dependencies. The ``cabal outdated`` command is designed to help with that. It will print a list of packages for which there is a new version on Hackage that is outside the version bound specified in the ``build-depends`` field. The ``outdated`` command can also be configured to act on the freeze file (both old- and new-style) and ignore major (or all) version bumps on Hackage for a subset of dependencies.hUj1h`hahbhhd}rB(hf]hg]hh]hi]hl]uhnMhohhp]rC(hyX1Manually updating dependency version bounds in a rD…rE}rF(hTX1Manually updating dependency version bounds in a h`NhnNhohhUj@ubhß)rG}rH(hTX ``.cabal``hd}rI(hf]hg]hh]hi]hl]uhUj@hp]rJhyX.cabalrK…rL}rM(hTUhUjGubahbhçubhyX\ file or a freeze file can be tedious, especially when there’s a lot of dependencies. The rN…rO}rP(hTXZ file or a freeze file can be tedious, especially when there's a lot of dependencies. The h`NhnNhohhUj@ubhß)rQ}rR(hTX``cabal outdated``hd}rS(hf]hg]hh]hi]hl]uhUj@hp]rThyXcabal outdatedrU…rV}rW(hTUhUjQubahbhçubhyX¨ command is designed to help with that. It will print a list of packages for which there is a new version on Hackage that is outside the version bound specified in the rX…rY}rZ(hTX¨ command is designed to help with that. It will print a list of packages for which there is a new version on Hackage that is outside the version bound specified in the h`NhnNhohhUj@ubhß)r[}r\(hTX``build-depends``hd}r](hf]hg]hh]hi]hl]uhUj@hp]r^hyX build-dependsr_…r`}ra(hTUhUj[ubahbhçubhyX field. The rb…rc}rd(hTX field. The h`NhnNhohhUj@ubhß)re}rf(hTX ``outdated``hd}rg(hf]hg]hh]hi]hl]uhUj@hp]rhhyXoutdatedri…rj}rk(hTUhUjeubahbhçubhyX¤ command can also be configured to act on the freeze file (both old- and new-style) and ignore major (or all) version bumps on Hackage for a subset of dependencies.rl…rm}rn(hTX¤ command can also be configured to act on the freeze file (both old- and new-style) and ignore major (or all) version bumps on Hackage for a subset of dependencies.h`NhnNhohhUj@ubeubh})ro}rp(hTX>The following flags are supported by the ``outdated`` command:rqhUj1h`hahbhhd}rr(hf]hg]hh]hi]hl]uhnM‹hohhp]rs(hyX)The following flags are supported by the rt…ru}rv(hTX)The following flags are supported by the h`NhnNhohhUjoubhß)rw}rx(hTX ``outdated``hd}ry(hf]hg]hh]hi]hl]uhUjohp]rzhyXoutdatedr{…r|}r}(hTUhUjwubahbhçubhyX command:r~…r}r€(hTX command:h`NhnNhohhUjoubeubj)r}r‚(hTUhUj1h`hahbjhd}rƒ(hf]hg]hh]hi]hl]uhnNhohhp]r„(j)r…}r†(hTXš``--freeze-file`` Read dependency version bounds from the freeze file (``cabal.config``) instead of the package description file (``$PACKAGENAME.cabal``).hUjh`hahbjhd}r‡(hf]hg]hh]hi]hl]uhnMŽhp]rˆ(j)r‰}rŠ(hTX``--freeze-file``r‹hUj…h`hahbj hd}rŒ(hf]hg]hh]hi]hl]uhnMŽhp]rhß)rŽ}r(hTj‹hd}r(hf]hg]hh]hi]hl]uhUj‰hp]r‘hyX --freeze-filer’…r“}r”(hTUhUjŽubahbhçubaubj3)r•}r–(hTUhd}r—(hf]hg]hh]hi]hl]uhUj…hp]r˜h})r™}rš(hTXˆRead dependency version bounds from the freeze file (``cabal.config``) instead of the package description file (``$PACKAGENAME.cabal``).hUj•h`hahbhhd}r›(hf]hg]hh]hi]hl]uhnMŽhp]rœ(hyX5Read dependency version bounds from the freeze file (r…rž}rŸ(hTX5Read dependency version bounds from the freeze file (hUj™ubhß)r }r¡(hTX``cabal.config``hd}r¢(hf]hg]hh]hi]hl]uhUj™hp]r£hyX cabal.configr¤…r¥}r¦(hTUhUj ubahbhçubhyX+) instead of the package description file (r§…r¨}r©(hTX+) instead of the package description file (hUj™ubhß)rª}r«(hTX``$PACKAGENAME.cabal``hd}r¬(hf]hg]hh]hi]hl]uhUj™hp]r­hyX$PACKAGENAME.cabalr®…r¯}r°(hTUhUjªubahbhçubhyX).r±…r²}r³(hTX).hUj™ubeubahbjMubeubj)r´}rµ(hTX—``--new-freeze-file`` Read dependency version bounds from the new-style freeze file (``cabal.project.freeze``) instead of the package description file.hUjh`hahbjhd}r¶(hf]hg]hh]hi]hl]uhnM‘hohhp]r·(j)r¸}r¹(hTX``--new-freeze-file``rºhUj´h`hahbj hd}r»(hf]hg]hh]hi]hl]uhnM‘hp]r¼hß)r½}r¾(hTjºhd}r¿(hf]hg]hh]hi]hl]uhUj¸hp]rÀhyX--new-freeze-filerÁ…rÂ}rÃ(hTUhUj½ubahbhçubaubj3)rÄ}rÅ(hTUhd}rÆ(hf]hg]hh]hi]hl]uhUj´hp]rÇh})rÈ}rÉ(hTXRead dependency version bounds from the new-style freeze file (``cabal.project.freeze``) instead of the package description file.hUjÄh`hahbhhd}rÊ(hf]hg]hh]hi]hl]uhnM‘hp]rË(hyX?Read dependency version bounds from the new-style freeze file (rÌ…rÍ}rÎ(hTX?Read dependency version bounds from the new-style freeze file (hUjÈubhß)rÏ}rÐ(hTX``cabal.project.freeze``hd}rÑ(hf]hg]hh]hi]hl]uhUjÈhp]rÒhyXcabal.project.freezerÓ…rÔ}rÕ(hTUhUjÏubahbhçubhyX*) instead of the package description file.rÖ…r×}rØ(hTX*) instead of the package description file.hUjÈubeubahbjMubeubj)rÙ}rÚ(hTXP``--simple-output`` Print only the names of outdated dependencies, one per line.hUjh`hahbjhd}rÛ(hf]hg]hh]hi]hl]uhnM“hohhp]rÜ(j)rÝ}rÞ(hTX``--simple-output``rßhUjÙh`hahbj hd}rà(hf]hg]hh]hi]hl]uhnM“hp]ráhß)râ}rã(hTjßhd}rä(hf]hg]hh]hi]hl]uhUjÝhp]råhyX--simple-outputræ…rç}rè(hTUhUjâubahbhçubaubj3)ré}rê(hTUhd}rë(hf]hg]hh]hi]hl]uhUjÙhp]rìh})rí}rî(hTX<Print only the names of outdated dependencies, one per line.rïhUjéh`hahbhhd}rð(hf]hg]hh]hi]hl]uhnM”hp]rñhyX<Print only the names of outdated dependencies, one per line.rò…ró}rô(hTjïhUjíubaubahbjMubeubj)rõ}rö(hTXT``--exit-code`` Exit with a non-zero exit code when there are outdated dependencies.hUjh`hahbjhd}r÷(hf]hg]hh]hi]hl]uhnM•hohhp]rø(j)rù}rú(hTX``--exit-code``rûhUjõh`hahbj hd}rü(hf]hg]hh]hi]hl]uhnM•hp]rýhß)rþ}rÿ(hTjûhd}r(hf]hg]hh]hi]hl]uhUjùhp]rhyX --exit-coder…r}r(hTUhUjþubahbhçubaubj3)r}r(hTUhd}r(hf]hg]hh]hi]hl]uhUjõhp]rh})r }r (hTXDExit with a non-zero exit code when there are outdated dependencies.r hUjh`hahbhhd}r (hf]hg]hh]hi]hl]uhnM–hp]r hyXDExit with a non-zero exit code when there are outdated dependencies.r…r}r(hTj hUj ubaubahbjMubeubj)r}r(hTXL``-q, --quiet`` Don't print any output. Implies ``-v0`` and ``--exit-code``.hUjh`hahbjhd}r(hf]hg]hh]hi]hl]uhnM—hohhp]r(j)r}r(hTX``-q, --quiet``rhUjh`hahbj hd}r(hf]hg]hh]hi]hl]uhnM—hp]rhß)r}r(hTjhd}r(hf]hg]hh]hi]hl]uhUjhp]rhyX -q, --quietr…r}r (hTUhUjubahbhçubaubj3)r!}r"(hTUhd}r#(hf]hg]hh]hi]hl]uhUjhp]r$h})r%}r&(hTX<Don't print any output. Implies ``-v0`` and ``--exit-code``.hUj!h`hahbhhd}r'(hf]hg]hh]hi]hl]uhnM˜hp]r((hyX"Don’t print any output. Implies r)…r*}r+(hTX Don't print any output. Implies hUj%ubhß)r,}r-(hTX``-v0``hd}r.(hf]hg]hh]hi]hl]uhUj%hp]r/hyX-v0r0…r1}r2(hTUhUj,ubahbhçubhyX and r3…r4}r5(hTX and hUj%ubhß)r6}r7(hTX``--exit-code``hd}r8(hf]hg]hh]hi]hl]uhUj%hp]r9hyX --exit-coder:…r;}r<(hTUhUj6ubahbhçubhyX.…r=}r>(hTX.hUj%ubeubahbjMubeubj)r?}r@(hTXn``--ignore`` *PACKAGENAMES* Don't warn about outdated dependency version bounds for the packages in this list.hUjh`hahbjhd}rA(hf]hg]hh]hi]hl]uhnMšhohhp]rB(j)rC}rD(hTX``--ignore`` *PACKAGENAMES*rEhUj?h`hahbj hd}rF(hf]hg]hh]hi]hl]uhnMšhp]rG(hß)rH}rI(hTX ``--ignore``hd}rJ(hf]hg]hh]hi]hl]uhUjChp]rKhyX--ignorerL…rM}rN(hTUhUjHubahbhçubhyX …rO}rP(hTX hUjCubh¿)rQ}rR(hTX*PACKAGENAMES*hd}rS(hf]hg]hh]hi]hl]uhUjChp]rThyX PACKAGENAMESrU…rV}rW(hTUhUjQubahbhÇubeubj3)rX}rY(hTUhd}rZ(hf]hg]hh]hi]hl]uhUj?hp]r[h})r\}r](hTXRDon't warn about outdated dependency version bounds for the packages in this list.r^hUjXh`hahbhhd}r_(hf]hg]hh]hi]hl]uhnMšhp]r`hyXTDon’t warn about outdated dependency version bounds for the packages in this list.ra…rb}rc(hTj^hUj\ubaubahbjMubeubj)rd}re(hTXÖ``--minor`` *[PACKAGENAMES]* Ignore major version bumps for these packages. E.g. if there's a version 2.0 of a package ``pkg`` on Hackage and the freeze file specifies the constraint ``pkg == 1.9``, ``cabal outdated --freeze --minor=pkg`` will only consider the ``pkg`` outdated when there's a version of ``pkg`` on Hackage satisfying ``pkg > 1.9 && < 2.0``. ``--minor`` can also be used without arguments, in that case major version bumps are ignored for all packages. hUjh`hahbjhd}rf(hf]hg]hh]hi]hl]uhnM¢hohhp]rg(j)rh}ri(hTX``--minor`` *[PACKAGENAMES]*rjhUjdh`hahbj hd}rk(hf]hg]hh]hi]hl]uhnM¢hp]rl(hß)rm}rn(hTX ``--minor``hd}ro(hf]hg]hh]hi]hl]uhUjhhp]rphyX--minorrq…rr}rs(hTUhUjmubahbhçubhyX …rt}ru(hTX hUjhubh¿)rv}rw(hTX*[PACKAGENAMES]*hd}rx(hf]hg]hh]hi]hl]uhUjhhp]ryhyX[PACKAGENAMES]rz…r{}r|(hTUhUjvubahbhÇubeubj3)r}}r~(hTUhd}r(hf]hg]hh]hi]hl]uhUjdhp]r€h})r}r‚(hTX¸Ignore major version bumps for these packages. E.g. if there's a version 2.0 of a package ``pkg`` on Hackage and the freeze file specifies the constraint ``pkg == 1.9``, ``cabal outdated --freeze --minor=pkg`` will only consider the ``pkg`` outdated when there's a version of ``pkg`` on Hackage satisfying ``pkg > 1.9 && < 2.0``. ``--minor`` can also be used without arguments, in that case major version bumps are ignored for all packages.hUj}h`hahbhhd}rƒ(hf]hg]hh]hi]hl]uhnMhp]r„(hyX\Ignore major version bumps for these packages. E.g. if there’s a version 2.0 of a package r……r†}r‡(hTXZIgnore major version bumps for these packages. E.g. if there's a version 2.0 of a package hUjubhß)rˆ}r‰(hTX``pkg``hd}rŠ(hf]hg]hh]hi]hl]uhUjhp]r‹hyXpkgrŒ…r}rŽ(hTUhUjˆubahbhçubhyX9 on Hackage and the freeze file specifies the constraint r…r}r‘(hTX9 on Hackage and the freeze file specifies the constraint hUjubhß)r’}r“(hTX``pkg == 1.9``hd}r”(hf]hg]hh]hi]hl]uhUjhp]r•hyX pkg == 1.9r–…r—}r˜(hTUhUj’ubahbhçubhyX, r™…rš}r›(hTX, hUjubhß)rœ}r(hTX'``cabal outdated --freeze --minor=pkg``hd}rž(hf]hg]hh]hi]hl]uhUjhp]rŸhyX#cabal outdated --freeze --minor=pkgr …r¡}r¢(hTUhUjœubahbhçubhyX will only consider the r£…r¤}r¥(hTX will only consider the hUjubhß)r¦}r§(hTX``pkg``hd}r¨(hf]hg]hh]hi]hl]uhUjhp]r©hyXpkgrª…r«}r¬(hTUhUj¦ubahbhçubhyX& outdated when there’s a version of r­…r®}r¯(hTX$ outdated when there's a version of hUjubhß)r°}r±(hTX``pkg``hd}r²(hf]hg]hh]hi]hl]uhUjhp]r³hyXpkgr´…rµ}r¶(hTUhUj°ubahbhçubhyX on Hackage satisfying r·…r¸}r¹(hTX on Hackage satisfying hUjubhß)rº}r»(hTX``pkg > 1.9 && < 2.0``hd}r¼(hf]hg]hh]hi]hl]uhUjhp]r½hyXpkg > 1.9 && < 2.0r¾…r¿}rÀ(hTUhUjºubahbhçubhyX. rÁ…rÂ}rÃ(hTX. hUjubhß)rÄ}rÅ(hTX ``--minor``hd}rÆ(hf]hg]hh]hi]hl]uhUjhp]rÇhyX--minorrÈ…rÉ}rÊ(hTUhUjÄubahbhçubhyXc can also be used without arguments, in that case major version bumps are ignored for all packages.rË…rÌ}rÍ(hTXc can also be used without arguments, in that case major version bumps are ignored for all packages.hUjubeubahbjMubeubeubh})rÎ}rÏ(hTX Examples:rÐhUj1h`hahbhhd}rÑ(hf]hg]hh]hi]hl]uhnM¤hohhp]rÒhyX Examples:rÓ…rÔ}rÕ(hTjÐh`NhnNhohhUjÎubaubjÌ)rÖ}r×(hTXM$ cd /some/package $ cabal outdated Outdated dependencies: haskell-src-exts <1.17 (latest: 1.19.1) language-javascript <0.6 (latest: 0.6.0.9) unix ==2.7.2.0 (latest: 2.7.2.1) $ cabal outdated --simple-output haskell-src-exts language-javascript unix $ cabal outdated --ignore=haskell-src-exts Outdated dependencies: language-javascript <0.6 (latest: 0.6.0.9) unix ==2.7.2.0 (latest: 2.7.2.1) $ cabal outdated --ignore=haskell-src-exts,language-javascript,unix All dependencies are up to date. $ cabal outdated --ignore=haskell-src-exts,language-javascript,unix -q $ echo $? 0 $ cd /some/other/package $ cabal outdated --freeze-file Outdated dependencies: HTTP ==4000.3.3 (latest: 4000.3.4) HUnit ==1.3.1.1 (latest: 1.5.0.0) $ cabal outdated --freeze-file --ignore=HTTP --minor=HUnit Outdated dependencies: HUnit ==1.3.1.1 (latest: 1.3.1.2)hUj1h`hahbjÏhd}rØ(j‰jXconsolejÑjÒhi]hh]hf]j}hg]hl]uhnM¦hohhp]rÙhyXM$ cd /some/package $ cabal outdated Outdated dependencies: haskell-src-exts <1.17 (latest: 1.19.1) language-javascript <0.6 (latest: 0.6.0.9) unix ==2.7.2.0 (latest: 2.7.2.1) $ cabal outdated --simple-output haskell-src-exts language-javascript unix $ cabal outdated --ignore=haskell-src-exts Outdated dependencies: language-javascript <0.6 (latest: 0.6.0.9) unix ==2.7.2.0 (latest: 2.7.2.1) $ cabal outdated --ignore=haskell-src-exts,language-javascript,unix All dependencies are up to date. $ cabal outdated --ignore=haskell-src-exts,language-javascript,unix -q $ echo $? 0 $ cd /some/other/package $ cabal outdated --freeze-file Outdated dependencies: HTTP ==4000.3.3 (latest: 4000.3.4) HUnit ==1.3.1.1 (latest: 1.5.0.0) $ cabal outdated --freeze-file --ignore=HTTP --minor=HUnit Outdated dependencies: HUnit ==1.3.1.1 (latest: 1.3.1.2)rÚ…rÛ}rÜ(hTUhUjÖubaubeubeubhV)rÝ}rÞ(hTUhUh\h`hahbhchd}rß(hf]hg]hh]hi]ràU executablesráahl]râhauhnMÌhohhp]rã(hr)rä}rå(hTX ExecutablesræhUjÝh`hahbhvhd}rç(hf]hg]hh]hi]hl]uhnMÌhohhp]rèhyX Executablesré…rê}rë(hTjæh`NhnNhohhUjäubaubj¹)rì}rí(hTUhUjÝh`hahbj¼hd}rî(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rï}rð(hTUhUjÝh`hahbjÁhd}rñ(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-sectionròjÇjòuhnNhohhp]ró(jÉ)rô}rõ(hTXexecutable namehUjïh`hahbjÍhd}rö(hi]r÷X!pkg-section-executable-executablerøahh]hf]hg]hl]jщuhnNhohhp]rù(j¹)rú}rû(hTUhUjôh`hahbj¼hd}rü(hi]hh]hf]hg]hl]Uentries]rý(j×X,executable:executable; package.cabal sectionjøUNtrþauhnNhohhp]ubjÙ)rÿ}r(hTX executablerhUjôh`hahbjÜhd}r(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rhyX executabler…r}r(hTUh`NhnNhohhUjÿubaubjâ)r}r(hTU hUjôh`hahbjåhd}r (jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]r hyX …r }r (hTUh`NhnNhohhUjubaubja)r }r(hTXnamehUjôh`hahbjdhd}r(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rhyXnamer…r}r(hTUh`NhnNhohhUj ubaubeubjê)r}r(hTUhUjïh`hahbjíhd}r(hf]hg]hh]hi]hl]uhnNhohhp]rh})r}r(hTXëExecutable sections (if present) describe executable programs contained in the package and must have an argument after the section label, which defines the name of the executable. This is a freeform argument but may not contain spaces.rhUjh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMÑhohhp]rhyXëExecutable sections (if present) describe executable programs contained in the package and must have an argument after the section label, which defines the name of the executable. This is a freeform argument but may not contain spaces.r…r}r(hTjh`NhnNhohhUjubaubaubeubh})r }r!(hTXŠThe executable may be described using the following fields, as well as build information fields (see the section on `build information`_).hUjÝh`hahbhhd}r"(hf]hg]hh]hi]hl]uhnMÖhohhp]r#(hyXtThe executable may be described using the following fields, as well as build information fields (see the section on r$…r%}r&(hTXtThe executable may be described using the following fields, as well as build information fields (see the section on h`NhnNhohhUj ubj?)r'}r((hTX`build information`_jBKhUj hbjChd}r)(UnameXbuild informationhi]hh]hf]hg]hl]jEj(uhp]r*hyXbuild informationr+…r,}r-(hTUhUj'ubaubhyX).r.…r/}r0(hTX).h`NhnNhohhUj ubeubj¹)r1}r2(hTUhUjÝh`hahbj¼hd}r3(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r4}r5(hTUhUjÝh`hahbjÁhd}r6(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr7jÇj7uhnNhohhp]r8(jÉ)r9}r:(hTXmain-is: filename (required)hUj4h`hahbjÍhd}r;(hi]r<Xpkg-field-executable-main-isr=ahh]hf]hg]hl]jщuhnMàhohhp]r>(j¹)r?}r@(hTUhUj9h`hahbj¼hd}rA(hi]hh]hf]hg]hl]Uentries]rB(j×X'executable:main-is; package.cabal fieldj=UNtrCauhnMàhohhp]ubjÙ)rD}rE(hTXmain-isrFhUj9h`hahbjÜhd}rG(jÑjÒhi]hh]hf]hg]hl]uhnMàhohhp]rHhyXmain-isrI…rJ}rK(hTUh`NhnNhohhUjDubaubjâ)rL}rM(hTj[hUj9h`hahbjåhd}rN(jÑjÒhi]hh]hf]hg]hl]uhnMàhohhp]rOhyX: rP…rQ}rR(hTUh`NhnNhohhUjLubaubja)rS}rT(hTXfilename (required)hUj9h`hahbjdhd}rU(jÑjÒhi]hh]hf]hg]hl]uhnMàhohhp]rVhyXfilename (required)rW…rX}rY(hTUh`NhnNhohhUjSubaubeubjê)rZ}r[(hTUhUj4h`hahbjíhd}r\(hf]hg]hh]hi]hl]uhnMàhohhp]r]h})r^}r_(hTXThe name of the ``.hs`` or ``.lhs`` file containing the ``Main`` module. Note that it is the ``.hs`` filename that must be listed, even if that file is generated using a preprocessor. The source file must be relative to one of the directories listed in :pkg-field:`hs-source-dirs`.hUjZh`hahbhhd}r`(hf]hg]hh]hi]hl]uhnMÛhohhp]ra(hyXThe name of the rb…rc}rd(hTXThe name of the h`NhnNhohhUj^ubhß)re}rf(hTX``.hs``hd}rg(hf]hg]hh]hi]hl]uhUj^hp]rhhyX.hsri…rj}rk(hTUhUjeubahbhçubhyX or rl…rm}rn(hTX or h`NhnNhohhUj^ubhß)ro}rp(hTX``.lhs``hd}rq(hf]hg]hh]hi]hl]uhUj^hp]rrhyX.lhsrs…rt}ru(hTUhUjoubahbhçubhyX file containing the rv…rw}rx(hTX file containing the h`NhnNhohhUj^ubhß)ry}rz(hTX``Main``hd}r{(hf]hg]hh]hi]hl]uhUj^hp]r|hyXMainr}…r~}r(hTUhUjyubahbhçubhyX module. Note that it is the r€…r}r‚(hTX module. Note that it is the h`NhnNhohhUj^ubhß)rƒ}r„(hTX``.hs``hd}r…(hf]hg]hh]hi]hl]uhUj^hp]r†hyX.hsr‡…rˆ}r‰(hTUhUjƒubahbhçubhyX™ filename that must be listed, even if that file is generated using a preprocessor. The source file must be relative to one of the directories listed in rŠ…r‹}rŒ(hTX™ filename that must be listed, even if that file is generated using a preprocessor. The source file must be relative to one of the directories listed in h`NhnNhohhUj^ubjk)r}rŽ(hTX:pkg-field:`hs-source-dirs`rhUj^h`hahbjohd}r(UreftypeX pkg-fieldjqˆjrXhs-source-dirsU refdomainXcabalr‘hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹X executabler’uhnMÛhp]r“hß)r”}r•(hTjhd}r–(hf]hg]r—(j|j‘Xcabal-pkg-fieldr˜ehh]hi]hl]uhUjhp]r™hyXhs-source-dirsrš…r›}rœ(hTUhUj”ubahbhçubaubhyX.…r}rž(hTX.h`NhnNhohhUj^ubeubaubeubj¹)rŸ}r (hTUhUjÝh`hahbj¼hd}r¡(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r¢}r£(hTUhUjÝh`hahbjÁhd}r¤(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr¥jÇj¥uhnNhohhp]r¦(jÉ)r§}r¨(hTX scope: tokenhUj¢h`hahbjÍhd}r©(hi]rªXpkg-field-executable-scoper«ahh]hf]hg]hl]jщuhnMæhohhp]r¬(j¹)r­}r®(hTUhUj§h`hahbj¼hd}r¯(hi]hh]hf]hg]hl]Uentries]r°(j×X%executable:scope; package.cabal fieldj«UNtr±auhnMæhohhp]ubjÙ)r²}r³(hTXscoper´hUj§h`hahbjÜhd}rµ(jÑjÒhi]hh]hf]hg]hl]uhnMæhohhp]r¶hyXscoper·…r¸}r¹(hTUh`NhnNhohhUj²ubaubjâ)rº}r»(hTj[hUj§h`hahbjåhd}r¼(jÑjÒhi]hh]hf]hg]hl]uhnMæhohhp]r½hyX: r¾…r¿}rÀ(hTUh`NhnNhohhUjºubaubja)rÁ}rÂ(hTXtokenhUj§h`hahbjdhd}rÃ(jÑjÒhi]hh]hf]hg]hl]uhnMæhohhp]rÄhyXtokenrÅ…rÆ}rÇ(hTUh`NhnNhohhUjÁubaubeubjê)rÈ}rÉ(hTUhUj¢h`hahbjíhd}rÊ(hf]hg]hh]hi]hl]uhnMæhohhp]rËh})rÌ}rÍ(hTXÀWhether the executable is ``public`` (default) or ``private``, i.e. meant to be run by other programs rather than the user. Private executables are installed into `$libexecdir/$libexecsubdir`.hUjÈh`hahbhhd}rÎ(hf]hg]hh]hi]hl]uhnMãhohhp]rÏ(hyXWhether the executable is rÐ…rÑ}rÒ(hTXWhether the executable is h`NhnNhohhUjÌubhß)rÓ}rÔ(hTX ``public``hd}rÕ(hf]hg]hh]hi]hl]uhUjÌhp]rÖhyXpublicr×…rØ}rÙ(hTUhUjÓubahbhçubhyX (default) or rÚ…rÛ}rÜ(hTX (default) or h`NhnNhohhUjÌubhß)rÝ}rÞ(hTX ``private``hd}rß(hf]hg]hh]hi]hl]uhUjÌhp]ràhyXprivaterá…râ}rã(hTUhUjÝubahbhçubhyXf, i.e. meant to be run by other programs rather than the user. Private executables are installed into rä…rå}ræ(hTXf, i.e. meant to be run by other programs rather than the user. Private executables are installed into h`NhnNhohhUjÌubcdocutils.nodes title_reference rç)rè}ré(hTX`$libexecdir/$libexecsubdir`hd}rê(hf]hg]hh]hi]hl]uhUjÌhp]rëhyX$libexecdir/$libexecsubdirrì…rí}rî(hTUhUjèubahbUtitle_referencerïubhyX.…rð}rñ(hTX.h`NhnNhohhUjÌubeubaubeubhV)rò}ró(hTUhUjÝh`hahbhchd}rô(hf]hg]hh]hi]rõUrunning-executablesröahl]r÷hauhnMèhohhp]rø(hr)rù}rú(hTXRunning executablesrûhUjòh`hahbhvhd}rü(hf]hg]hh]hi]hl]uhnMèhohhp]rýhyXRunning executablesrþ…rÿ}r(hTjûh`NhnNhohhUjùubaubh})r}r(hTXOYou can have Cabal build and run your executables by using the ``run`` command:hUjòh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMêhohhp]r(hyX?You can have Cabal build and run your executables by using the r…r}r(hTX?You can have Cabal build and run your executables by using the h`NhnNhohhUjubhß)r}r (hTX``run``hd}r (hf]hg]hh]hi]hl]uhUjhp]r hyXrunr …r }r(hTUhUjubahbhçubhyX command:r…r}r(hTX command:h`NhnNhohhUjubeubjÌ)r}r(hTX,$ cabal run EXECUTABLE [-- EXECUTABLE_FLAGS]hUjòh`hahbjÏhd}r(j‰jXconsolejÑjÒhi]hh]hf]j}hg]hl]uhnMíhohhp]rhyX,$ cabal run EXECUTABLE [-- EXECUTABLE_FLAGS]r…r}r(hTUhUjubaubh})r}r(hTXgThis command will configure, build and run the executable ``EXECUTABLE``. The double dash separator is required to distinguish executable flags from ``run``'s own flags. If there is only one executable defined in the whole package, the executable's name can be omitted. See the output of ``cabal help run`` for a list of options you can pass to ``cabal run``.hUjòh`hahbhhd}r(hf]hg]hh]hi]hl]uhnMñhohhp]r(hyX:This command will configure, build and run the executable r…r}r(hTX:This command will configure, build and run the executable h`NhnNhohhUjubhß)r }r!(hTX``EXECUTABLE``hd}r"(hf]hg]hh]hi]hl]uhUjhp]r#hyX EXECUTABLEr$…r%}r&(hTUhUj ubahbhçubhyXM. The double dash separator is required to distinguish executable flags from r'…r(}r)(hTXM. The double dash separator is required to distinguish executable flags from h`NhnNhohhUjubhß)r*}r+(hTX``run``hd}r,(hf]hg]hh]hi]hl]uhUjhp]r-hyXrunr.…r/}r0(hTUhUj*ubahbhçubhyXˆâ€™s own flags. If there is only one executable defined in the whole package, the executable’s name can be omitted. See the output of r1…r2}r3(hTX„'s own flags. If there is only one executable defined in the whole package, the executable's name can be omitted. See the output of h`NhnNhohhUjubhß)r4}r5(hTX``cabal help run``hd}r6(hf]hg]hh]hi]hl]uhUjhp]r7hyXcabal help runr8…r9}r:(hTUhUj4ubahbhçubhyX' for a list of options you can pass to r;…r<}r=(hTX' for a list of options you can pass to h`NhnNhohhUjubhß)r>}r?(hTX ``cabal run``hd}r@(hf]hg]hh]hi]hl]uhUjhp]rAhyX cabal runrB…rC}rD(hTUhUj>ubahbhçubhyX.…rE}rF(hTX.h`NhnNhohhUjubeubeubeubhV)rG}rH(hTUhUh\h`hahbhchd}rI(hf]hg]hh]hi]rJU test-suitesrKahl]rLhauhnMùhohhp]rM(hr)rN}rO(hTX Test suitesrPhUjGh`hahbhvhd}rQ(hf]hg]hh]hi]hl]uhnMùhohhp]rRhyX Test suitesrS…rT}rU(hTjPh`NhnNhohhUjNubaubj¹)rV}rW(hTUhUjGh`hahbj¼hd}rX(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rY}rZ(hTUhUjGh`hahbjÁhd}r[(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-sectionr\jÇj\uhnNhohhp]r](jÉ)r^}r_(hTX test namehUjYh`hahbjÍhd}r`(hi]raXpkg-section-test-testrbahh]hf]hg]hl]jщuhnNhohhp]rc(j¹)rd}re(hTUhUj^h`hahbj¼hd}rf(hi]hh]hf]hg]hl]Uentries]rg(j×X test:test; package.cabal sectionjbUNtrhauhnNhohhp]ubjÙ)ri}rj(hTXtestrkhUj^h`hahbjÜhd}rl(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rmhyXtestrn…ro}rp(hTUh`NhnNhohhUjiubaubjâ)rq}rr(hTU hUj^h`hahbjåhd}rs(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rthyX …ru}rv(hTUh`NhnNhohhUjqubaubja)rw}rx(hTXnamehUj^h`hahbjdhd}ry(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rzhyXnamer{…r|}r}(hTUh`NhnNhohhUjwubaubeubjê)r~}r(hTUhUjYh`hahbjíhd}r€(hf]hg]hh]hi]hl]uhnNhohhp]rh})r‚}rƒ(hTXTest suite sections (if present) describe package test suites and must have an argument after the section label, which defines the name of the test suite. This is a freeform argument, but may not contain spaces. It should be unique among the names of the package's other test suites, the package's executables, and the package itself. Using test suite sections requires at least Cabal version 1.9.2.r„hUj~h`hahbhhd}r…(hf]hg]hh]hi]hl]uhnMþhohhp]r†hyX“Test suite sections (if present) describe package test suites and must have an argument after the section label, which defines the name of the test suite. This is a freeform argument, but may not contain spaces. It should be unique among the names of the package’s other test suites, the package’s executables, and the package itself. Using test suite sections requires at least Cabal version 1.9.2.r‡…rˆ}r‰(hTj„h`NhnNhohhUj‚ubaubaubeubh})rŠ}r‹(hTXŠThe test suite may be described using the following fields, as well as build information fields (see the section on `build information`_).hUjGh`hahbhhd}rŒ(hf]hg]hh]hi]hl]uhnMhohhp]r(hyXtThe test suite may be described using the following fields, as well as build information fields (see the section on rŽ…r}r(hTXtThe test suite may be described using the following fields, as well as build information fields (see the section on h`NhnNhohhUjŠubj?)r‘}r’(hTX`build information`_jBKhUjŠhbjChd}r“(UnameXbuild informationhi]hh]hf]hg]hl]jEj(uhp]r”hyXbuild informationr•…r–}r—(hTUhUj‘ubaubhyX).r˜…r™}rš(hTX).h`NhnNhohhUjŠubeubj¹)r›}rœ(hTUhUjGh`hahbj¼hd}r(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rž}rŸ(hTUhUjGh`hahbjÁhd}r (jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr¡jÇj¡uhnNhohhp]r¢(jÉ)r£}r¤(hTXtype: interface (required)hUjžh`hahbjÍhd}r¥(hi]r¦Xpkg-field-test-typer§ahh]hf]hg]hl]jщuhnMhohhp]r¨(j¹)r©}rª(hTUhUj£h`hahbj¼hd}r«(hi]hh]hf]hg]hl]Uentries]r¬(j×Xtest:type; package.cabal fieldj§UNtr­auhnMhohhp]ubjÙ)r®}r¯(hTXtyper°hUj£h`hahbjÜhd}r±(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]r²hyXtyper³…r´}rµ(hTUh`NhnNhohhUj®ubaubjâ)r¶}r·(hTj[hUj£h`hahbjåhd}r¸(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]r¹hyX: rº…r»}r¼(hTUh`NhnNhohhUj¶ubaubja)r½}r¾(hTXinterface (required)hUj£h`hahbjdhd}r¿(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]rÀhyXinterface (required)rÁ…rÂ}rÃ(hTUh`NhnNhohhUj½ubaubeubjê)rÄ}rÅ(hTUhUjžh`hahbjíhd}rÆ(hf]hg]hh]hi]hl]uhnMhohhp]rÇh})rÈ}rÉ(hTXÜThe interface type and version of the test suite. Cabal supports two test suite interfaces, called ``exitcode-stdio-1.0`` and ``detailed-0.9``. Each of these types may require or disallow other fields as described below.hUjÄh`hahbhhd}rÊ(hf]hg]hh]hi]hl]uhnM hohhp]rË(hyXcThe interface type and version of the test suite. Cabal supports two test suite interfaces, called rÌ…rÍ}rÎ(hTXcThe interface type and version of the test suite. Cabal supports two test suite interfaces, called h`NhnNhohhUjÈubhß)rÏ}rÐ(hTX``exitcode-stdio-1.0``hd}rÑ(hf]hg]hh]hi]hl]uhUjÈhp]rÒhyXexitcode-stdio-1.0rÓ…rÔ}rÕ(hTUhUjÏubahbhçubhyX and rÖ…r×}rØ(hTX and h`NhnNhohhUjÈubhß)rÙ}rÚ(hTX``detailed-0.9``hd}rÛ(hf]hg]hh]hi]hl]uhUjÈhp]rÜhyX detailed-0.9rÝ…rÞ}rß(hTUhUjÙubahbhçubhyXN. Each of these types may require or disallow other fields as described below.rà…rá}râ(hTXN. Each of these types may require or disallow other fields as described below.h`NhnNhohhUjÈubeubaubeubh})rã}rä(hTX%Test suites using the ``exitcode-stdio-1.0`` interface are executables that indicate test failure with a non-zero exit code when run; they may provide human-readable log information through the standard output and error channels. The ``exitcode-stdio-1.0`` type requires the ``main-is`` field.hUjGh`hahbhhd}rå(hf]hg]hh]hi]hl]uhnMhohhp]ræ(hyXTest suites using the rç…rè}ré(hTXTest suites using the h`NhnNhohhUjãubhß)rê}rë(hTX``exitcode-stdio-1.0``hd}rì(hf]hg]hh]hi]hl]uhUjãhp]ríhyXexitcode-stdio-1.0rî…rï}rð(hTUhUjêubahbhçubhyX¾ interface are executables that indicate test failure with a non-zero exit code when run; they may provide human-readable log information through the standard output and error channels. The rñ…rò}ró(hTX¾ interface are executables that indicate test failure with a non-zero exit code when run; they may provide human-readable log information through the standard output and error channels. The h`NhnNhohhUjãubhß)rô}rõ(hTX``exitcode-stdio-1.0``hd}rö(hf]hg]hh]hi]hl]uhUjãhp]r÷hyXexitcode-stdio-1.0rø…rù}rú(hTUhUjôubahbhçubhyX type requires the rû…rü}rý(hTX type requires the h`NhnNhohhUjãubhß)rþ}rÿ(hTX ``main-is``hd}r(hf]hg]hh]hi]hl]uhUjãhp]rhyXmain-isr…r}r(hTUhUjþubahbhçubhyX field.r…r}r(hTX field.h`NhnNhohhUjãubeubj¹)r}r (hTUhUjGh`hahbj¼hd}r (hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r }r (hTUhUjGh`hahbjÁhd}r (jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrjÇjuhnNhohhp]r(jÉ)r}r(hTXmain-is: filenamehUj h`hahbjÍhd}r(hi]rXpkg-field-test-main-israhh]hf]hg]hl]jщuhnNhohhp]r(j¹)r}r(hTUhUjh`hahbj¼hd}r(hi]hh]hf]hg]hl]Uentries]r(j×X!test:main-is; package.cabal fieldjUNtrauhnNhohhp]ubjÙ)r}r(hTXmain-isrhUjh`hahbjÜhd}r(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rhyXmain-isr …r!}r"(hTUh`NhnNhohhUjubaubjâ)r#}r$(hTj[hUjh`hahbjåhd}r%(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]r&hyX: r'…r(}r)(hTUh`NhnNhohhUj#ubaubja)r*}r+(hTXfilenamehUjh`hahbjdhd}r,(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]r-hyXfilenamer.…r/}r0(hTUh`NhnNhohhUj*ubaubeubjê)r1}r2(hTUhUj h`hahbjíhd}r3(hf]hg]hh]hi]hl]uhnNhohhp]r4(jð)r5}r6(hTUhUj1h`hahbjóhd}r7(hf]hg]hh]hi]hl]uhnNhohhp]r8(jö)r9}r:(hTUhUj5h`hahbjùhd}r;(hf]hg]hh]hi]hl]uhnMhohhp]r<(jü)r=}r>(hTXrequiredhUj9h`hahbjhd}r?(hf]hg]hh]hi]hl]uhnKhp]r@hyXRequiredrA…rB}rC(hTUhUj=ubaubj)rD}rE(hTX``exitcode-stdio-1.0``rFhd}rG(hf]hg]hh]hi]hl]uhUj9hp]rHh})rI}rJ(hTjFhUjDh`hahbhhd}rK(hf]hg]hh]hi]hl]uhnMhp]rLhß)rM}rN(hTjFhd}rO(hf]hg]hh]hi]hl]uhUjIhp]rPhyXexitcode-stdio-1.0rQ…rR}rS(hTUhUjMubahbhçubaubahbjubeubjö)rT}rU(hTUhUj5h`hahbjùhd}rV(hf]hg]hh]hi]hl]uhnMhohhp]rW(jü)rX}rY(hTX disallowedhUjTh`hahbjhd}rZ(hf]hg]hh]hi]hl]uhnKhp]r[hyX Disallowedr\…r]}r^(hTUhUjXubaubj)r_}r`(hTX``detailed-0.9`` hd}ra(hf]hg]hh]hi]hl]uhUjThp]rbh})rc}rd(hTX``detailed-0.9``rehUj_h`hahbhhd}rf(hf]hg]hh]hi]hl]uhnMhp]rghß)rh}ri(hTjehd}rj(hf]hg]hh]hi]hl]uhUjchp]rkhyX detailed-0.9rl…rm}rn(hTUhUjhubahbhçubaubahbjubeubeubh})ro}rp(hTXdThe name of the ``.hs`` or ``.lhs`` file containing the ``Main`` module. Note that it is the ``.hs`` filename that must be listed, even if that file is generated using a preprocessor. The source file must be relative to one of the directories listed in :pkg-field:`hs-source-dirs`. This field is analogous to the ``main-is`` field of an executable section.hUj1h`hahbhhd}rq(hf]hg]hh]hi]hl]uhnMhohhp]rr(hyXThe name of the rs…rt}ru(hTXThe name of the h`NhnNhohhUjoubhß)rv}rw(hTX``.hs``hd}rx(hf]hg]hh]hi]hl]uhUjohp]ryhyX.hsrz…r{}r|(hTUhUjvubahbhçubhyX or r}…r~}r(hTX or h`NhnNhohhUjoubhß)r€}r(hTX``.lhs``hd}r‚(hf]hg]hh]hi]hl]uhUjohp]rƒhyX.lhsr„…r…}r†(hTUhUj€ubahbhçubhyX file containing the r‡…rˆ}r‰(hTX file containing the h`NhnNhohhUjoubhß)rŠ}r‹(hTX``Main``hd}rŒ(hf]hg]hh]hi]hl]uhUjohp]rhyXMainrŽ…r}r(hTUhUjŠubahbhçubhyX module. Note that it is the r‘…r’}r“(hTX module. Note that it is the h`NhnNhohhUjoubhß)r”}r•(hTX``.hs``hd}r–(hf]hg]hh]hi]hl]uhUjohp]r—hyX.hsr˜…r™}rš(hTUhUj”ubahbhçubhyX™ filename that must be listed, even if that file is generated using a preprocessor. The source file must be relative to one of the directories listed in r›…rœ}r(hTX™ filename that must be listed, even if that file is generated using a preprocessor. The source file must be relative to one of the directories listed in h`NhnNhohhUjoubjk)rž}rŸ(hTX:pkg-field:`hs-source-dirs`r hUjoh`hahbjohd}r¡(UreftypeX pkg-fieldjqˆjrXhs-source-dirsU refdomainXcabalr¢hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹Xtestr£uhnMhp]r¤hß)r¥}r¦(hTj hd}r§(hf]hg]r¨(j|j¢Xcabal-pkg-fieldr©ehh]hi]hl]uhUjžhp]rªhyXhs-source-dirsr«…r¬}r­(hTUhUj¥ubahbhçubaubhyX!. This field is analogous to the r®…r¯}r°(hTX!. This field is analogous to the h`NhnNhohhUjoubhß)r±}r²(hTX ``main-is``hd}r³(hf]hg]hh]hi]hl]uhUjohp]r´hyXmain-isrµ…r¶}r·(hTUhUj±ubahbhçubhyX field of an executable section.r¸…r¹}rº(hTX field of an executable section.h`NhnNhohhUjoubeubeubeubh})r»}r¼(hTXìTest suites using the ``detailed-0.9`` interface are modules exporting the symbol ``tests :: IO [Test]``. The ``Test`` type is exported by the module ``Distribution.TestSuite`` provided by Cabal. For more details, see the example below.hUjGh`hahbhhd}r½(hf]hg]hh]hi]hl]uhnM"hohhp]r¾(hyXTest suites using the r¿…rÀ}rÁ(hTXTest suites using the h`NhnNhohhUj»ubhß)rÂ}rÃ(hTX``detailed-0.9``hd}rÄ(hf]hg]hh]hi]hl]uhUj»hp]rÅhyX detailed-0.9rÆ…rÇ}rÈ(hTUhUjÂubahbhçubhyX, interface are modules exporting the symbol rÉ…rÊ}rË(hTX, interface are modules exporting the symbol h`NhnNhohhUj»ubhß)rÌ}rÍ(hTX``tests :: IO [Test]``hd}rÎ(hf]hg]hh]hi]hl]uhUj»hp]rÏhyXtests :: IO [Test]rÐ…rÑ}rÒ(hTUhUjÌubahbhçubhyX. The rÓ…rÔ}rÕ(hTX. The h`NhnNhohhUj»ubhß)rÖ}r×(hTX``Test``hd}rØ(hf]hg]hh]hi]hl]uhUj»hp]rÙhyXTestrÚ…rÛ}rÜ(hTUhUjÖubahbhçubhyX type is exported by the module rÝ…rÞ}rß(hTX type is exported by the module h`NhnNhohhUj»ubhß)rà}rá(hTX``Distribution.TestSuite``hd}râ(hf]hg]hh]hi]hl]uhUj»hp]rãhyXDistribution.TestSuiterä…rå}ræ(hTUhUjàubahbhçubhyX< provided by Cabal. For more details, see the example below.rç…rè}ré(hTX< provided by Cabal. For more details, see the example below.h`NhnNhohhUj»ubeubh})rê}rë(hTX÷The ``detailed-0.9`` interface allows Cabal and other test agents to inspect a test suite's results case by case, producing detailed human- and machine-readable log files. The ``detailed-0.9`` interface requires the :pkg-field:`test-module` field.hUjGh`hahbhhd}rì(hf]hg]hh]hi]hl]uhnM'hohhp]rí(hyXThe rî…rï}rð(hTXThe h`NhnNhohhUjêubhß)rñ}rò(hTX``detailed-0.9``hd}ró(hf]hg]hh]hi]hl]uhUjêhp]rôhyX detailed-0.9rõ…rö}r÷(hTUhUjñubahbhçubhyXž interface allows Cabal and other test agents to inspect a test suite’s results case by case, producing detailed human- and machine-readable log files. The rø…rù}rú(hTXœ interface allows Cabal and other test agents to inspect a test suite's results case by case, producing detailed human- and machine-readable log files. The h`NhnNhohhUjêubhß)rû}rü(hTX``detailed-0.9``hd}rý(hf]hg]hh]hi]hl]uhUjêhp]rþhyX detailed-0.9rÿ…r }r (hTUhUjûubahbhçubhyX interface requires the r …r }r (hTX interface requires the h`NhnNhohhUjêubjk)r }r (hTX:pkg-field:`test-module`r hUjêh`hahbjohd}r (UreftypeX pkg-fieldjqˆjrX test-moduleU refdomainXcabalr hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹j£uhnM'hp]r hß)r }r (hTj hd}r (hf]hg]r (j|j Xcabal-pkg-fieldr ehh]hi]hl]uhUj hp]r hyX test-moduler …r }r (hTUhUj ubahbhçubaubhyX field.r …r }r (hTX field.h`NhnNhohhUjêubeubj¹)r }r (hTUhUjGh`hahbj¼hd}r (hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r }r (hTUhUjGh`hahbjÁhd}r (jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr jÇj uhnNhohhp]r (jÉ)r }r (hTXtest-module: identifierhUj h`hahbjÍhd}r! (hi]r" Xpkg-field-test-test-moduler# ahh]hf]hg]hl]jщuhnM2hohhp]r$ (j¹)r% }r& (hTUhUj h`hahbj¼hd}r' (hi]hh]hf]hg]hl]Uentries]r( (j×X%test:test-module; package.cabal fieldj# UNtr) auhnM2hohhp]ubjÙ)r* }r+ (hTX test-moduler, hUj h`hahbjÜhd}r- (jÑjÒhi]hh]hf]hg]hl]uhnM2hohhp]r. hyX test-moduler/ …r0 }r1 (hTUh`NhnNhohhUj* ubaubjâ)r2 }r3 (hTj[hUj h`hahbjåhd}r4 (jÑjÒhi]hh]hf]hg]hl]uhnM2hohhp]r5 hyX: r6 …r7 }r8 (hTUh`NhnNhohhUj2 ubaubja)r9 }r: (hTX identifierhUj h`hahbjdhd}r; (jÑjÒhi]hh]hf]hg]hl]uhnM2hohhp]r< hyX identifierr= …r> }r? (hTUh`NhnNhohhUj9 ubaubeubjê)r@ }rA (hTUhUj h`hahbjíhd}rB (hf]hg]hh]hi]hl]uhnM2hohhp]rC (jð)rD }rE (hTUhUj@ h`hahbjóhd}rF (hf]hg]hh]hi]hl]uhnNhohhp]rG (jö)rH }rI (hTUhUjD h`hahbjùhd}rJ (hf]hg]hh]hi]hl]uhnM.hohhp]rK (jü)rL }rM (hTXrequiredhUjH h`hahbjhd}rN (hf]hg]hh]hi]hl]uhnKhp]rO hyXRequiredrP …rQ }rR (hTUhUjL ubaubj)rS }rT (hTX``detailed-0.9``rU hd}rV (hf]hg]hh]hi]hl]uhUjH hp]rW h})rX }rY (hTjU hUjS h`hahbhhd}rZ (hf]hg]hh]hi]hl]uhnM.hp]r[ hß)r\ }r] (hTjU hd}r^ (hf]hg]hh]hi]hl]uhUjX hp]r_ hyX detailed-0.9r` …ra }rb (hTUhUj\ ubahbhçubaubahbjubeubjö)rc }rd (hTUhUjD h`hahbjùhd}re (hf]hg]hh]hi]hl]uhnM/hohhp]rf (jü)rg }rh (hTX disallowedhUjc h`hahbjhd}ri (hf]hg]hh]hi]hl]uhnKhp]rj hyX Disallowedrk …rl }rm (hTUhUjg ubaubj)rn }ro (hTX``exitcode-stdio-1.0`` hd}rp (hf]hg]hh]hi]hl]uhUjc hp]rq h})rr }rs (hTX``exitcode-stdio-1.0``rt hUjn h`hahbhhd}ru (hf]hg]hh]hi]hl]uhnM/hp]rv hß)rw }rx (hTjt hd}ry (hf]hg]hh]hi]hl]uhUjr hp]rz hyXexitcode-stdio-1.0r{ …r| }r} (hTUhUjw ubahbhçubaubahbjubeubeubh})r~ }r (hTX*The module exporting the ``tests`` symbol.hUj@ h`hahbhhd}r€ (hf]hg]hh]hi]hl]uhnM1hohhp]r (hyXThe module exporting the r‚ …rƒ }r„ (hTXThe module exporting the h`NhnNhohhUj~ ubhß)r… }r† (hTX ``tests``hd}r‡ (hf]hg]hh]hi]hl]uhUj~ hp]rˆ hyXtestsr‰ …rŠ }r‹ (hTUhUj… ubahbhçubhyX symbol.rŒ …r }rŽ (hTX symbol.h`NhnNhohhUj~ ubeubeubeubhV)r }r (hTUhYKhUjGh`hahbhchd}r‘ (hf]r’ X3example: package using exitcode-stdio-1.0 interfacer“ ahg]hh]hi]r” U2example-package-using-exitcode-stdio-1-0-interfacer• ahl]uhnM4hohhp]r– (hr)r— }r˜ (hTX7Example: Package using ``exitcode-stdio-1.0`` interfacer™ hUj h`hahbhvhd}rš (hf]hg]hh]hi]hl]uhnM4hohhp]r› (hyXExample: Package using rœ …r }rž (hTXExample: Package using rŸ h`NhnNhohhUj— ubhß)r  }r¡ (hTX``exitcode-stdio-1.0``r¢ hd}r£ (hf]hg]hh]hi]hl]uhUj— hp]r¤ hyXexitcode-stdio-1.0r¥ …r¦ }r§ (hTUhUj  ubahbhçubhyX interfacer¨ …r© }rª (hTX interfacer« h`NhnNhohhUj— ubeubh})r¬ }r­ (hTX}The example package description and executable source file below demonstrate the use of the ``exitcode-stdio-1.0`` interface.hUj h`hahbhhd}r® (hf]hg]hh]hi]hl]uhnM6hohhp]r¯ (hyX\The example package description and executable source file below demonstrate the use of the r° …r± }r² (hTX\The example package description and executable source file below demonstrate the use of the h`NhnNhohhUj¬ ubhß)r³ }r´ (hTX``exitcode-stdio-1.0``hd}rµ (hf]hg]hh]hi]hl]uhUj¬ hp]r¶ hyXexitcode-stdio-1.0r· …r¸ }r¹ (hTUhUj³ ubahbhçubhyX interface.rº …r» }r¼ (hTX interface.h`NhnNhohhUj¬ ubeubcdocutils.nodes container r½ )r¾ }r¿ (hTUhUj h`UhbU containerrÀ hd}rÁ (hi]r Uid3rà ahh]hf]hg]rÄ Uliteral-block-wrapperrÅ ahl]U literal_blockˆuhnNhohhp]rÆ (cdocutils.nodes caption rÇ )rÈ }rÉ (hTX foo.cabalrÊ hUj¾ h`hahbUcaptionrË hd}rÌ (hf]hg]hh]hi]hl]uhnM9hp]rÍ hyX foo.cabalrÎ …rÏ }rÐ (hTjÊ hUjÈ ubaubjÌ)rÑ }rÒ (hTXØName: foo Version: 1.0 License: BSD3 Cabal-Version: >= 1.9.2 Build-Type: Simple Test-Suite test-foo type: exitcode-stdio-1.0 main-is: test-foo.hs build-depends: basehUj¾ h`hahbjÏhd}rÓ (j‰jXcabaljÑjÒhi]hh]hf]j}hg]hl]uhnM9hp]rÔ hyXØName: foo Version: 1.0 License: BSD3 Cabal-Version: >= 1.9.2 Build-Type: Simple Test-Suite test-foo type: exitcode-stdio-1.0 main-is: test-foo.hs build-depends: baserÕ …rÖ }r× (hTUhUjÑ ubaubeubj½ )rØ }rÙ (hTUhUj h`UhbjÀ hd}rÚ (hi]rÛ Uid4rÜ ahh]hf]hg]rÝ jÅ ahl]U literal_blockˆuhnNhohhp]rÞ (jÇ )rß }rà (hTX test-foo.hsrá hUjØ h`hahbjË hd}râ (hf]hg]hh]hi]hl]uhnMGhp]rã hyX test-foo.hsrä …rå }ræ (hTjá hUjß ubaubjÌ)rç }rè (hTXumodule Main where import System.Exit (exitFailure) main = do putStrLn "This test always fails!" exitFailurehUjØ h`hahbjÏhd}ré (j‰jXhaskelljÑjÒhi]hh]hf]j}hg]hl]uhnMGhp]rê hyXumodule Main where import System.Exit (exitFailure) main = do putStrLn "This test always fails!" exitFailurerë …rì }rí (hTUhUjç ubaubeubeubhV)rî }rï (hTUhUjGh`hahbhchd}rð (hf]hg]hh]hi]rñ U,example-package-using-detailed-0-9-interfacerò ahl]ró h-auhnMShohhp]rô (hr)rõ }rö (hTX1Example: Package using ``detailed-0.9`` interfacer÷ hUjî h`hahbhvhd}rø (hf]hg]hh]hi]hl]uhnMShohhp]rù (hyXExample: Package using rú …rû }rü (hTXExample: Package using rý h`NhnNhohhUjõ ubhß)rþ }rÿ (hTX``detailed-0.9``r!hd}r!(hf]hg]hh]hi]hl]uhUjõ hp]r!hyX detailed-0.9r!…r!}r!(hTUhUjþ ubahbhçubhyX interfacer!…r!}r!(hTX interfacer !h`NhnNhohhUjõ ubeubh})r !}r !(hTXNThe example package description and test module source file below demonstrate the use of the ``detailed-0.9`` interface. The test module also develops a simple implementation of the interface set by ``Distribution.TestSuite``, but in actual usage the implementation would be provided by the library that provides the testing facility.hUjî h`hahbhhd}r !(hf]hg]hh]hi]hl]uhnMUhohhp]r !(hyX]The example package description and test module source file below demonstrate the use of the r!…r!}r!(hTX]The example package description and test module source file below demonstrate the use of the h`NhnNhohhUj !ubhß)r!}r!(hTX``detailed-0.9``hd}r!(hf]hg]hh]hi]hl]uhUj !hp]r!hyX detailed-0.9r!…r!}r!(hTUhUj!ubahbhçubhyXZ interface. The test module also develops a simple implementation of the interface set by r!…r!}r!(hTXZ interface. The test module also develops a simple implementation of the interface set by h`NhnNhohhUj !ubhß)r!}r!(hTX``Distribution.TestSuite``hd}r!(hf]hg]hh]hi]hl]uhUj !hp]r!hyXDistribution.TestSuiter!…r !}r!!(hTUhUj!ubahbhçubhyXm, but in actual usage the implementation would be provided by the library that provides the testing facility.r"!…r#!}r$!(hTXm, but in actual usage the implementation would be provided by the library that provides the testing facility.h`NhnNhohhUj !ubeubj½ )r%!}r&!(hTUhUjî h`UhbjÀ hd}r'!(hi]r(!Uid5r)!ahh]hf]hg]r*!jÅ ahl]U literal_blockˆuhnNhohhp]r+!(jÇ )r,!}r-!(hTX bar.cabalr.!hUj%!h`hahbjË hd}r/!(hf]hg]hh]hi]hl]uhnM[hp]r0!hyX bar.cabalr1!…r2!}r3!(hTj.!hUj,!ubaubjÌ)r4!}r5!(hTXÛName: bar Version: 1.0 License: BSD3 Cabal-Version: >= 1.9.2 Build-Type: Simple Test-Suite test-bar type: detailed-0.9 test-module: Bar build-depends: base, Cabal >= 1.9.2hUj%!h`hahbjÏhd}r6!(j‰jXcabaljÑjÒhi]hh]hf]j}hg]hl]uhnM[hp]r7!hyXÛName: bar Version: 1.0 License: BSD3 Cabal-Version: >= 1.9.2 Build-Type: Simple Test-Suite test-bar type: detailed-0.9 test-module: Bar build-depends: base, Cabal >= 1.9.2r8!…r9!}r:!(hTUhUj4!ubaubeubj½ )r;!}r!Uid6r?!ahh]hf]hg]r@!jÅ ahl]U literal_blockˆuhnNhohhp]rA!(jÇ )rB!}rC!(hTXBar.hsrD!hUj;!h`hahbjË hd}rE!(hf]hg]hh]hi]hl]uhnMjhp]rF!hyXBar.hsrG!…rH!}rI!(hTjD!hUjB!ubaubjÌ)rJ!}rK!(hTX module Bar ( tests ) where import Distribution.TestSuite tests :: IO [Test] tests = return [ Test succeeds, Test fails ] where succeeds = TestInstance { run = return $ Finished Pass , name = "succeeds" , tags = [] , options = [] , setOption = \_ _ -> Right succeeds } fails = TestInstance { run = return $ Finished $ Fail "Always fails!" , name = "fails" , tags = [] , options = [] , setOption = \_ _ -> Right fails }hUj;!h`hahbjÏhd}rL!(j‰jXhaskelljÑjÒhi]hh]hf]j}hg]hl]uhnMjhp]rM!hyX module Bar ( tests ) where import Distribution.TestSuite tests :: IO [Test] tests = return [ Test succeeds, Test fails ] where succeeds = TestInstance { run = return $ Finished Pass , name = "succeeds" , tags = [] , options = [] , setOption = \_ _ -> Right succeeds } fails = TestInstance { run = return $ Finished $ Fail "Always fails!" , name = "fails" , tags = [] , options = [] , setOption = \_ _ -> Right fails }rN!…rO!}rP!(hTUhUjJ!ubaubeubeubhV)rQ!}rR!(hTUhUjGh`hahbhchd}rS!(hf]hg]hh]hi]rT!Urunning-test-suitesrU!ahl]rV!h?auhnM„hohhp]rW!(hr)rX!}rY!(hTXRunning test suitesrZ!hUjQ!h`hahbhvhd}r[!(hf]hg]hh]hi]hl]uhnM„hohhp]r\!hyXRunning test suitesr]!…r^!}r_!(hTjZ!h`NhnNhohhUjX!ubaubh})r`!}ra!(hTXGYou can have Cabal run your test suites using its built-in test runner:rb!hUjQ!h`hahbhhd}rc!(hf]hg]hh]hi]hl]uhnM†hohhp]rd!hyXGYou can have Cabal run your test suites using its built-in test runner:re!…rf!}rg!(hTjb!h`NhnNhohhUj`!ubaubjÌ)rh!}ri!(hTX;$ cabal configure --enable-tests $ cabal build $ cabal testhUjQ!h`hahbjÏhd}rj!(jÑjÒhi]hh]hf]hg]hl]uhnMŠhohhp]rk!hyX;$ cabal configure --enable-tests $ cabal build $ cabal testrl!…rm!}rn!(hTUhUjh!ubaubh})ro!}rp!(hTX[See the output of ``cabal help test`` for a list of options you can pass to ``cabal test``.hUjQ!h`hahbhhd}rq!(hf]hg]hh]hi]hl]uhnMŽhohhp]rr!(hyXSee the output of rs!…rt!}ru!(hTXSee the output of h`NhnNhohhUjo!ubhß)rv!}rw!(hTX``cabal help test``hd}rx!(hf]hg]hh]hi]hl]uhUjo!hp]ry!hyXcabal help testrz!…r{!}r|!(hTUhUjv!ubahbhçubhyX' for a list of options you can pass to r}!…r~!}r!(hTX' for a list of options you can pass to h`NhnNhohhUjo!ubhß)r€!}r!(hTX``cabal test``hd}r‚!(hf]hg]hh]hi]hl]uhUjo!hp]rƒ!hyX cabal testr„!…r…!}r†!(hTUhUj€!ubahbhçubhyX.…r‡!}rˆ!(hTX.h`NhnNhohhUjo!ubeubeubeubhZhV)r‰!}rŠ!(hTUhUh\h`hahbhchd}r‹!(hf]hg]hh]hi]rŒ!Uforeign-librariesr!ahl]rŽ!h+auhnMïhohhp]r!(hr)r!}r‘!(hTXForeign librariesr’!hUj‰!h`hahbhvhd}r“!(hf]hg]hh]hi]hl]uhnMïhohhp]r”!hyXForeign librariesr•!…r–!}r—!(hTj’!h`NhnNhohhUj!ubaubh})r˜!}r™!(hTXÞForeign libraries are system libraries intended to be linked against programs written in C or other "foreign" languages. They come in two primary flavours: dynamic libraries (``.so`` files on Linux, ``.dylib`` files on OSX, ``.dll`` files on Windows, etc.) are linked against executables when the executable is run (or even lazily during execution), while static libraries (``.a`` files on Linux/OSX, ``.lib`` files on Windows) get linked against the executable at compile time.hUj‰!h`hahbhhd}rš!(hf]hg]hh]hi]hl]uhnMñhohhp]r›!(hyX³Foreign libraries are system libraries intended to be linked against programs written in C or other “foreign†languages. They come in two primary flavours: dynamic libraries (rœ!…r!}rž!(hTX¯Foreign libraries are system libraries intended to be linked against programs written in C or other "foreign" languages. They come in two primary flavours: dynamic libraries (h`NhnNhohhUj˜!ubhß)rŸ!}r !(hTX``.so``hd}r¡!(hf]hg]hh]hi]hl]uhUj˜!hp]r¢!hyX.sor£!…r¤!}r¥!(hTUhUjŸ!ubahbhçubhyX files on Linux, r¦!…r§!}r¨!(hTX files on Linux, h`NhnNhohhUj˜!ubhß)r©!}rª!(hTX ``.dylib``hd}r«!(hf]hg]hh]hi]hl]uhUj˜!hp]r¬!hyX.dylibr­!…r®!}r¯!(hTUhUj©!ubahbhçubhyX files on OSX, r°!…r±!}r²!(hTX files on OSX, h`NhnNhohhUj˜!ubhß)r³!}r´!(hTX``.dll``hd}rµ!(hf]hg]hh]hi]hl]uhUj˜!hp]r¶!hyX.dllr·!…r¸!}r¹!(hTUhUj³!ubahbhçubhyXŽ files on Windows, etc.) are linked against executables when the executable is run (or even lazily during execution), while static libraries (rº!…r»!}r¼!(hTXŽ files on Windows, etc.) are linked against executables when the executable is run (or even lazily during execution), while static libraries (h`NhnNhohhUj˜!ubhß)r½!}r¾!(hTX``.a``hd}r¿!(hf]hg]hh]hi]hl]uhUj˜!hp]rÀ!hyX.arÁ!…rÂ!}rÃ!(hTUhUj½!ubahbhçubhyX files on Linux/OSX, rÄ!…rÅ!}rÆ!(hTX files on Linux/OSX, h`NhnNhohhUj˜!ubhß)rÇ!}rÈ!(hTX``.lib``hd}rÉ!(hf]hg]hh]hi]hl]uhUj˜!hp]rÊ!hyX.librË!…rÌ!}rÍ!(hTUhUjÇ!ubahbhçubhyXE files on Windows) get linked against the executable at compile time.rÎ!…rÏ!}rÐ!(hTXE files on Windows) get linked against the executable at compile time.h`NhnNhohhUj˜!ubeubh})rÑ!}rÒ!(hTX3Foreign libraries only work with GHC 7.8 and later.rÓ!hUj‰!h`hahbhhd}rÔ!(hf]hg]hh]hi]hl]uhnMùhohhp]rÕ!hyX3Foreign libraries only work with GHC 7.8 and later.rÖ!…r×!}rØ!(hTjÓ!h`NhnNhohhUjÑ!ubaubh})rÙ!}rÚ!(hTX1A typical stanza for a foreign library looks likerÛ!hUj‰!h`hahbhhd}rÜ!(hf]hg]hh]hi]hl]uhnMûhohhp]rÝ!hyX1A typical stanza for a foreign library looks likerÞ!…rß!}rà!(hTjÛ!h`NhnNhohhUjÙ!ubaubjÌ)rá!}râ!(hTX©foreign-library myforeignlib type: native-shared lib-version-info: 6:3:2 if os(Windows) options: standalone mod-def-file: MyForeignLib.def other-modules: MyForeignLib.SomeModule MyForeignLib.SomeOtherModule build-depends: base >=4.7 && <4.9 hs-source-dirs: src c-sources: csrc/MyForeignLibWrapper.c default-language: Haskell2010hUj‰!h`hahbjÏhd}rã!(jÑjÒhi]hh]hf]hg]hl]uhnMÿhohhp]rä!hyX©foreign-library myforeignlib type: native-shared lib-version-info: 6:3:2 if os(Windows) options: standalone mod-def-file: MyForeignLib.def other-modules: MyForeignLib.SomeModule MyForeignLib.SomeOtherModule build-depends: base >=4.7 && <4.9 hs-source-dirs: src c-sources: csrc/MyForeignLibWrapper.c default-language: Haskell2010rå!…ræ!}rç!(hTUhUjá!ubaubj¹)rè!}ré!(hTUhUj‰!h`hahbj¼hd}rê!(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rë!}rì!(hTUhUj‰!h`hahbjÁhd}rí!(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrî!jÇjî!uhnNhohhp]rï!(jÉ)rð!}rñ!(hTXtype: foreign library typehUjë!h`hahbjÍhd}rò!(hi]ró!Xpkg-field-benchmark-typerô!ahh]hf]hg]hl]jщuhnMhohhp]rõ!(j¹)rö!}r÷!(hTUhUjð!h`hahbj¼hd}rø!(hi]hh]hf]hg]hl]Uentries]rù!(j×X#benchmark:type; package.cabal fieldjô!UNtrú!auhnMhohhp]ubjÙ)rû!}rü!(hTXtypehUjð!h`hahbjÜhd}rý!(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]rþ!hyXtyperÿ!…r"}r"(hTUh`NhnNhohhUjû!ubaubjâ)r"}r"(hTj[hUjð!h`hahbjåhd}r"(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]r"hyX: r"…r"}r"(hTUh`NhnNhohhUj"ubaubja)r "}r "(hTXforeign library typehUjð!h`hahbjdhd}r "(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]r "hyXforeign library typer "…r"}r"(hTUh`NhnNhohhUj "ubaubeubjê)r"}r"(hTUhUjë!h`hahbjíhd}r"(hf]hg]hh]hi]hl]uhnMhohhp]r"h})r"}r"(hTX…Cabal recognizes ``native-static`` and ``native-shared`` here, although we currently only support building `native-shared` libraries.hUj"h`hahbhhd}r"(hf]hg]hh]hi]hl]uhnMhohhp]r"(hyXCabal recognizes r"…r"}r"(hTXCabal recognizes h`NhnNhohhUj"ubhß)r"}r"(hTX``native-static``hd}r"(hf]hg]hh]hi]hl]uhUj"hp]r"hyX native-staticr"…r "}r!"(hTUhUj"ubahbhçubhyX and r""…r#"}r$"(hTX and h`NhnNhohhUj"ubhß)r%"}r&"(hTX``native-shared``hd}r'"(hf]hg]hh]hi]hl]uhUj"hp]r("hyX native-sharedr)"…r*"}r+"(hTUhUj%"ubahbhçubhyX3 here, although we currently only support building r,"…r-"}r."(hTX3 here, although we currently only support building h`NhnNhohhUj"ubjç)r/"}r0"(hTX`native-shared`hd}r1"(hf]hg]hh]hi]hl]uhUj"hp]r2"hyX native-sharedr3"…r4"}r5"(hTUhUj/"ubahbjïubhyX libraries.r6"…r7"}r8"(hTX libraries.h`NhnNhohhUj"ubeubaubeubj¹)r9"}r:"(hTUhUj‰!h`hahbj¼hd}r;"(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r<"}r="(hTUhUj‰!h`hahbjÁhd}r>"(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr?"jÇj?"uhnNhohhp]r@"(jÉ)rA"}rB"(hTX$options: foreign library option listhUj<"h`hahbjÍhd}rC"(hi]rD"Xpkg-field-benchmark-optionsrE"ahh]hf]hg]hl]jщuhnMhohhp]rF"(j¹)rG"}rH"(hTUhUjA"h`hahbj¼hd}rI"(hi]hh]hf]hg]hl]Uentries]rJ"(j×X&benchmark:options; package.cabal fieldjE"UNtrK"auhnMhohhp]ubjÙ)rL"}rM"(hTXoptionsrN"hUjA"h`hahbjÜhd}rO"(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]rP"hyXoptionsrQ"…rR"}rS"(hTUh`NhnNhohhUjL"ubaubjâ)rT"}rU"(hTj[hUjA"h`hahbjåhd}rV"(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]rW"hyX: rX"…rY"}rZ"(hTUh`NhnNhohhUjT"ubaubja)r["}r\"(hTXforeign library option listhUjA"h`hahbjdhd}r]"(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]r^"hyXforeign library option listr_"…r`"}ra"(hTUh`NhnNhohhUj["ubaubeubjê)rb"}rc"(hTUhUj<"h`hahbjíhd}rd"(hf]hg]hh]hi]hl]uhnMhohhp]re"h})rf"}rg"(hTX Options for building the foreign library, typically specific to the specified type of foreign library. Currently we only support ``standalone`` here. A standalone dynamic library is one that does not have any dependencies on other (Haskell) shared libraries; without the ``standalone`` option the generated library would have dependencies on the Haskell runtime library (``libHSrts``), the base library (``libHSbase``), etc. Currently, ``standalone`` *must* be used on Windows and *must not* be used on any other platform.hUjb"h`hahbhhd}rh"(hf]hg]hh]hi]hl]uhnMhohhp]ri"(hyXOptions for building the foreign library, typically specific to the specified type of foreign library. Currently we only support rj"…rk"}rl"(hTXOptions for building the foreign library, typically specific to the specified type of foreign library. Currently we only support h`NhnNhohhUjf"ubhß)rm"}rn"(hTX``standalone``hd}ro"(hf]hg]hh]hi]hl]uhUjf"hp]rp"hyX standalonerq"…rr"}rs"(hTUhUjm"ubahbhçubhyX€ here. A standalone dynamic library is one that does not have any dependencies on other (Haskell) shared libraries; without the rt"…ru"}rv"(hTX€ here. A standalone dynamic library is one that does not have any dependencies on other (Haskell) shared libraries; without the h`NhnNhohhUjf"ubhß)rw"}rx"(hTX``standalone``hd}ry"(hf]hg]hh]hi]hl]uhUjf"hp]rz"hyX standaloner{"…r|"}r}"(hTUhUjw"ubahbhçubhyXV option the generated library would have dependencies on the Haskell runtime library (r~"…r"}r€"(hTXV option the generated library would have dependencies on the Haskell runtime library (h`NhnNhohhUjf"ubhß)r"}r‚"(hTX ``libHSrts``hd}rƒ"(hf]hg]hh]hi]hl]uhUjf"hp]r„"hyXlibHSrtsr…"…r†"}r‡"(hTUhUj"ubahbhçubhyX), the base library (rˆ"…r‰"}rŠ"(hTX), the base library (h`NhnNhohhUjf"ubhß)r‹"}rŒ"(hTX ``libHSbase``hd}r"(hf]hg]hh]hi]hl]uhUjf"hp]rŽ"hyX libHSbaser"…r"}r‘"(hTUhUj‹"ubahbhçubhyX), etc. Currently, r’"…r“"}r”"(hTX), etc. Currently, h`NhnNhohhUjf"ubhß)r•"}r–"(hTX``standalone``hd}r—"(hf]hg]hh]hi]hl]uhUjf"hp]r˜"hyX standaloner™"…rš"}r›"(hTUhUj•"ubahbhçubhyX …rœ"}r"(hTX h`NhnNhohhUjf"ubh¿)rž"}rŸ"(hTX*must*hd}r "(hf]hg]hh]hi]hl]uhUjf"hp]r¡"hyXmustr¢"…r£"}r¤"(hTUhUjž"ubahbhÇubhyX be used on Windows and r¥"…r¦"}r§"(hTX be used on Windows and h`NhnNhohhUjf"ubh¿)r¨"}r©"(hTX *must not*hd}rª"(hf]hg]hh]hi]hl]uhUjf"hp]r«"hyXmust notr¬"…r­"}r®"(hTUhUj¨"ubahbhÇubhyX be used on any other platform.r¯"…r°"}r±"(hTX be used on any other platform.h`NhnNhohhUjf"ubeubaubeubj¹)r²"}r³"(hTUhUj‰!h`hahbj¼hd}r´"(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rµ"}r¶"(hTUhUj‰!h`hahbjÁhd}r·"(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr¸"jÇj¸"uhnNhohhp]r¹"(jÉ)rº"}r»"(hTXmod-def-file: filenamehUjµ"h`hahbjÍhd}r¼"(hi]r½"X pkg-field-benchmark-mod-def-filer¾"ahh]hf]hg]hl]jщuhnM&hohhp]r¿"(j¹)rÀ"}rÁ"(hTUhUjº"h`hahbj¼hd}rÂ"(hi]hh]hf]hg]hl]Uentries]rÃ"(j×X+benchmark:mod-def-file; package.cabal fieldj¾"UNtrÄ"auhnM&hohhp]ubjÙ)rÅ"}rÆ"(hTX mod-def-filerÇ"hUjº"h`hahbjÜhd}rÈ"(jÑjÒhi]hh]hf]hg]hl]uhnM&hohhp]rÉ"hyX mod-def-filerÊ"…rË"}rÌ"(hTUh`NhnNhohhUjÅ"ubaubjâ)rÍ"}rÎ"(hTj[hUjº"h`hahbjåhd}rÏ"(jÑjÒhi]hh]hf]hg]hl]uhnM&hohhp]rÐ"hyX: rÑ"…rÒ"}rÓ"(hTUh`NhnNhohhUjÍ"ubaubja)rÔ"}rÕ"(hTXfilenamehUjº"h`hahbjdhd}rÖ"(jÑjÒhi]hh]hf]hg]hl]uhnM&hohhp]r×"hyXfilenamerØ"…rÙ"}rÚ"(hTUh`NhnNhohhUjÔ"ubaubeubjê)rÛ"}rÜ"(hTUhUjµ"h`hahbjíhd}rÝ"(hf]hg]hh]hi]hl]uhnM&hohhp]rÞ"h})rß"}rà"(hTX§This option can only be used when creating dynamic Windows libraries (that is, when using ``native-shared`` and the ``os`` is ``Windows``). If used, it must be a path to a _module definition file_. The details of module definition files are beyond the scope of this document; see the `GHC `_ manual for some details and some further pointers.hUjÛ"h`hahbhhd}rá"(hf]hg]hh]hi]hl]uhnM hohhp]râ"(hyXZThis option can only be used when creating dynamic Windows libraries (that is, when using rã"…rä"}rå"(hTXZThis option can only be used when creating dynamic Windows libraries (that is, when using h`NhnNhohhUjß"ubhß)ræ"}rç"(hTX``native-shared``hd}rè"(hf]hg]hh]hi]hl]uhUjß"hp]ré"hyX native-sharedrê"…rë"}rì"(hTUhUjæ"ubahbhçubhyX and the rí"…rî"}rï"(hTX and the h`NhnNhohhUjß"ubhß)rð"}rñ"(hTX``os``hd}rò"(hf]hg]hh]hi]hl]uhUjß"hp]ró"hyXosrô"…rõ"}rö"(hTUhUjð"ubahbhçubhyX is r÷"…rø"}rù"(hTX is h`NhnNhohhUjß"ubhß)rú"}rû"(hTX ``Windows``hd}rü"(hf]hg]hh]hi]hl]uhUjß"hp]rý"hyXWindowsrþ"…rÿ"}r#(hTUhUjú"ubahbhçubhyX6). If used, it must be a path to a _module definition r#…r#}r#(hTX6). If used, it must be a path to a _module definition h`NhnNhohhUjß"ubcdocutils.nodes problematic r#)r#}r#(hTXfile_r#hUjß"h`NhbU problematicr#hd}r #(hi]r #Uid9r #ahh]hf]hg]hl]UrefidUid8r #uhnNhohhp]r #hyXfile_r#…r#}r#(hTUh`NhnNhohhUj#ubaubhyXX. The details of module definition files are beyond the scope of this document; see the r#…r#}r#(hTXX. The details of module definition files are beyond the scope of this document; see the h`NhnNhohhUjß"ubj?)r#}r#(hTXX`GHC `_hd}r#(UnameXGHCj~XOhttps://downloads.haskell.org/~ghc/latest/docs/html/users_guide/win32-dlls.htmlr#hi]hh]hf]hg]hl]uhUjß"hp]r#hyXGHCr#…r#}r#(hTUhUj#ubahbjCubj )r#}r#(hTXR hYKhUjß"hbj£hd}r#(Urefurij#hi]r#Ughcr #ahh]hf]hg]hl]r!#h0auhp]ubhyX3 manual for some details and some further pointers.r"#…r##}r$#(hTX3 manual for some details and some further pointers.h`NhnNhohhUjß"ubeubaubeubj¹)r%#}r&#(hTUhUj‰!h`hahbj¼hd}r'#(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r(#}r)#(hTUhUj‰!h`hahbjÁhd}r*#(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr+#jÇj+#uhnNhohhp]r,#(jÉ)r-#}r.#(hTX&lib-version-info: current:revision:agehUj(#h`hahbjÍhd}r/#(hi]r0#X$pkg-field-benchmark-lib-version-infor1#ahh]hf]hg]hl]jщuhnMFhohhp]r2#(j¹)r3#}r4#(hTUhUj-#h`hahbj¼hd}r5#(hi]hh]hf]hg]hl]Uentries]r6#(j×X/benchmark:lib-version-info; package.cabal fieldj1#UNtr7#auhnMFhohhp]ubjÙ)r8#}r9#(hTXlib-version-infor:#hUj-#h`hahbjÜhd}r;#(jÑjÒhi]hh]hf]hg]hl]uhnMFhohhp]r<#hyXlib-version-infor=#…r>#}r?#(hTUh`NhnNhohhUj8#ubaubjâ)r@#}rA#(hTj[hUj-#h`hahbjåhd}rB#(jÑjÒhi]hh]hf]hg]hl]uhnMFhohhp]rC#hyX: rD#…rE#}rF#(hTUh`NhnNhohhUj@#ubaubja)rG#}rH#(hTXcurrent:revision:agehUj-#h`hahbjdhd}rI#(jÑjÒhi]hh]hf]hg]hl]uhnMFhohhp]rJ#hyXcurrent:revision:agerK#…rL#}rM#(hTUh`NhnNhohhUjG#ubaubeubjê)rN#}rO#(hTUhUj(#h`hahbjíhd}rP#(hf]hg]hh]hi]hl]uhnMFhohhp]rQ#(h})rR#}rS#(hTX+This field is currently only used on Linux.rT#hUjN#h`hahbhhd}rU#(hf]hg]hh]hi]hl]uhnM)hohhp]rV#hyX+This field is currently only used on Linux.rW#…rX#}rY#(hTjT#h`NhnNhohhUjR#ubaubh})rZ#}r[#(hTX This field specifies a Libtool-style version-info field that sets an appropriate ABI version for the foreign library. Note that the three numbers specified in this field do not directly specify the actual ABI version: ``6:3:2`` results in library version ``4.2.3``.hUjN#h`hahbhhd}r\#(hf]hg]hh]hi]hl]uhnM+hohhp]r]#(hyXÚThis field specifies a Libtool-style version-info field that sets an appropriate ABI version for the foreign library. Note that the three numbers specified in this field do not directly specify the actual ABI version: r^#…r_#}r`#(hTXÚThis field specifies a Libtool-style version-info field that sets an appropriate ABI version for the foreign library. Note that the three numbers specified in this field do not directly specify the actual ABI version: h`NhnNhohhUjZ#ubhß)ra#}rb#(hTX ``6:3:2``hd}rc#(hf]hg]hh]hi]hl]uhUjZ#hp]rd#hyX6:3:2re#…rf#}rg#(hTUhUja#ubahbhçubhyX results in library version rh#…ri#}rj#(hTX results in library version h`NhnNhohhUjZ#ubhß)rk#}rl#(hTX ``4.2.3``hd}rm#(hf]hg]hh]hi]hl]uhUjZ#hp]rn#hyX4.2.3ro#…rp#}rq#(hTUhUjk#ubahbhçubhyX.…rr#}rs#(hTX.h`NhnNhohhUjZ#ubeubh})rt#}ru#(hTXRWith this field set, the SONAME of the library is set, and symlinks are installed.rv#hUjN#h`hahbhhd}rw#(hf]hg]hh]hi]hl]uhnM0hohhp]rx#hyXRWith this field set, the SONAME of the library is set, and symlinks are installed.ry#…rz#}r{#(hTjv#h`NhnNhohhUjt#ubaubh})r|#}r}#(hTXVHow you should bump this field on an ABI change depends on the breakage you introduce:r~#hUjN#h`hahbhhd}r#(hf]hg]hh]hi]hl]uhnM3hohhp]r€#hyXVHow you should bump this field on an ABI change depends on the breakage you introduce:r#…r‚#}rƒ#(hTj~#h`NhnNhohhUj|#ubaubh‡)r„#}r…#(hTUhUjN#h`hahbhŠhd}r†#(hŒX-hi]hh]hf]hg]hl]uhnM6hohhp]r‡#(hŽ)rˆ#}r‰#(hTXPrograms using the previous version may use the new version as drop-in replacement, and programs using the new version can also work with the previous one. In other words, no recompiling nor relinking is needed. In this case, bump ``revision`` only, don't touch current nor age.hUj„#h`hahbh‘hd}rŠ#(hf]hg]hh]hi]hl]uhnNhohhp]r‹#h})rŒ#}r#(hTXPrograms using the previous version may use the new version as drop-in replacement, and programs using the new version can also work with the previous one. In other words, no recompiling nor relinking is needed. In this case, bump ``revision`` only, don't touch current nor age.hUjˆ#h`hahbhhd}rŽ#(hf]hg]hh]hi]hl]uhnM6hp]r#(hyXçPrograms using the previous version may use the new version as drop-in replacement, and programs using the new version can also work with the previous one. In other words, no recompiling nor relinking is needed. In this case, bump r#…r‘#}r’#(hTXçPrograms using the previous version may use the new version as drop-in replacement, and programs using the new version can also work with the previous one. In other words, no recompiling nor relinking is needed. In this case, bump hUjŒ#ubhß)r“#}r”#(hTX ``revision``hd}r•#(hf]hg]hh]hi]hl]uhUjŒ#hp]r–#hyXrevisionr—#…r˜#}r™#(hTUhUj“#ubahbhçubhyX% only, don’t touch current nor age.rš#…r›#}rœ#(hTX# only, don't touch current nor age.hUjŒ#ubeubaubhŽ)r#}rž#(hTXYPrograms using the previous version may use the new version as drop-in replacement, but programs using the new version may use APIs not present in the previous one. In other words, a program linking against the new version may fail with "unresolved symbols" if linking against the old version at runtime: set revision to 0, bump current and age.hUj„#h`hahbh‘hd}rŸ#(hf]hg]hh]hi]hl]uhnNhohhp]r #h})r¡#}r¢#(hTXYPrograms using the previous version may use the new version as drop-in replacement, but programs using the new version may use APIs not present in the previous one. In other words, a program linking against the new version may fail with "unresolved symbols" if linking against the old version at runtime: set revision to 0, bump current and age.r£#hUj#h`hahbhhd}r¤#(hf]hg]hh]hi]hl]uhnM;hp]r¥#hyX]Programs using the previous version may use the new version as drop-in replacement, but programs using the new version may use APIs not present in the previous one. In other words, a program linking against the new version may fail with “unresolved symbols†if linking against the old version at runtime: set revision to 0, bump current and age.r¦#…r§#}r¨#(hTj£#hUj¡#ubaubaubhŽ)r©#}rª#(hTX„Programs may need to be changed, recompiled, and relinked in order to use the new version. Bump current, set revision and age to 0. hUj„#h`hahbh‘hd}r«#(hf]hg]hh]hi]hl]uhnNhohhp]r¬#h})r­#}r®#(hTXƒPrograms may need to be changed, recompiled, and relinked in order to use the new version. Bump current, set revision and age to 0.r¯#hUj©#h`hahbhhd}r°#(hf]hg]hh]hi]hl]uhnMAhp]r±#hyXƒPrograms may need to be changed, recompiled, and relinked in order to use the new version. Bump current, set revision and age to 0.r²#…r³#}r´#(hTj¯#hUj­#ubaubaubeubh})rµ#}r¶#(hTXBAlso refer to the Libtool documentation on the version-info field.r·#hUjN#h`hahbhhd}r¸#(hf]hg]hh]hi]hl]uhnMEhohhp]r¹#hyXBAlso refer to the Libtool documentation on the version-info field.rº#…r»#}r¼#(hTj·#h`NhnNhohhUjµ#ubaubeubeubj¹)r½#}r¾#(hTUhUj‰!h`hahbj¼hd}r¿#(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÀ#}rÁ#(hTUhUj‰!h`hahbjÁhd}rÂ#(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrÃ#jÇjÃ#uhnNhohhp]rÄ#(jÉ)rÅ#}rÆ#(hTXlib-version-linux: versionhUjÀ#h`hahbjÍhd}rÇ#(hi]rÈ#X%pkg-field-benchmark-lib-version-linuxrÉ#ahh]hf]hg]hl]jщuhnMPhohhp]rÊ#(j¹)rË#}rÌ#(hTUhUjÅ#h`hahbj¼hd}rÍ#(hi]hh]hf]hg]hl]Uentries]rÎ#(j×X0benchmark:lib-version-linux; package.cabal fieldjÉ#UNtrÏ#auhnMPhohhp]ubjÙ)rÐ#}rÑ#(hTXlib-version-linuxrÒ#hUjÅ#h`hahbjÜhd}rÓ#(jÑjÒhi]hh]hf]hg]hl]uhnMPhohhp]rÔ#hyXlib-version-linuxrÕ#…rÖ#}r×#(hTUh`NhnNhohhUjÐ#ubaubjâ)rØ#}rÙ#(hTj[hUjÅ#h`hahbjåhd}rÚ#(jÑjÒhi]hh]hf]hg]hl]uhnMPhohhp]rÛ#hyX: rÜ#…rÝ#}rÞ#(hTUh`NhnNhohhUjØ#ubaubja)rß#}rà#(hTXversionhUjÅ#h`hahbjdhd}rá#(jÑjÒhi]hh]hf]hg]hl]uhnMPhohhp]râ#hyXversionrã#…rä#}rå#(hTUh`NhnNhohhUjß#ubaubeubjê)ræ#}rç#(hTUhUjÀ#h`hahbjíhd}rè#(hf]hg]hh]hi]hl]uhnMPhohhp]ré#(h})rê#}rë#(hTX!This field is only used on Linux.rì#hUjæ#h`hahbhhd}rí#(hf]hg]hh]hi]hl]uhnMIhohhp]rî#hyX!This field is only used on Linux.rï#…rð#}rñ#(hTjì#h`NhnNhohhUjê#ubaubh})rò#}ró#(hTXSpecifies the library ABI version directly for foreign libraries built on Linux: so specifying ``4.2.3`` causes a library ``libfoo.so.4.2.3`` to be built with SONAME ``libfoo.so.4``, and appropriate symlinks ``libfoo.so.4`` and ``libfoo.so`` to be installed.hUjæ#h`hahbhhd}rô#(hf]hg]hh]hi]hl]uhnMKhohhp]rõ#(hyX_Specifies the library ABI version directly for foreign libraries built on Linux: so specifying rö#…r÷#}rø#(hTX_Specifies the library ABI version directly for foreign libraries built on Linux: so specifying h`NhnNhohhUjò#ubhß)rù#}rú#(hTX ``4.2.3``hd}rû#(hf]hg]hh]hi]hl]uhUjò#hp]rü#hyX4.2.3rý#…rþ#}rÿ#(hTUhUjù#ubahbhçubhyX causes a library r$…r$}r$(hTX causes a library h`NhnNhohhUjò#ubhß)r$}r$(hTX``libfoo.so.4.2.3``hd}r$(hf]hg]hh]hi]hl]uhUjò#hp]r$hyXlibfoo.so.4.2.3r$…r$}r $(hTUhUj$ubahbhçubhyX to be built with SONAME r $…r $}r $(hTX to be built with SONAME h`NhnNhohhUjò#ubhß)r $}r$(hTX``libfoo.so.4``hd}r$(hf]hg]hh]hi]hl]uhUjò#hp]r$hyX libfoo.so.4r$…r$}r$(hTUhUj $ubahbhçubhyX, and appropriate symlinks r$…r$}r$(hTX, and appropriate symlinks h`NhnNhohhUjò#ubhß)r$}r$(hTX``libfoo.so.4``hd}r$(hf]hg]hh]hi]hl]uhUjò#hp]r$hyX libfoo.so.4r$…r$}r$(hTUhUj$ubahbhçubhyX and r$…r$}r $(hTX and h`NhnNhohhUjò#ubhß)r!$}r"$(hTX ``libfoo.so``hd}r#$(hf]hg]hh]hi]hl]uhUjò#hp]r$$hyX libfoo.sor%$…r&$}r'$(hTUhUj!$ubahbhçubhyX to be installed.r($…r)$}r*$(hTX to be installed.h`NhnNhohhUjò#ubeubeubeubh})r+$}r,$(hTXØNote that typically foreign libraries should export a way to initialize and shutdown the Haskell runtime. In the example above, this is done by the ``csrc/MyForeignLibWrapper.c`` file, which might look something likehUj‰!h`hahbhhd}r-$(hf]hg]hh]hi]hl]uhnMQhohhp]r.$(hyX”Note that typically foreign libraries should export a way to initialize and shutdown the Haskell runtime. In the example above, this is done by the r/$…r0$}r1$(hTX”Note that typically foreign libraries should export a way to initialize and shutdown the Haskell runtime. In the example above, this is done by the h`NhnNhohhUj+$ubhß)r2$}r3$(hTX``csrc/MyForeignLibWrapper.c``hd}r4$(hf]hg]hh]hi]hl]uhUj+$hp]r5$hyXcsrc/MyForeignLibWrapper.cr6$…r7$}r8$(hTUhUj2$ubahbhçubhyX& file, which might look something liker9$…r:$}r;$(hTX& file, which might look something likeh`NhnNhohhUj+$ubeubjÌ)r<$}r=$(hTXn#include #include "HsFFI.h" HsBool myForeignLibInit(void){ int argc = 2; char *argv[] = { "+RTS", "-A32m", NULL }; char **pargv = argv; // Initialize Haskell runtime hs_init(&argc, &pargv); // do any other initialization here and // return false if there was a problem return HS_BOOL_TRUE; } void myForeignLibExit(void){ hs_exit(); }hUj‰!h`hahbjÏhd}r>$(j‰jXcjÑjÒhi]hh]hf]j}hg]hl]uhnMUhohhp]r?$hyXn#include #include "HsFFI.h" HsBool myForeignLibInit(void){ int argc = 2; char *argv[] = { "+RTS", "-A32m", NULL }; char **pargv = argv; // Initialize Haskell runtime hs_init(&argc, &pargv); // do any other initialization here and // return false if there was a problem return HS_BOOL_TRUE; } void myForeignLibExit(void){ hs_exit(); }r@$…rA$}rB$(hTUhUj<$ubaubh})rC$}rD$(hTXWith modern ghc regular libraries are installed in directories that contain package keys. This isn't usually a problem because the package gets registered in ghc's package DB and so we can figure out what the location of the library is. Foreign libraries however don't get registered, which means that we'd have to have a way of finding out where a platform library got installed (other than by searching the ``lib/`` directory). Instead, we install foreign libraries in ``~/.cabal/lib``, much like we install executables in ``~/.cabal/bin``.hUj‰!h`hahbhhd}rE$(hf]hg]hh]hi]hl]uhnMkhohhp]rF$(hyX¡With modern ghc regular libraries are installed in directories that contain package keys. This isn’t usually a problem because the package gets registered in ghc’s package DB and so we can figure out what the location of the library is. Foreign libraries however don’t get registered, which means that we’d have to have a way of finding out where a platform library got installed (other than by searching the rG$…rH$}rI$(hTX™With modern ghc regular libraries are installed in directories that contain package keys. This isn't usually a problem because the package gets registered in ghc's package DB and so we can figure out what the location of the library is. Foreign libraries however don't get registered, which means that we'd have to have a way of finding out where a platform library got installed (other than by searching the h`NhnNhohhUjC$ubhß)rJ$}rK$(hTX``lib/``hd}rL$(hf]hg]hh]hi]hl]uhUjC$hp]rM$hyXlib/rN$…rO$}rP$(hTUhUjJ$ubahbhçubhyX6 directory). Instead, we install foreign libraries in rQ$…rR$}rS$(hTX6 directory). Instead, we install foreign libraries in h`NhnNhohhUjC$ubhß)rT$}rU$(hTX``~/.cabal/lib``hd}rV$(hf]hg]hh]hi]hl]uhUjC$hp]rW$hyX ~/.cabal/librX$…rY$}rZ$(hTUhUjT$ubahbhçubhyX&, much like we install executables in r[$…r\$}r]$(hTX&, much like we install executables in h`NhnNhohhUjC$ubhß)r^$}r_$(hTX``~/.cabal/bin``hd}r`$(hf]hg]hh]hi]hl]uhUjC$hp]ra$hyX ~/.cabal/binrb$…rc$}rd$(hTUhUj^$ubahbhçubhyX.…re$}rf$(hTX.h`NhnNhohhUjC$ubeubeubhV)rg$}rh$(hTUhYKhUh\h`hahbhchd}ri$(hf]hg]hh]hi]rj$j(ahl]rk$h@auhnMthohhp]rl$(hr)rm$}rn$(hTXBuild informationro$hUjg$h`hahbhvhd}rp$(hf]hg]hh]hi]hl]uhnMthohhp]rq$hyXBuild informationrr$…rs$}rt$(hTjo$h`NhnNhohhUjm$ubaubh})ru$}rv$(hTXGThe following fields may be optionally present in a library, executable, test suite or benchmark section, and give information for the building of the corresponding library or executable. See also the sections on `system-dependent parameters`_ and `configurations`_ for a way to supply system-dependent values for these fields.hUjg$h`hahbhhd}rw$(hf]hg]hh]hi]hl]uhnMwhohhp]rx$(hyXÕThe following fields may be optionally present in a library, executable, test suite or benchmark section, and give information for the building of the corresponding library or executable. See also the sections on ry$…rz$}r{$(hTXÕThe following fields may be optionally present in a library, executable, test suite or benchmark section, and give information for the building of the corresponding library or executable. See also the sections on h`NhnNhohhUju$ubj?)r|$}r}$(hTX`system-dependent parameters`_jBKhUju$hbjChd}r~$(UnameXsystem-dependent parametershi]hh]hf]hg]hl]jEjuhp]r$hyXsystem-dependent parametersr€$…r$}r‚$(hTUhUj|$ubaubhyX and rƒ$…r„$}r…$(hTX and h`NhnNhohhUju$ubj?)r†$}r‡$(hTX`configurations`_jBKhUju$hbjChd}rˆ$(UnameXconfigurationshi]hh]hf]hg]hl]jEjœuhp]r‰$hyXconfigurationsrŠ$…r‹$}rŒ$(hTUhUj†$ubaubhyX> for a way to supply system-dependent values for these fields.r$…rŽ$}r$(hTX> for a way to supply system-dependent values for these fields.h`NhnNhohhUju$ubeubj¹)r$}r‘$(hTUhUjg$h`Nhbj¼hd}r’$(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r“$}r”$(hTUhUjg$h`NhbjÁhd}r•$(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr–$jÇj–$uhnNhohhp]r—$(jÉ)r˜$}r™$(hTXbuild-depends: package listhUj“$h`hahbjÍhd}rš$(hi]r›$Xpkg-field-build-dependsrœ$ahh]hf]hg]hl]jщuhnM¼hohhp]r$(j¹)rž$}rŸ$(hTUhUj˜$h`hahbj¼hd}r $(hi]hh]hf]hg]hl]Uentries]r¡$(j×X"build-depends; package.cabal fieldjœ$UNtr¢$auhnM¼hohhp]ubjÙ)r£$}r¤$(hTX build-dependsr¥$hUj˜$h`hahbjÜhd}r¦$(jÑjÒhi]hh]hf]hg]hl]uhnM¼hohhp]r§$hyX build-dependsr¨$…r©$}rª$(hTUh`NhnNhohhUj£$ubaubjâ)r«$}r¬$(hTj[hUj˜$h`hahbjåhd}r­$(jÑjÒhi]hh]hf]hg]hl]uhnM¼hohhp]r®$hyX: r¯$…r°$}r±$(hTUh`NhnNhohhUj«$ubaubja)r²$}r³$(hTX package listhUj˜$h`hahbjdhd}r´$(jÑjÒhi]hh]hf]hg]hl]uhnM¼hohhp]rµ$hyX package listr¶$…r·$}r¸$(hTUh`NhnNhohhUj²$ubaubeubjê)r¹$}rº$(hTUhUj“$h`hahbjíhd}r»$(hf]hg]hh]hi]hl]uhnM¼hohhp]r¼$(h})r½$}r¾$(hTXeA list of packages needed to build this one. Each package can be annotated with a version constraint.r¿$hUj¹$h`hahbhhd}rÀ$(hf]hg]hh]hi]hl]uhnMhohhp]rÁ$hyXeA list of packages needed to build this one. Each package can be annotated with a version constraint.rÂ$…rÃ$}rÄ$(hTj¿$h`NhnNhohhUj½$ubaubh})rÅ$}rÆ$(hTXêVersion constraints use the operators ``==, >=, >, <, <=`` and a version number. Multiple constraints can be combined using ``&&`` or ``||``. If no version constraint is specified, any version is assumed to be acceptable. For example:hUj¹$h`hahbhhd}rÇ$(hf]hg]hh]hi]hl]uhnM‚hohhp]rÈ$(hyX&Version constraints use the operators rÉ$…rÊ$}rË$(hTX&Version constraints use the operators h`NhnNhohhUjÅ$ubhß)rÌ$}rÍ$(hTX``==, >=, >, <, <=``hd}rÎ$(hf]hg]hh]hi]hl]uhUjÅ$hp]rÏ$hyX==, >=, >, <, <=rÐ$…rÑ$}rÒ$(hTUhUjÌ$ubahbhçubhyXB and a version number. Multiple constraints can be combined using rÓ$…rÔ$}rÕ$(hTXB and a version number. Multiple constraints can be combined using h`NhnNhohhUjÅ$ubhß)rÖ$}r×$(hTX``&&``hd}rØ$(hf]hg]hh]hi]hl]uhUjÅ$hp]rÙ$hyX&&rÚ$…rÛ$}rÜ$(hTUhUjÖ$ubahbhçubhyX or rÝ$…rÞ$}rß$(hTX or h`NhnNhohhUjÅ$ubhß)rà$}rá$(hTX``||``hd}râ$(hf]hg]hh]hi]hl]uhUjÅ$hp]rã$hyX||rä$…rå$}ræ$(hTUhUjà$ubahbhçubhyX^. If no version constraint is specified, any version is assumed to be acceptable. For example:rç$…rè$}ré$(hTX^. If no version constraint is specified, any version is assumed to be acceptable. For example:h`NhnNhohhUjÅ$ubeubjÌ)rê$}rë$(hTXJlibrary build-depends: base >= 2, foo >= 1.2.3 && < 1.3, barhUj¹$h`hahbjÏhd}rì$(jÑjÒhi]hh]hf]hg]hl]uhnM‰hohhp]rí$hyXJlibrary build-depends: base >= 2, foo >= 1.2.3 && < 1.3, barrî$…rï$}rð$(hTUhUjê$ubaubh})rñ$}rò$(hTX¨Dependencies like ``foo >= 1.2.3 && < 1.3`` turn out to be very common because it is recommended practise for package versions to correspond to API versions (see PVP_).hUj¹$h`hahbhhd}ró$(hf]hg]hh]hi]hl]uhnMhohhp]rô$(hyXDependencies like rõ$…rö$}r÷$(hTXDependencies like h`NhnNhohhUjñ$ubhß)rø$}rù$(hTX``foo >= 1.2.3 && < 1.3``hd}rú$(hf]hg]hh]hi]hl]uhUjñ$hp]rû$hyXfoo >= 1.2.3 && < 1.3rü$…rý$}rþ$(hTUhUjø$ubahbhçubhyXw turn out to be very common because it is recommended practise for package versions to correspond to API versions (see rÿ$…r%}r%(hTXw turn out to be very common because it is recommended practise for package versions to correspond to API versions (see h`NhnNhohhUjñ$ubj?)r%}r%(hTXPVP_jBKhUjñ$hbjChd}r%(UnameXPVPj~jÖ hi]hh]hf]hg]hl]uhp]r%hyXPVPr%…r%}r%(hTUhUj%ubaubhyX).r %…r %}r %(hTX).h`NhnNhohhUjñ$ubeubh})r %}r %(hTXLSince Cabal 1.6, there is a special wildcard syntax to help with such rangesr%hUj¹$h`hahbhhd}r%(hf]hg]hh]hi]hl]uhnM“hohhp]r%hyXLSince Cabal 1.6, there is a special wildcard syntax to help with such rangesr%…r%}r%(hTj%h`NhnNhohhUj %ubaubjÌ)r%}r%(hTXbuild-depends: foo ==1.2.*hUj¹$h`hahbjÏhd}r%(jÑjÒhi]hh]hf]hg]hl]uhnM˜hohhp]r%hyXbuild-depends: foo ==1.2.*r%…r%}r%(hTUhUj%ubaubh})r%}r%(hTXPIt is only syntactic sugar. It is exactly equivalent to ``foo >= 1.2 && < 1.3``.hUj¹$h`hahbhhd}r%(hf]hg]hh]hi]hl]uhnMšhohhp]r%(hyX8It is only syntactic sugar. It is exactly equivalent to r%…r %}r!%(hTX8It is only syntactic sugar. It is exactly equivalent to h`NhnNhohhUj%ubhß)r"%}r#%(hTX``foo >= 1.2 && < 1.3``hd}r$%(hf]hg]hh]hi]hl]uhUj%hp]r%%hyXfoo >= 1.2 && < 1.3r&%…r'%}r(%(hTUhUj"%ubahbhçubhyX.…r)%}r*%(hTX.h`NhnNhohhUj%ubeubh})r+%}r,%(hTXêStarting with Cabal 2.0, there's a new syntactic sugar to support PVP_-style major upper bounds conveniently, and is inspired by similiar syntactic sugar found in other language ecosystems where it's often called the "Caret" operator:hUj¹$h`hahbhhd}r-%(hf]hg]hh]hi]hl]uhnMhohhp]r.%(hyXDStarting with Cabal 2.0, there’s a new syntactic sugar to support r/%…r0%}r1%(hTXBStarting with Cabal 2.0, there's a new syntactic sugar to support h`NhnNhohhUj+%ubj?)r2%}r3%(hTXPVP_jBKhUj+%hbjChd}r4%(UnameXPVPj~jÖ hi]hh]hf]hg]hl]uhp]r5%hyXPVPr6%…r7%}r8%(hTUhUj2%ubaubhyXª-style major upper bounds conveniently, and is inspired by similiar syntactic sugar found in other language ecosystems where it’s often called the “Caret†operator:r9%…r:%}r;%(hTX¤-style major upper bounds conveniently, and is inspired by similiar syntactic sugar found in other language ecosystems where it's often called the "Caret" operator:h`NhnNhohhUj+%ubeubjÌ)r<%}r=%(hTX8build-depends: foo ^>= 1.2.3.4, bar ^>= 1hUj¹$h`hahbjÏhd}r>%(jÑjÒhi]hh]hf]hg]hl]uhnM¥hohhp]r?%hyX8build-depends: foo ^>= 1.2.3.4, bar ^>= 1r@%…rA%}rB%(hTUhUj<%ubaubh})rC%}rD%(hTX.The declaration above is exactly equivalent torE%hUj¹$h`hahbhhd}rF%(hf]hg]hh]hi]hl]uhnM¨hohhp]rG%hyX.The declaration above is exactly equivalent torH%…rI%}rJ%(hTjE%h`NhnNhohhUjC%ubaubjÌ)rK%}rL%(hTXHbuild-depends: foo >= 1.2.3.4 && < 1.3, bar >= 1 && < 1.1hUj¹$h`hahbjÏhd}rM%(jÑjÒhi]hh]hf]hg]hl]uhnM¬hohhp]rN%hyXHbuild-depends: foo >= 1.2.3.4 && < 1.3, bar >= 1 && < 1.1rO%…rP%}rQ%(hTUhUjK%ubaubhë)rR%}rS%(hTX=Prior to Cabal 1.8, ``build-depends`` specified in each section were global to all sections. This was unintentional, but some packages were written to depend on it, so if you need your :pkg-field:`build-depends` to be local to each section, you must specify at least ``Cabal-Version: >= 1.8`` in your ``.cabal`` file.hUj¹$h`hahbhîhd}rT%(hf]hg]hh]hi]hl]uhnNhohhp]rU%h})rV%}rW%(hTX=Prior to Cabal 1.8, ``build-depends`` specified in each section were global to all sections. This was unintentional, but some packages were written to depend on it, so if you need your :pkg-field:`build-depends` to be local to each section, you must specify at least ``Cabal-Version: >= 1.8`` in your ``.cabal`` file.hUjR%h`hahbhhd}rX%(hf]hg]hh]hi]hl]uhnM±hp]rY%(hyXPrior to Cabal 1.8, rZ%…r[%}r\%(hTXPrior to Cabal 1.8, hUjV%ubhß)r]%}r^%(hTX``build-depends``hd}r_%(hf]hg]hh]hi]hl]uhUjV%hp]r`%hyX build-dependsra%…rb%}rc%(hTUhUj]%ubahbhçubhyX” specified in each section were global to all sections. This was unintentional, but some packages were written to depend on it, so if you need your rd%…re%}rf%(hTX” specified in each section were global to all sections. This was unintentional, but some packages were written to depend on it, so if you need your hUjV%ubjk)rg%}rh%(hTX:pkg-field:`build-depends`ri%hUjV%h`hahbjohd}rj%(UreftypeX pkg-fieldjqˆjrX build-dependsU refdomainXcabalrk%hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnM±hp]rl%hß)rm%}rn%(hTji%hd}ro%(hf]hg]rp%(j|jk%Xcabal-pkg-fieldrq%ehh]hi]hl]uhUjg%hp]rr%hyX build-dependsrs%…rt%}ru%(hTUhUjm%ubahbhçubaubhyX8 to be local to each section, you must specify at least rv%…rw%}rx%(hTX8 to be local to each section, you must specify at least hUjV%ubhß)ry%}rz%(hTX``Cabal-Version: >= 1.8``hd}r{%(hf]hg]hh]hi]hl]uhUjV%hp]r|%hyXCabal-Version: >= 1.8r}%…r~%}r%(hTUhUjy%ubahbhçubhyX in your r€%…r%}r‚%(hTX in your hUjV%ubhß)rƒ%}r„%(hTX ``.cabal``hd}r…%(hf]hg]hh]hi]hl]uhUjV%hp]r†%hyX.cabalr‡%…rˆ%}r‰%(hTUhUjƒ%ubahbhçubhyX file.rŠ%…r‹%}rŒ%(hTX file.hUjV%ubeubaubhë)r%}rŽ%(hTX›Cabal 1.20 experimentally supported module thinning and renaming in ``build-depends``; however, this support has since been removed and should not be used.hUj¹$h`hahbhîhd}r%(hf]hg]hh]hi]hl]uhnNhohhp]r%h})r‘%}r’%(hTX›Cabal 1.20 experimentally supported module thinning and renaming in ``build-depends``; however, this support has since been removed and should not be used.hUj%h`hahbhhd}r“%(hf]hg]hh]hi]hl]uhnM¹hp]r”%(hyXDCabal 1.20 experimentally supported module thinning and renaming in r•%…r–%}r—%(hTXDCabal 1.20 experimentally supported module thinning and renaming in hUj‘%ubhß)r˜%}r™%(hTX``build-depends``hd}rš%(hf]hg]hh]hi]hl]uhUj‘%hp]r›%hyX build-dependsrœ%…r%}rž%(hTUhUj˜%ubahbhçubhyXF; however, this support has since been removed and should not be used.rŸ%…r %}r¡%(hTXF; however, this support has since been removed and should not be used.hUj‘%ubeubaubeubeubj¹)r¢%}r£%(hTUhUjg$h`Nhbj¼hd}r¤%(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r¥%}r¦%(hTUhUjg$h`NhbjÁhd}r§%(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr¨%jÇj¨%uhnNhohhp]r©%(jÉ)rª%}r«%(hTXother-modules: identifier listhUj¥%h`hahbjÍhd}r¬%(hi]r­%Xpkg-field-other-modulesr®%ahh]hf]hg]hl]jщuhnMÉhohhp]r¯%(j¹)r°%}r±%(hTUhUjª%h`hahbj¼hd}r²%(hi]hh]hf]hg]hl]Uentries]r³%(j×X"other-modules; package.cabal fieldj®%UNtr´%auhnMÉhohhp]ubjÙ)rµ%}r¶%(hTX other-modulesr·%hUjª%h`hahbjÜhd}r¸%(jÑjÒhi]hh]hf]hg]hl]uhnMÉhohhp]r¹%hyX other-modulesrº%…r»%}r¼%(hTUh`NhnNhohhUjµ%ubaubjâ)r½%}r¾%(hTj[hUjª%h`hahbjåhd}r¿%(jÑjÒhi]hh]hf]hg]hl]uhnMÉhohhp]rÀ%hyX: rÁ%…rÂ%}rÃ%(hTUh`NhnNhohhUj½%ubaubja)rÄ%}rÅ%(hTXidentifier listhUjª%h`hahbjdhd}rÆ%(jÑjÒhi]hh]hf]hg]hl]uhnMÉhohhp]rÇ%hyXidentifier listrÈ%…rÉ%}rÊ%(hTUh`NhnNhohhUjÄ%ubaubeubjê)rË%}rÌ%(hTUhUj¥%h`hahbjíhd}rÍ%(hf]hg]hh]hi]hl]uhnMÉhohhp]rÎ%(h})rÏ%}rÐ%(hTX÷A list of modules used by the component but not exposed to users. For a library component, these would be hidden modules of the library. For an executable, these would be auxiliary modules to be linked with the file named in the ``main-is`` field.hUjË%h`hahbhhd}rÑ%(hf]hg]hh]hi]hl]uhnM¿hohhp]rÒ%(hyXåA list of modules used by the component but not exposed to users. For a library component, these would be hidden modules of the library. For an executable, these would be auxiliary modules to be linked with the file named in the rÓ%…rÔ%}rÕ%(hTXåA list of modules used by the component but not exposed to users. For a library component, these would be hidden modules of the library. For an executable, these would be auxiliary modules to be linked with the file named in the h`NhnNhohhUjÏ%ubhß)rÖ%}r×%(hTX ``main-is``hd}rØ%(hf]hg]hh]hi]hl]uhUjÏ%hp]rÙ%hyXmain-isrÚ%…rÛ%}rÜ%(hTUhUjÖ%ubahbhçubhyX field.rÝ%…rÞ%}rß%(hTX field.h`NhnNhohhUjÏ%ubeubhë)rà%}rá%(hTX¢Every module in the package *must* be listed in one of :pkg-field:`other-modules`, :pkg-field:`library:exposed-modules` or :pkg-field:`executable:main-is` fields.hUjË%h`hahbhîhd}râ%(hf]hg]hh]hi]hl]uhnNhohhp]rã%h})rä%}rå%(hTX¢Every module in the package *must* be listed in one of :pkg-field:`other-modules`, :pkg-field:`library:exposed-modules` or :pkg-field:`executable:main-is` fields.hUjà%h`hahbhhd}ræ%(hf]hg]hh]hi]hl]uhnMÆhp]rç%(hyXEvery module in the package rè%…ré%}rê%(hTXEvery module in the package hUjä%ubh¿)rë%}rì%(hTX*must*hd}rí%(hf]hg]hh]hi]hl]uhUjä%hp]rî%hyXmustrï%…rð%}rñ%(hTUhUjë%ubahbhÇubhyX be listed in one of rò%…ró%}rô%(hTX be listed in one of hUjä%ubjk)rõ%}rö%(hTX:pkg-field:`other-modules`r÷%hUjä%h`hahbjohd}rø%(UreftypeX pkg-fieldjqˆjrX other-modulesU refdomainXcabalrù%hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMÆhp]rú%hß)rû%}rü%(hTj÷%hd}rý%(hf]hg]rþ%(j|jù%Xcabal-pkg-fieldrÿ%ehh]hi]hl]uhUjõ%hp]r&hyX other-modulesr&…r&}r&(hTUhUjû%ubahbhçubaubhyX, r&…r&}r&(hTX, hUjä%ubjk)r&}r&(hTX$:pkg-field:`library:exposed-modules`r &hUjä%h`hahbjohd}r &(UreftypeX pkg-fieldjqˆjrXexposed-modulesU refdomainXcabalr &hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹XlibraryuhnMÆhp]r &hß)r &}r&(hTj &hd}r&(hf]hg]r&(j|j &Xcabal-pkg-fieldr&ehh]hi]hl]uhUj&hp]r&hyXlibrary:exposed-modulesr&…r&}r&(hTUhUj &ubahbhçubaubhyX or r&…r&}r&(hTX or hUjä%ubjk)r&}r&(hTX:pkg-field:`executable:main-is`r&hUjä%h`hahbjohd}r&(UreftypeX pkg-fieldjqˆjrXmain-isU refdomainXcabalr&hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹X executableuhnMÆhp]r&hß)r&}r &(hTj&hd}r!&(hf]hg]r"&(j|j&Xcabal-pkg-fieldr#&ehh]hi]hl]uhUj&hp]r$&hyXexecutable:main-isr%&…r&&}r'&(hTUhUj&ubahbhçubaubhyX fields.r(&…r)&}r*&(hTX fields.hUjä%ubeubaubeubeubj¹)r+&}r,&(hTUhUjg$h`hahbj¼hd}r-&(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r.&}r/&(hTUhUjg$h`hahbjÁhd}r0&(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr1&jÇj1&uhnNhohhp]r2&(jÉ)r3&}r4&(hTXhs-source-dirs: directory listhUj.&h`hahbjÍhd}r5&(hi]r6&Xpkg-field-hs-source-dirsr7&ahh]hf]hg]hl]jщuhnMÒhohhp]r8&(j¹)r9&}r:&(hTUhUj3&h`hahbj¼hd}r;&(hi]hh]hf]hg]hl]Uentries]r<&(j×X#hs-source-dirs; package.cabal fieldj7&UNtr=&auhnMÒhohhp]ubjÙ)r>&}r?&(hTXhs-source-dirsr@&hUj3&h`hahbjÜhd}rA&(jÑjÒhi]hh]hf]hg]hl]uhnMÒhohhp]rB&hyXhs-source-dirsrC&…rD&}rE&(hTUh`NhnNhohhUj>&ubaubjâ)rF&}rG&(hTj[hUj3&h`hahbjåhd}rH&(jÑjÒhi]hh]hf]hg]hl]uhnMÒhohhp]rI&hyX: rJ&…rK&}rL&(hTUh`NhnNhohhUjF&ubaubja)rM&}rN&(hTXdirectory listhUj3&h`hahbjdhd}rO&(jÑjÒhi]hh]hf]hg]hl]uhnMÒhohhp]rP&hyXdirectory listrQ&…rR&}rS&(hTUh`NhnNhohhUjM&ubaubeubjê)rT&}rU&(hTUhUj.&h`hahbjíhd}rV&(hf]hg]hh]hi]hl]uhnMÒhohhp]rW&(jð)rX&}rY&(hTUhUjT&h`hahbjóhd}rZ&(hf]hg]hh]hi]hl]uhnNhohhp]r[&jö)r\&}r]&(hTUhd}r^&(hf]hg]hh]hi]hl]uhUjX&hp]r_&(jü)r`&}ra&(hTX Default valuehUj\&h`hahbjhd}rb&(hf]hg]hh]hi]hl]uhnKhp]rc&hyX Default valuerd&…re&}rf&(hTUhUj`&ubaubj)rg&}rh&(hTUhd}ri&(hf]hg]hh]hi]hl]uhUj\&hp]rj&h})rk&}rl&(hTX.hd}rm&(hf]hg]hh]hi]hl]uhUjg&hp]rn&hß)ro&}rp&(hTX``.``rq&hUjk&h`hahbhçhd}rr&(hf]hg]hh]hi]hl]uhnNhohhp]rs&hyX.…rt&}ru&(hTUh`NhnNhohhUjo&ubaubahbhubahbjubehbjùubaubh})rv&}rw&(hTX*Root directories for the module hierarchy.rx&hUjT&h`hahbhhd}ry&(hf]hg]hh]hi]hl]uhnMÎhohhp]rz&hyX*Root directories for the module hierarchy.r{&…r|&}r}&(hTjx&h`NhnNhohhUjv&ubaubh})r~&}r&(hTXRFor backwards compatibility, the old variant ``hs-source-dir`` is also recognized.hUjT&h`hahbhhd}r€&(hf]hg]hh]hi]hl]uhnMÐhohhp]r&(hyX-For backwards compatibility, the old variant r‚&…rƒ&}r„&(hTX-For backwards compatibility, the old variant h`NhnNhohhUj~&ubhß)r…&}r†&(hTX``hs-source-dir``hd}r‡&(hf]hg]hh]hi]hl]uhUj~&hp]rˆ&hyX hs-source-dirr‰&…rŠ&}r‹&(hTUhUj…&ubahbhçubhyX is also recognized.rŒ&…r&}rŽ&(hTX is also recognized.h`NhnNhohhUj~&ubeubeubeubj¹)r&}r&(hTUhUjg$h`hahbj¼hd}r‘&(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r’&}r“&(hTUhUjg$h`hahbjÁhd}r”&(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr•&jÇj•&uhnNhohhp]r–&(jÉ)r—&}r˜&(hTX#default-extensions: identifier listhUj’&h`hahbjÍhd}r™&(hi]rš&Xpkg-field-default-extensionsr›&ahh]hf]hg]hl]jщuhnMÛhohhp]rœ&(j¹)r&}rž&(hTUhUj—&h`hahbj¼hd}rŸ&(hi]hh]hf]hg]hl]Uentries]r &(j×X'default-extensions; package.cabal fieldj›&UNtr¡&auhnMÛhohhp]ubjÙ)r¢&}r£&(hTXdefault-extensionsr¤&hUj—&h`hahbjÜhd}r¥&(jÑjÒhi]hh]hf]hg]hl]uhnMÛhohhp]r¦&hyXdefault-extensionsr§&…r¨&}r©&(hTUh`NhnNhohhUj¢&ubaubjâ)rª&}r«&(hTj[hUj—&h`hahbjåhd}r¬&(jÑjÒhi]hh]hf]hg]hl]uhnMÛhohhp]r­&hyX: r®&…r¯&}r°&(hTUh`NhnNhohhUjª&ubaubja)r±&}r²&(hTXidentifier listhUj—&h`hahbjdhd}r³&(jÑjÒhi]hh]hf]hg]hl]uhnMÛhohhp]r´&hyXidentifier listrµ&…r¶&}r·&(hTUh`NhnNhohhUj±&ubaubeubjê)r¸&}r¹&(hTUhUj’&h`hahbjíhd}rº&(hf]hg]hh]hi]hl]uhnMÛhohhp]r»&h})r¼&}r½&(hTXsA list of Haskell extensions used by every module. These determine corresponding compiler options enabled for all files. Extension names are the constructors of the `Extension <../release/cabal-latest/doc/API/Cabal/Language-Haskell-Extension.html#t:Extension>`__ type. For example, ``CPP`` specifies that Haskell source files are to be preprocessed with a C preprocessor.hUj¸&h`hahbhhd}r¾&(hf]hg]hh]hi]hl]uhnMÕhohhp]r¿&(hyX¥A list of Haskell extensions used by every module. These determine corresponding compiler options enabled for all files. Extension names are the constructors of the rÀ&…rÁ&}rÂ&(hTX¥A list of Haskell extensions used by every module. These determine corresponding compiler options enabled for all files. Extension names are the constructors of the h`NhnNhohhUj¼&ubj?)rÃ&}rÄ&(hTXa`Extension <../release/cabal-latest/doc/API/Cabal/Language-Haskell-Extension.html#t:Extension>`__hd}rÅ&(UnameX Extensionj~XQ../release/cabal-latest/doc/API/Cabal/Language-Haskell-Extension.html#t:Extensionhi]hh]hf]hg]hl]uhUj¼&hp]rÆ&hyX ExtensionrÇ&…rÈ&}rÉ&(hTUhUjÃ&ubahbjCubhyX type. For example, rÊ&…rË&}rÌ&(hTX type. For example, h`NhnNhohhUj¼&ubhß)rÍ&}rÎ&(hTX``CPP``hd}rÏ&(hf]hg]hh]hi]hl]uhUj¼&hp]rÐ&hyXCPPrÑ&…rÒ&}rÓ&(hTUhUjÍ&ubahbhçubhyXR specifies that Haskell source files are to be preprocessed with a C preprocessor.rÔ&…rÕ&}rÖ&(hTXR specifies that Haskell source files are to be preprocessed with a C preprocessor.h`NhnNhohhUj¼&ubeubaubeubj¹)r×&}rØ&(hTUhUjg$h`hahbj¼hd}rÙ&(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÚ&}rÛ&(hTUhUjg$h`hahbjÁhd}rÜ&(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrÝ&jÇjÝ&uhnNhohhp]rÞ&(jÉ)rß&}rà&(hTX!other-extensions: identifier listhUjÚ&h`hahbjÍhd}rá&(hi]râ&Xpkg-field-other-extensionsrã&ahh]hf]hg]hl]jщuhnM÷hohhp]rä&(j¹)rå&}ræ&(hTUhUjß&h`hahbj¼hd}rç&(hi]hh]hf]hg]hl]Uentries]rè&(j×X%other-extensions; package.cabal fieldjã&UNtré&auhnM÷hohhp]ubjÙ)rê&}rë&(hTXother-extensionsrì&hUjß&h`hahbjÜhd}rí&(jÑjÒhi]hh]hf]hg]hl]uhnM÷hohhp]rî&hyXother-extensionsrï&…rð&}rñ&(hTUh`NhnNhohhUjê&ubaubjâ)rò&}ró&(hTj[hUjß&h`hahbjåhd}rô&(jÑjÒhi]hh]hf]hg]hl]uhnM÷hohhp]rõ&hyX: rö&…r÷&}rø&(hTUh`NhnNhohhUjò&ubaubja)rù&}rú&(hTXidentifier listhUjß&h`hahbjdhd}rû&(jÑjÒhi]hh]hf]hg]hl]uhnM÷hohhp]rü&hyXidentifier listrý&…rþ&}rÿ&(hTUh`NhnNhohhUjù&ubaubeubjê)r'}r'(hTUhUjÚ&h`hahbjíhd}r'(hf]hg]hh]hi]hl]uhnM÷hohhp]r'(h})r'}r'(hTXÃA list of Haskell extensions used by some (but not necessarily all) modules. From GHC version 6.6 onward, these may be specified by placing a ``LANGUAGE`` pragma in the source files affected e.g.hUj'h`hahbhhd}r'(hf]hg]hh]hi]hl]uhnMÞhohhp]r'(hyXŽA list of Haskell extensions used by some (but not necessarily all) modules. From GHC version 6.6 onward, these may be specified by placing a r'…r '}r '(hTXŽA list of Haskell extensions used by some (but not necessarily all) modules. From GHC version 6.6 onward, these may be specified by placing a h`NhnNhohhUj'ubhß)r '}r '(hTX ``LANGUAGE``hd}r '(hf]hg]hh]hi]hl]uhUj'hp]r'hyXLANGUAGEr'…r'}r'(hTUhUj 'ubahbhçubhyX) pragma in the source files affected e.g.r'…r'}r'(hTX) pragma in the source files affected e.g.h`NhnNhohhUj'ubeubjÌ)r'}r'(hTX+{-# LANGUAGE CPP, MultiParamTypeClasses #-}hUj'h`hahbjÏhd}r'(j‰jXhaskelljÑjÒhi]hh]hf]j}hg]hl]uhnMâhohhp]r'hyX+{-# LANGUAGE CPP, MultiParamTypeClasses #-}r'…r'}r'(hTUhUj'ubaubh})r'}r'(hTXÅIn Cabal-1.24 the dependency solver will use this and :pkg-field:`default-extensions` information. Cabal prior to 1.24 will abort compilation if the current compiler doesn't provide the extensions.hUj'h`hahbhhd}r'(hf]hg]hh]hi]hl]uhnMæhohhp]r'(hyX6In Cabal-1.24 the dependency solver will use this and r '…r!'}r"'(hTX6In Cabal-1.24 the dependency solver will use this and h`NhnNhohhUj'ubjk)r#'}r$'(hTX:pkg-field:`default-extensions`r%'hUj'h`hahbjohd}r&'(UreftypeX pkg-fieldjqˆjrXdefault-extensionsU refdomainXcabalr''hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMæhp]r('hß)r)'}r*'(hTj%'hd}r+'(hf]hg]r,'(j|j''Xcabal-pkg-fieldr-'ehh]hi]hl]uhUj#'hp]r.'hyXdefault-extensionsr/'…r0'}r1'(hTUhUj)'ubahbhçubaubhyXr information. Cabal prior to 1.24 will abort compilation if the current compiler doesn’t provide the extensions.r2'…r3'}r4'(hTXp information. Cabal prior to 1.24 will abort compilation if the current compiler doesn't provide the extensions.h`NhnNhohhUj'ubeubh})r5'}r6'(hTX¥If you use some extensions conditionally, using CPP or conditional module lists, it is good to replicate the condition in :pkg-field:`other-extensions` declarations:hUj'h`hahbhhd}r7'(hf]hg]hh]hi]hl]uhnMêhohhp]r8'(hyXzIf you use some extensions conditionally, using CPP or conditional module lists, it is good to replicate the condition in r9'…r:'}r;'(hTXzIf you use some extensions conditionally, using CPP or conditional module lists, it is good to replicate the condition in h`NhnNhohhUj5'ubjk)r<'}r='(hTX:pkg-field:`other-extensions`r>'hUj5'h`hahbjohd}r?'(UreftypeX pkg-fieldjqˆjrXother-extensionsU refdomainXcabalr@'hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMêhp]rA'hß)rB'}rC'(hTj>'hd}rD'(hf]hg]rE'(j|j@'Xcabal-pkg-fieldrF'ehh]hi]hl]uhUj<'hp]rG'hyXother-extensionsrH'…rI'}rJ'(hTUhUjB'ubahbhçubaubhyX declarations:rK'…rL'}rM'(hTX declarations:h`NhnNhohhUj5'ubeubjÌ)rN'}rO'(hTXGother-extensions: CPP if impl(ghc >= 7.5) other-extensions: PolyKindshUj'h`hahbjÏhd}rP'(jÑjÒhi]hh]hf]hg]hl]uhnMðhohhp]rQ'hyXGother-extensions: CPP if impl(ghc >= 7.5) other-extensions: PolyKindsrR'…rS'}rT'(hTUhUjN'ubaubh})rU'}rV'(hTX¯You could also omit the conditionally used extensions, as they are for information only, but it is recommended to replicate them in :pkg-field:`other-extensions` declarations.hUj'h`hahbhhd}rW'(hf]hg]hh]hi]hl]uhnMôhohhp]rX'(hyX„You could also omit the conditionally used extensions, as they are for information only, but it is recommended to replicate them in rY'…rZ'}r['(hTX„You could also omit the conditionally used extensions, as they are for information only, but it is recommended to replicate them in h`NhnNhohhUjU'ubjk)r\'}r]'(hTX:pkg-field:`other-extensions`r^'hUjU'h`hahbjohd}r_'(UreftypeX pkg-fieldjqˆjrXother-extensionsU refdomainXcabalr`'hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMôhp]ra'hß)rb'}rc'(hTj^'hd}rd'(hf]hg]re'(j|j`'Xcabal-pkg-fieldrf'ehh]hi]hl]uhUj\'hp]rg'hyXother-extensionsrh'…ri'}rj'(hTUhUjb'ubahbhçubaubhyX declarations.rk'…rl'}rm'(hTX declarations.h`NhnNhohhUjU'ubeubeubeubj¹)rn'}ro'(hTUhUjg$h`hahbj¼hd}rp'(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rq'}rr'(hTUhUjg$h`hahbjÁhd}rs'(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrt'jÇjt'uhnNhohhp]ru'(jÉ)rv'}rw'(hTXextensions: identifier listhUjq'h`hahbjÍhd}rx'(hi]ry'Xpkg-field-extensionsrz'ahh]hf]hg]hl]jщuhnNhohhp]r{'(j¹)r|'}r}'(hTUhUjv'h`hahbj¼hd}r~'(hi]hh]hf]hg]hl]Uentries]r'(j×Xextensions; package.cabal fieldjz'UNtr€'auhnNhohhp]ubjÙ)r'}r‚'(hTX extensionsrƒ'hUjv'h`hahbjÜhd}r„'(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]r…'hyX extensionsr†'…r‡'}rˆ'(hTUh`NhnNhohhUj'ubaubjâ)r‰'}rŠ'(hTj[hUjv'h`hahbjåhd}r‹'(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rŒ'hyX: r'…rŽ'}r'(hTUh`NhnNhohhUj‰'ubaubja)r'}r‘'(hTXidentifier listhUjv'h`hahbjdhd}r’'(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]r“'hyXidentifier listr”'…r•'}r–'(hTUh`NhnNhohhUj'ubaubeubjê)r—'}r˜'(hTUhUjq'h`hahbjíhd}r™'(hf]hg]hh]hi]hl]uhnNhohhp]rš'(jð)r›'}rœ'(hTUhUj—'h`hahbjóhd}r'(hf]hg]hh]hi]hl]uhnNhohhp]rž'jö)rŸ'}r '(hTUhUj›'h`hahbjùhd}r¡'(hf]hg]hh]hi]hl]uhnNhohhp]r¢'(jü)r£'}r¤'(hTU Deprecatedr¥'hUjŸ'h`hahbjhd}r¦'(hf]hg]hh]hi]hl]uhnKhp]r§'hyX Deprecatedr¨'…r©'}rª'(hTUhUj£'ubaubj)r«'}r¬'(hTUhd}r­'(hf]hg]hh]hi]hl]uhUjŸ'hp]r®'h})r¯'}r°'(hTUhd}r±'(hf]hg]hh]hi]hl]uhUj«'hp]hbhubahbjubeubaubh})r²'}r³'(hTX7Deprecated in favor of :pkg-field:`default-extensions`.hUj—'h`hahbhhd}r´'(hf]hg]hh]hi]hl]uhnMûhohhp]rµ'(hyXDeprecated in favor of r¶'…r·'}r¸'(hTXDeprecated in favor of h`NhnNhohhUj²'ubjk)r¹'}rº'(hTX:pkg-field:`default-extensions`r»'hUj²'h`hahbjohd}r¼'(UreftypeX pkg-fieldjqˆjrXdefault-extensionsU refdomainXcabalr½'hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMûhp]r¾'hß)r¿'}rÀ'(hTj»'hd}rÁ'(hf]hg]rÂ'(j|j½'Xcabal-pkg-fieldrÃ'ehh]hi]hl]uhUj¹'hp]rÄ'hyXdefault-extensionsrÅ'…rÆ'}rÇ'(hTUhUj¿'ubahbhçubaubhyX.…rÈ'}rÉ'(hTX.h`NhnNhohhUj²'ubeubeubeubj¹)rÊ'}rË'(hTUhUjg$h`hahbj¼hd}rÌ'(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÍ'}rÎ'(hTUhUjg$h`hahbjÁhd}rÏ'(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrÐ'jÇjÐ'uhnNhohhp]rÑ'(jÉ)rÒ'}rÓ'(hTX+build-tool-depends: package:executable listhUjÍ'h`hahbjÍhd}rÔ'(hi]rÕ'Xpkg-field-build-tool-dependsrÖ'ahh]hf]hg]hl]jщuhnMhohhp]r×'(j¹)rØ'}rÙ'(hTUhUjÒ'h`hahbj¼hd}rÚ'(hi]hh]hf]hg]hl]Uentries]rÛ'(j×X'build-tool-depends; package.cabal fieldjÖ'UNtrÜ'auhnMhohhp]ubjÙ)rÝ'}rÞ'(hTXbuild-tool-dependsrß'hUjÒ'h`hahbjÜhd}rà'(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]rá'hyXbuild-tool-dependsrâ'…rã'}rä'(hTUh`NhnNhohhUjÝ'ubaubjâ)rå'}ræ'(hTj[hUjÒ'h`hahbjåhd}rç'(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]rè'hyX: ré'…rê'}rë'(hTUh`NhnNhohhUjå'ubaubja)rì'}rí'(hTXpackage:executable listhUjÒ'h`hahbjdhd}rî'(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]rï'hyXpackage:executable listrð'…rñ'}rò'(hTUh`NhnNhohhUjì'ubaubeubjê)ró'}rô'(hTUhUjÍ'h`hahbjíhd}rõ'(hf]hg]hh]hi]hl]uhnMhohhp]rö'(h})r÷'}rø'(hTXjA list of Haskell programs needed to build this component. Each is specified by the package containing the executable and the name of the executable itself, separated by a colon, and optionally followed by a version bound. It is fine for the package to be the current one, in which case this is termed an *internal*, rather than *external* executable dependency.hUjó'h`hahbhhd}rù'(hf]hg]hh]hi]hl]uhnMÿhohhp]rú'(hyX1A list of Haskell programs needed to build this component. Each is specified by the package containing the executable and the name of the executable itself, separated by a colon, and optionally followed by a version bound. It is fine for the package to be the current one, in which case this is termed an rû'…rü'}rý'(hTX1A list of Haskell programs needed to build this component. Each is specified by the package containing the executable and the name of the executable itself, separated by a colon, and optionally followed by a version bound. It is fine for the package to be the current one, in which case this is termed an h`NhnNhohhUj÷'ubh¿)rþ'}rÿ'(hTX *internal*hd}r((hf]hg]hh]hi]hl]uhUj÷'hp]r(hyXinternalr(…r(}r((hTUhUjþ'ubahbhÇubhyX, rather than r(…r(}r((hTX, rather than h`NhnNhohhUj÷'ubh¿)r(}r ((hTX *external*hd}r ((hf]hg]hh]hi]hl]uhUj÷'hp]r (hyXexternalr (…r (}r((hTUhUj(ubahbhÇubhyX executable dependency.r(…r(}r((hTX executable dependency.h`NhnNhohhUj÷'ubeubh})r(}r((hTXÛExternal dependencies can (and should) contain a version bound like conventional :pkg-field:`build-depends` dependencies. Internal deps should not contain a version bound, as they will be always resolved within the same configuration of the package in the build plan. Specifically, version bounds that include the package's version will be warned for being extraneous, and version bounds that exclude the package's version will raise and error for being impossible to follow.hUjó'h`hahbhhd}r((hf]hg]hh]hi]hl]uhnMhohhp]r((hyXQExternal dependencies can (and should) contain a version bound like conventional r(…r(}r((hTXQExternal dependencies can (and should) contain a version bound like conventional h`NhnNhohhUj(ubjk)r(}r((hTX:pkg-field:`build-depends`r(hUj(h`hahbjohd}r((UreftypeX pkg-fieldjqˆjrX build-dependsU refdomainXcabalr(hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMhp]r(hß)r(}r ((hTj(hd}r!((hf]hg]r"((j|j(Xcabal-pkg-fieldr#(ehh]hi]hl]uhUj(hp]r$(hyX build-dependsr%(…r&(}r'((hTUhUj(ubahbhçubaubhyXt dependencies. Internal deps should not contain a version bound, as they will be always resolved within the same configuration of the package in the build plan. Specifically, version bounds that include the package’s version will be warned for being extraneous, and version bounds that exclude the package’s version will raise and error for being impossible to follow.r((…r)(}r*((hTXp dependencies. Internal deps should not contain a version bound, as they will be always resolved within the same configuration of the package in the build plan. Specifically, version bounds that include the package's version will be warned for being extraneous, and version bounds that exclude the package's version will raise and error for being impossible to follow.h`NhnNhohhUj(ubeubh})r+(}r,((hTXðCabal can make sure that specified programs are built and on the ``PATH`` before building the component in question. It will always do so for internal dependencies, and also do so for external dependencies when using Nix-style local builds.hUjó'h`hahbhhd}r-((hf]hg]hh]hi]hl]uhnMhohhp]r.((hyXACabal can make sure that specified programs are built and on the r/(…r0(}r1((hTXACabal can make sure that specified programs are built and on the h`NhnNhohhUj+(ubhß)r2(}r3((hTX``PATH``hd}r4((hf]hg]hh]hi]hl]uhUj+(hp]r5(hyXPATHr6(…r7(}r8((hTUhUj2(ubahbhçubhyX§ before building the component in question. It will always do so for internal dependencies, and also do so for external dependencies when using Nix-style local builds.r9(…r:(}r;((hTX§ before building the component in question. It will always do so for internal dependencies, and also do so for external dependencies when using Nix-style local builds.h`NhnNhohhUj+(ubeubh})r<(}r=((hTXÍ:pkg-field:`build-tool-depends` was added in Cabal 2.0, and it will be ignored (with a warning) with old versions of Cabal. See :pkg-field:`build-tools` for more information about backwards compatibility.hUjó'h`hahbhhd}r>((hf]hg]hh]hi]hl]uhnM hohhp]r?((jk)r@(}rA((hTX:pkg-field:`build-tool-depends`rB(hUj<(h`hahbjohd}rC((UreftypeX pkg-fieldjqˆjrXbuild-tool-dependsU refdomainXcabalrD(hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnM hp]rE(hß)rF(}rG((hTjB(hd}rH((hf]hg]rI((j|jD(Xcabal-pkg-fieldrJ(ehh]hi]hl]uhUj@(hp]rK(hyXbuild-tool-dependsrL(…rM(}rN((hTUhUjF(ubahbhçubaubhyXb was added in Cabal 2.0, and it will be ignored (with a warning) with old versions of Cabal. See rO(…rP(}rQ((hTXb was added in Cabal 2.0, and it will be ignored (with a warning) with old versions of Cabal. See h`NhnNhohhUj<(ubjk)rR(}rS((hTX:pkg-field:`build-tools`rT(hUj<(h`hahbjohd}rU((UreftypeX pkg-fieldjqˆjrX build-toolsU refdomainXcabalrV(hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnM hp]rW(hß)rX(}rY((hTjT(hd}rZ((hf]hg]r[((j|jV(Xcabal-pkg-fieldr\(ehh]hi]hl]uhUjR(hp]r](hyX build-toolsr^(…r_(}r`((hTUhUjX(ubahbhçubaubhyX4 for more information about backwards compatibility.ra(…rb(}rc((hTX4 for more information about backwards compatibility.h`NhnNhohhUj<(ubeubeubeubj¹)rd(}re((hTUhUjg$h`hahbj¼hd}rf((hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rg(}rh((hTUhUjg$h`hahbjÁhd}ri((jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrj(jÇjj(uhnNhohhp]rk((jÉ)rl(}rm((hTXbuild-tools: program listhUjg(h`hahbjÍhd}rn((hi]ro(Xpkg-field-build-toolsrp(ahh]hf]hg]hl]jщuhnNhohhp]rq((j¹)rr(}rs((hTUhUjl(h`hahbj¼hd}rt((hi]hh]hf]hg]hl]Uentries]ru((j×X build-tools; package.cabal fieldjp(UNtrv(auhnNhohhp]ubjÙ)rw(}rx((hTX build-toolsry(hUjl(h`hahbjÜhd}rz((jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]r{(hyX build-toolsr|(…r}(}r~((hTUh`NhnNhohhUjw(ubaubjâ)r(}r€((hTj[hUjl(h`hahbjåhd}r((jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]r‚(hyX: rƒ(…r„(}r…((hTUh`NhnNhohhUj(ubaubja)r†(}r‡((hTX program listhUjl(h`hahbjdhd}rˆ((jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]r‰(hyX program listrŠ(…r‹(}rŒ((hTUh`NhnNhohhUj†(ubaubeubjê)r(}rŽ((hTUhUjg(h`hahbjíhd}r((hf]hg]hh]hi]hl]uhnNhohhp]r((jð)r‘(}r’((hTUhUj(h`hahbjóhd}r“((hf]hg]hh]hi]hl]uhnNhohhp]r”(jö)r•(}r–((hTUhUj‘(h`hahbjùhd}r—((hf]hg]hh]hi]hl]uhnNhohhp]r˜((jü)r™(}rš((hTj¥'hUj•(h`hahbjhd}r›((hf]hg]hh]hi]hl]uhnKhp]rœ(hyX Deprecatedr(…rž(}rŸ((hTUhUj™(ubaubj)r (}r¡((hTUhd}r¢((hf]hg]hh]hi]hl]uhUj•(hp]r£(h})r¤(}r¥((hTUhd}r¦((hf]hg]hh]hi]hl]uhUj (hp]hbhubahbjubeubaubjL)r§(}r¨((hTUhUj(h`hahbjOhd}r©((hf]hg]hh]hi]hl]uhnNhohhp]rª((h})r«(}r¬((hTX€Deprecated in favor of :pkg-field:`build-tool-depends`, but `see below for backwards compatibility information. `_r­(hUj§(h`hahbhhd}r®((hf]hg]hh]hi]hl]uhnMhp]r¯((hyXDeprecated in favor of r°(…r±(}r²((hTXDeprecated in favor of hUj«(ubjk)r³(}r´((hTX:pkg-field:`build-tool-depends`rµ(hUj«(h`hahbjohd}r¶((UreftypeX pkg-fieldjqˆjrXbuild-tool-dependsU refdomainXcabalr·(hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMhp]r¸(hß)r¹(}rº((hTjµ(hd}r»((hf]hg]r¼((j|j·(Xcabal-pkg-fieldr½(ehh]hi]hl]uhUj³(hp]r¾(hyXbuild-tool-dependsr¿(…rÀ(}rÁ((hTUhUj¹(ubahbhçubaubhyX, but rÂ(…rÃ(}rÄ((hTX, but hUj«(ubj?)rÅ(}rÆ((hTXD`see below for backwards compatibility information. `_hd}rÇ((UnameX2see below for backwards compatibility information.j~X buildtoolsbcrÈ(hi]hh]hf]hg]hl]uhUj«(hp]rÉ(hyX2see below for backwards compatibility information.rÊ(…rË(}rÌ((hTUhUjÅ(ubahbjCubj )rÍ(}rÎ((hTX hYKhUj«(hbj£hd}rÏ((UrefurijÈ(hi]rÐ(U1see-below-for-backwards-compatibility-informationrÑ(ahh]hf]hg]hl]rÒ(hKauhp]ubeubh})rÓ(}rÔ((hTX¸A list of Haskell programs needed to build this component. Each may be followed by an optional version bound. Confusingly, each program in the list either refer to one of three things:rÕ(hUj§(h`hahbhhd}rÖ((hf]hg]hh]hi]hl]uhnMhp]r×(hyX¸A list of Haskell programs needed to build this component. Each may be followed by an optional version bound. Confusingly, each program in the list either refer to one of three things:rØ(…rÙ(}rÚ((hTjÕ(hUjÓ(ubaubjL)rÛ(}rÜ((hTUhd}rÝ((hf]hg]hh]hi]hl]uhUj§(hp]rÞ(cdocutils.nodes enumerated_list rß()rà(}rá((hTUhd}râ((Usuffixrã(U.hi]hh]hf]Uprefixrä(Uhg]hl]Uenumtyperå(Uarabicræ(uhUjÛ(hp]rç((hŽ)rè(}ré((hTX(Another executables in the same package hd}rê((hf]hg]hh]hi]hl]uhUjà(hp]rë(h})rì(}rí((hTX'Another executables in the same packagerî(hUjè(h`hahbhhd}rï((hf]hg]hh]hi]hl]uhnMhp]rð(hyX'Another executables in the same packagerñ(…rò(}ró((hTjî(hUjì(ubaubahbh‘ubhŽ)rô(}rõ((hTXsOne of a hard-coded set of packages containing common build tools (possibly extended by a ``Custom`` setup script) hd}rö((hf]hg]hh]hi]hl]uhUjà(hp]r÷(h})rø(}rù((hTXrOne of a hard-coded set of packages containing common build tools (possibly extended by a ``Custom`` setup script)hUjô(h`hahbhhd}rú((hf]hg]hh]hi]hl]uhnMhp]rû((hyXZOne of a hard-coded set of packages containing common build tools (possibly extended by a rü(…rý(}rþ((hTXZOne of a hard-coded set of packages containing common build tools (possibly extended by a hUjø(ubhß)rÿ(}r)(hTX ``Custom``hd}r)(hf]hg]hh]hi]hl]uhUjø(hp]r)hyXCustomr)…r)}r)(hTUhUjÿ(ubahbhçubhyX setup script)r)…r)}r)(hTX setup script)hUjø(ubeubahbh‘ubhŽ)r )}r )(hTXgA pre-built executable that should already be on the ``PATH`` (Supported only by Cabal 2.0 and later.) hd}r )(hf]hg]hh]hi]hl]uhUjà(hp]r )h})r )}r)(hTXfA pre-built executable that should already be on the ``PATH`` (Supported only by Cabal 2.0 and later.)hUj )h`hahbhhd}r)(hf]hg]hh]hi]hl]uhnMhp]r)(hyX5A pre-built executable that should already be on the r)…r)}r)(hTX5A pre-built executable that should already be on the hUj )ubhß)r)}r)(hTX``PATH``hd}r)(hf]hg]hh]hi]hl]uhUj )hp]r)hyXPATHr)…r)}r)(hTUhUj)ubahbhçubhyX) (Supported only by Cabal 2.0 and later.)r)…r)}r)(hTX) (Supported only by Cabal 2.0 and later.)hUj )ubeubahbh‘ubehbUenumerated_listr)ubahbjOubh})r)}r )(hTXÑThese cases are listed in order of priority: an executable in the package will override any of the hard-coded packages with the same name, and a hard-coded package will override any executable on the ``PATH``.hUj§(h`hahbhhd}r!)(hf]hg]hh]hi]hl]uhnM hp]r")(hyXÈThese cases are listed in order of priority: an executable in the package will override any of the hard-coded packages with the same name, and a hard-coded package will override any executable on the r#)…r$)}r%)(hTXÈThese cases are listed in order of priority: an executable in the package will override any of the hard-coded packages with the same name, and a hard-coded package will override any executable on the hUj)ubhß)r&)}r')(hTX``PATH``hd}r()(hf]hg]hh]hi]hl]uhUj)hp]r))hyXPATHr*)…r+)}r,)(hTUhUj&)ubahbhçubhyX.…r-)}r.)(hTX.hUj)ubeubh})r/)}r0)(hTXIn the first two cases, the list entry is desugared into a :pkg-field:`build-tool-depends` entry. In the first case, the entry is desugared into a :pkg-field:`build-tool-depends` entry by prefixing with ``$pkg:``. In the second case, it is desugared by looking up the package and executable name in a hard-coded table. In either case, the optional version bound is passed through unchanged. Refer to the documentation for :pkg-field:`build-tool-depends` to understand the desugared field's meaning, along with restrictions on version bounds.hUj§(h`hahbhhd}r1)(hf]hg]hh]hi]hl]uhnM$hp]r2)(hyX;In the first two cases, the list entry is desugared into a r3)…r4)}r5)(hTX;In the first two cases, the list entry is desugared into a hUj/)ubjk)r6)}r7)(hTX:pkg-field:`build-tool-depends`r8)hUj/)h`hahbjohd}r9)(UreftypeX pkg-fieldjqˆjrXbuild-tool-dependsU refdomainXcabalr:)hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnM$hp]r;)hß)r<)}r=)(hTj8)hd}r>)(hf]hg]r?)(j|j:)Xcabal-pkg-fieldr@)ehh]hi]hl]uhUj6)hp]rA)hyXbuild-tool-dependsrB)…rC)}rD)(hTUhUj<)ubahbhçubaubhyX9 entry. In the first case, the entry is desugared into a rE)…rF)}rG)(hTX9 entry. In the first case, the entry is desugared into a hUj/)ubjk)rH)}rI)(hTX:pkg-field:`build-tool-depends`rJ)hUj/)h`hahbjohd}rK)(UreftypeX pkg-fieldjqˆjrXbuild-tool-dependsU refdomainXcabalrL)hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnM$hp]rM)hß)rN)}rO)(hTjJ)hd}rP)(hf]hg]rQ)(j|jL)Xcabal-pkg-fieldrR)ehh]hi]hl]uhUjH)hp]rS)hyXbuild-tool-dependsrT)…rU)}rV)(hTUhUjN)ubahbhçubaubhyX entry by prefixing with rW)…rX)}rY)(hTX entry by prefixing with hUj/)ubhß)rZ)}r[)(hTX ``$pkg:``hd}r\)(hf]hg]hh]hi]hl]uhUj/)hp]r])hyX$pkg:r^)…r_)}r`)(hTUhUjZ)ubahbhçubhyXÒ. In the second case, it is desugared by looking up the package and executable name in a hard-coded table. In either case, the optional version bound is passed through unchanged. Refer to the documentation for ra)…rb)}rc)(hTXÒ. In the second case, it is desugared by looking up the package and executable name in a hard-coded table. In either case, the optional version bound is passed through unchanged. Refer to the documentation for hUj/)ubjk)rd)}re)(hTX:pkg-field:`build-tool-depends`rf)hUj/)h`hahbjohd}rg)(UreftypeX pkg-fieldjqˆjrXbuild-tool-dependsU refdomainXcabalrh)hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnM$hp]ri)hß)rj)}rk)(hTjf)hd}rl)(hf]hg]rm)(j|jh)Xcabal-pkg-fieldrn)ehh]hi]hl]uhUjd)hp]ro)hyXbuild-tool-dependsrp)…rq)}rr)(hTUhUjj)ubahbhçubaubhyXZ to understand the desugared field’s meaning, along with restrictions on version bounds.rs)…rt)}ru)(hTXX to understand the desugared field's meaning, along with restrictions on version bounds.hUj/)ubeubj )rv)}rw)(hTX.. _buildtoolsbc:hUj§(hbj£hd}rx)(hi]hh]hf]hg]hl]jEU buildtoolsbcry)uhnM*hp]ubh})rz)}r{)(hTXQAlthough this field is deprecated in favor of :pkg-field:`build-tool-depends`, there are some situations where you may prefer to use :pkg-field:`build-tool` in cases (1) and (2), as it is supported by more versions of Cabal. In case (3), :pkg-field:`build-tool-depends` is better for backwards-compatibility, as it will be ignored by old versions of Cabal; if you add the executable to :pkg-field:`build-tools`, a setup script built against old Cabal will choke. If an old version of Cabal is used, an end-user will have to manually arrange for the requested executable to be in your ``PATH``.hUj§(h`hajÓ }r|)h*(j¹)r?*}r@*(hTUhUj9*h`hahbj¼hd}rA*(hi]hh]hf]hg]hl]Uentries]rB*(j×X ghc-options; package.cabal fieldj=*UNtrC*auhnMDhohhp]ubjÙ)rD*}rE*(hTX ghc-optionsrF*hUj9*h`hahbjÜhd}rG*(jÑjÒhi]hh]hf]hg]hl]uhnMDhohhp]rH*hyX ghc-optionsrI*…rJ*}rK*(hTUh`NhnNhohhUjD*ubaubjâ)rL*}rM*(hTj[hUj9*h`hahbjåhd}rN*(jÑjÒhi]hh]hf]hg]hl]uhnMDhohhp]rO*hyX: rP*…rQ*}rR*(hTUh`NhnNhohhUjL*ubaubja)rS*}rT*(hTX token listhUj9*h`hahbjdhd}rU*(jÑjÒhi]hh]hf]hg]hl]uhnMDhohhp]rV*hyX token listrW*…rX*}rY*(hTUh`NhnNhohhUjS*ubaubeubjê)rZ*}r[*(hTUhUj4*h`hahbjíhd}r\*(hf]hg]hh]hi]hl]uhnMDhohhp]r]*(h})r^*}r_*(hTX~Additional options for GHC. You can often achieve the same effect using the :pkg-field:`extensions` field, which is preferred.hUjZ*h`hahbhhd}r`*(hf]hg]hh]hi]hl]uhnM;hohhp]ra*(hyXLAdditional options for GHC. You can often achieve the same effect using the rb*…rc*}rd*(hTXLAdditional options for GHC. You can often achieve the same effect using the h`NhnNhohhUj^*ubjk)re*}rf*(hTX:pkg-field:`extensions`rg*hUj^*h`hahbjohd}rh*(UreftypeX pkg-fieldjqˆjrX extensionsU refdomainXcabalri*hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnM;hp]rj*hß)rk*}rl*(hTjg*hd}rm*(hf]hg]rn*(j|ji*Xcabal-pkg-fieldro*ehh]hi]hl]uhUje*hp]rp*hyX extensionsrq*…rr*}rs*(hTUhUjk*ubahbhçubaubhyX field, which is preferred.rt*…ru*}rv*(hTX field, which is preferred.h`NhnNhohhUj^*ubeubh})rw*}rx*(hTXvOptions required only by one module may be specified by placing an ``OPTIONS_GHC`` pragma in the source file affected.hUjZ*h`hahbhhd}ry*(hf]hg]hh]hi]hl]uhnM>hohhp]rz*(hyXCOptions required only by one module may be specified by placing an r{*…r|*}r}*(hTXCOptions required only by one module may be specified by placing an h`NhnNhohhUjw*ubhß)r~*}r*(hTX``OPTIONS_GHC``hd}r€*(hf]hg]hh]hi]hl]uhUjw*hp]r*hyX OPTIONS_GHCr‚*…rƒ*}r„*(hTUhUj~*ubahbhçubhyX$ pragma in the source file affected.r…*…r†*}r‡*(hTX$ pragma in the source file affected.h`NhnNhohhUjw*ubeubh})rˆ*}r‰*(hTX•As with many other fields, whitespace can be escaped by using Haskell string syntax. Example: ``ghc-options: -Wcompat "-with-rtsopts=-T -I1" -Wall``.hUjZ*h`hahbhhd}rŠ*(hf]hg]hh]hi]hl]uhnMAhohhp]r‹*(hyX^As with many other fields, whitespace can be escaped by using Haskell string syntax. Example: rŒ*…r*}rŽ*(hTX^As with many other fields, whitespace can be escaped by using Haskell string syntax. Example: h`NhnNhohhUjˆ*ubhß)r*}r*(hTX6``ghc-options: -Wcompat "-with-rtsopts=-T -I1" -Wall``hd}r‘*(hf]hg]hh]hi]hl]uhUjˆ*hp]r’*hyX2ghc-options: -Wcompat "-with-rtsopts=-T -I1" -Wallr“*…r”*}r•*(hTUhUj*ubahbhçubhyX.…r–*}r—*(hTX.h`NhnNhohhUjˆ*ubeubeubeubj¹)r˜*}r™*(hTUhUjg$h`hahbj¼hd}rš*(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r›*}rœ*(hTUhUjg$h`hahbjÁhd}r*(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrž*jÇjž*uhnNhohhp]rŸ*(jÉ)r *}r¡*(hTXghc-prof-options: token listhUj›*h`hahbjÍhd}r¢*(hi]r£*Xpkg-field-ghc-prof-optionsr¤*ahh]hf]hg]hl]jщuhnMYhohhp]r¥*(j¹)r¦*}r§*(hTUhUj *h`hahbj¼hd}r¨*(hi]hh]hf]hg]hl]Uentries]r©*(j×X%ghc-prof-options; package.cabal fieldj¤*UNtrª*auhnMYhohhp]ubjÙ)r«*}r¬*(hTXghc-prof-optionsr­*hUj *h`hahbjÜhd}r®*(jÑjÒhi]hh]hf]hg]hl]uhnMYhohhp]r¯*hyXghc-prof-optionsr°*…r±*}r²*(hTUh`NhnNhohhUj«*ubaubjâ)r³*}r´*(hTj[hUj *h`hahbjåhd}rµ*(jÑjÒhi]hh]hf]hg]hl]uhnMYhohhp]r¶*hyX: r·*…r¸*}r¹*(hTUh`NhnNhohhUj³*ubaubja)rº*}r»*(hTX token listhUj *h`hahbjdhd}r¼*(jÑjÒhi]hh]hf]hg]hl]uhnMYhohhp]r½*hyX token listr¾*…r¿*}rÀ*(hTUh`NhnNhohhUjº*ubaubeubjê)rÁ*}rÂ*(hTUhUj›*h`hahbjíhd}rÃ*(hf]hg]hh]hi]hl]uhnMYhohhp]rÄ*(h})rÅ*}rÆ*(hTXLAdditional options for GHC when the package is built with profiling enabled.rÇ*hUjÁ*h`hahbhhd}rÈ*(hf]hg]hh]hi]hl]uhnMGhohhp]rÉ*hyXLAdditional options for GHC when the package is built with profiling enabled.rÊ*…rË*}rÌ*(hTjÇ*h`NhnNhohhUjÅ*ubaubh})rÍ*}rÎ*(hTX²Note that as of Cabal-1.24, the default profiling detail level defaults to ``exported-functions`` for libraries and ``toplevel-functions`` for executables. For GHC these correspond to the flags ``-fprof-auto-exported`` and ``-fprof-auto-top``. Prior to Cabal-1.24 the level defaulted to ``none``. These levels can be adjusted by the person building the package with the ``--profiling-detail`` and ``--library-profiling-detail`` flags.hUjÁ*h`hahbhhd}rÏ*(hf]hg]hh]hi]hl]uhnMJhohhp]rÐ*(hyXKNote that as of Cabal-1.24, the default profiling detail level defaults to rÑ*…rÒ*}rÓ*(hTXKNote that as of Cabal-1.24, the default profiling detail level defaults to h`NhnNhohhUjÍ*ubhß)rÔ*}rÕ*(hTX``exported-functions``hd}rÖ*(hf]hg]hh]hi]hl]uhUjÍ*hp]r×*hyXexported-functionsrØ*…rÙ*}rÚ*(hTUhUjÔ*ubahbhçubhyX for libraries and rÛ*…rÜ*}rÝ*(hTX for libraries and h`NhnNhohhUjÍ*ubhß)rÞ*}rß*(hTX``toplevel-functions``hd}rà*(hf]hg]hh]hi]hl]uhUjÍ*hp]rá*hyXtoplevel-functionsrâ*…rã*}rä*(hTUhUjÞ*ubahbhçubhyX8 for executables. For GHC these correspond to the flags rå*…ræ*}rç*(hTX8 for executables. For GHC these correspond to the flags h`NhnNhohhUjÍ*ubhß)rè*}ré*(hTX``-fprof-auto-exported``hd}rê*(hf]hg]hh]hi]hl]uhUjÍ*hp]rë*hyX-fprof-auto-exportedrì*…rí*}rî*(hTUhUjè*ubahbhçubhyX and rï*…rð*}rñ*(hTX and rò*h`NhnNhohhUjÍ*ubhß)ró*}rô*(hTX``-fprof-auto-top``hd}rõ*(hf]hg]hh]hi]hl]uhUjÍ*hp]rö*hyX-fprof-auto-topr÷*…rø*}rù*(hTUhUjó*ubahbhçubhyX-. Prior to Cabal-1.24 the level defaulted to rú*…rû*}rü*(hTX-. Prior to Cabal-1.24 the level defaulted to h`NhnNhohhUjÍ*ubhß)rý*}rþ*(hTX``none``hd}rÿ*(hf]hg]hh]hi]hl]uhUjÍ*hp]r+hyXnoner+…r+}r+(hTUhUjý*ubahbhçubhyXK. These levels can be adjusted by the person building the package with the r+…r+}r+(hTXK. These levels can be adjusted by the person building the package with the h`NhnNhohhUjÍ*ubhß)r+}r+(hTX``--profiling-detail``hd}r +(hf]hg]hh]hi]hl]uhUjÍ*hp]r +hyX--profiling-detailr +…r +}r +(hTUhUj+ubahbhçubhyX and r+…r+}r+(hTjò*hUjÍ*ubhß)r+}r+(hTX``--library-profiling-detail``hd}r+(hf]hg]hh]hi]hl]uhUjÍ*hp]r+hyX--library-profiling-detailr+…r+}r+(hTUhUj+ubahbhçubhyX flags.r+…r+}r+(hTX flags.h`NhnNhohhUjÍ*ubeubh})r+}r+(hTX¯It is typically better for the person building the package to pick the profiling detail level rather than for the package author. So unless you have special needs it is probably better not to specify any of the GHC ``-fprof-auto*`` flags here. However if you wish to override the profiling detail level, you can do so using the :pkg-field:`ghc-prof-options` field: use ``-fno-prof-auto`` or one of the other ``-fprof-auto*`` flags.hUjÁ*h`hahbhhd}r+(hf]hg]hh]hi]hl]uhnMRhohhp]r+(hyX×It is typically better for the person building the package to pick the profiling detail level rather than for the package author. So unless you have special needs it is probably better not to specify any of the GHC r+…r +}r!+(hTX×It is typically better for the person building the package to pick the profiling detail level rather than for the package author. So unless you have special needs it is probably better not to specify any of the GHC h`NhnNhohhUj+ubhß)r"+}r#+(hTX``-fprof-auto*``hd}r$+(hf]hg]hh]hi]hl]uhUj+hp]r%+hyX -fprof-auto*r&+…r'+}r(+(hTUhUj"+ubahbhçubhyXa flags here. However if you wish to override the profiling detail level, you can do so using the r)+…r*+}r++(hTXa flags here. However if you wish to override the profiling detail level, you can do so using the h`NhnNhohhUj+ubjk)r,+}r-+(hTX:pkg-field:`ghc-prof-options`r.+hUj+h`hahbjohd}r/+(UreftypeX pkg-fieldjqˆjrXghc-prof-optionsU refdomainXcabalr0+hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMRhp]r1+hß)r2+}r3+(hTj.+hd}r4+(hf]hg]r5+(j|j0+Xcabal-pkg-fieldr6+ehh]hi]hl]uhUj,+hp]r7+hyXghc-prof-optionsr8+…r9+}r:+(hTUhUj2+ubahbhçubaubhyX field: use r;+…r<+}r=+(hTX field: use h`NhnNhohhUj+ubhß)r>+}r?+(hTX``-fno-prof-auto``hd}r@+(hf]hg]hh]hi]hl]uhUj+hp]rA+hyX-fno-prof-autorB+…rC+}rD+(hTUhUj>+ubahbhçubhyX or one of the other rE+…rF+}rG+(hTX or one of the other h`NhnNhohhUj+ubhß)rH+}rI+(hTX``-fprof-auto*``hd}rJ+(hf]hg]hh]hi]hl]uhUj+hp]rK+hyX -fprof-auto*rL+…rM+}rN+(hTUhUjH+ubahbhçubhyX flags.rO+…rP+}rQ+(hTX flags.h`NhnNhohhUj+ubeubeubeubj¹)rR+}rS+(hTUhUjg$h`hahbj¼hd}rT+(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rU+}rV+(hTUhUjg$h`hahbjÁhd}rW+(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrX+jÇjX+uhnNhohhp]rY+(jÉ)rZ+}r[+(hTXghc-shared-options: token listhUjU+h`hahbjÍhd}r\+(hi]r]+Xpkg-field-ghc-shared-optionsr^+ahh]hf]hg]hl]jщuhnM`hohhp]r_+(j¹)r`+}ra+(hTUhUjZ+h`hahbj¼hd}rb+(hi]hh]hf]hg]hl]Uentries]rc+(j×X'ghc-shared-options; package.cabal fieldj^+UNtrd+auhnM`hohhp]ubjÙ)re+}rf+(hTXghc-shared-optionsrg+hUjZ+h`hahbjÜhd}rh+(jÑjÒhi]hh]hf]hg]hl]uhnM`hohhp]ri+hyXghc-shared-optionsrj+…rk+}rl+(hTUh`NhnNhohhUje+ubaubjâ)rm+}rn+(hTj[hUjZ+h`hahbjåhd}ro+(jÑjÒhi]hh]hf]hg]hl]uhnM`hohhp]rp+hyX: rq+…rr+}rs+(hTUh`NhnNhohhUjm+ubaubja)rt+}ru+(hTX token listhUjZ+h`hahbjdhd}rv+(jÑjÒhi]hh]hf]hg]hl]uhnM`hohhp]rw+hyX token listrx+…ry+}rz+(hTUh`NhnNhohhUjt+ubaubeubjê)r{+}r|+(hTUhUjU+h`hahbjíhd}r}+(hf]hg]hh]hi]hl]uhnM`hohhp]r~+h})r+}r€+(hTXîAdditional options for GHC when the package is built as shared library. The options specified via this field are combined with the ones specified via :pkg-field:`ghc-options`, and are passed to GHC during both the compile and link phases.hUj{+h`hahbhhd}r+(hf]hg]hh]hi]hl]uhnM\hohhp]r‚+(hyX–Additional options for GHC when the package is built as shared library. The options specified via this field are combined with the ones specified via rƒ+…r„+}r…+(hTX–Additional options for GHC when the package is built as shared library. The options specified via this field are combined with the ones specified via h`NhnNhohhUj+ubjk)r†+}r‡+(hTX:pkg-field:`ghc-options`rˆ+hUj+h`hahbjohd}r‰+(UreftypeX pkg-fieldjqˆjrX ghc-optionsU refdomainXcabalrŠ+hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnM\hp]r‹+hß)rŒ+}r+(hTjˆ+hd}rŽ+(hf]hg]r+(j|jŠ+Xcabal-pkg-fieldr+ehh]hi]hl]uhUj†+hp]r‘+hyX ghc-optionsr’+…r“+}r”+(hTUhUjŒ+ubahbhçubaubhyX@, and are passed to GHC during both the compile and link phases.r•+…r–+}r—+(hTX@, and are passed to GHC during both the compile and link phases.h`NhnNhohhUj+ubeubaubeubj¹)r˜+}r™+(hTUhUjg$h`hahbj¼hd}rš+(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r›+}rœ+(hTUhUjg$h`hahbjÁhd}r+(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrž+jÇjž+uhnNhohhp]rŸ+(jÉ)r +}r¡+(hTXincludes: filename listhUj›+h`hahbjÍhd}r¢+(hi]r£+Xpkg-field-includesr¤+ahh]hf]hg]hl]jщuhnMphohhp]r¥+(j¹)r¦+}r§+(hTUhUj +h`hahbj¼hd}r¨+(hi]hh]hf]hg]hl]Uentries]r©+(j×Xincludes; package.cabal fieldj¤+UNtrª+auhnMphohhp]ubjÙ)r«+}r¬+(hTXincludesr­+hUj +h`hahbjÜhd}r®+(jÑjÒhi]hh]hf]hg]hl]uhnMphohhp]r¯+hyXincludesr°+…r±+}r²+(hTUh`NhnNhohhUj«+ubaubjâ)r³+}r´+(hTj[hUj +h`hahbjåhd}rµ+(jÑjÒhi]hh]hf]hg]hl]uhnMphohhp]r¶+hyX: r·+…r¸+}r¹+(hTUh`NhnNhohhUj³+ubaubja)rº+}r»+(hTX filename listhUj +h`hahbjdhd}r¼+(jÑjÒhi]hh]hf]hg]hl]uhnMphohhp]r½+hyX filename listr¾+…r¿+}rÀ+(hTUh`NhnNhohhUjº+ubaubeubjê)rÁ+}rÂ+(hTUhUj›+h`hahbjíhd}rÃ+(hf]hg]hh]hi]hl]uhnMphohhp]rÄ+(h})rÅ+}rÆ+(hTXA list of header files to be included in any compilations via C. This field applies to both header files that are already installed on the system and to those coming with the package to be installed. The former files should be found in absolute paths, while the latter files should be found in paths relative to the top of the source tree or relative to one of the directories listed in :pkg-field:`include-dirs`.hUjÁ+h`hahbhhd}rÇ+(hf]hg]hh]hi]hl]uhnMchohhp]rÈ+(hyXƒA list of header files to be included in any compilations via C. This field applies to both header files that are already installed on the system and to those coming with the package to be installed. The former files should be found in absolute paths, while the latter files should be found in paths relative to the top of the source tree or relative to one of the directories listed in rÉ+…rÊ+}rË+(hTXƒA list of header files to be included in any compilations via C. This field applies to both header files that are already installed on the system and to those coming with the package to be installed. The former files should be found in absolute paths, while the latter files should be found in paths relative to the top of the source tree or relative to one of the directories listed in h`NhnNhohhUjÅ+ubjk)rÌ+}rÍ+(hTX:pkg-field:`include-dirs`rÎ+hUjÅ+h`hahbjohd}rÏ+(UreftypeX pkg-fieldjqˆjrX include-dirsU refdomainXcabalrÐ+hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMchp]rÑ+hß)rÒ+}rÓ+(hTjÎ+hd}rÔ+(hf]hg]rÕ+(j|jÐ+Xcabal-pkg-fieldrÖ+ehh]hi]hl]uhUjÌ+hp]r×+hyX include-dirsrØ+…rÙ+}rÚ+(hTUhUjÒ+ubahbhçubaubhyX.…rÛ+}rÜ+(hTX.h`NhnNhohhUjÅ+ubeubh})rÝ+}rÞ+(hTXThese files typically contain function prototypes for foreign imports used by the package. This is in contrast to :pkg-field:`install-includes`, which lists header files that are intended to be exposed to other packages that transitively depend on this library.hUjÁ+h`hahbhhd}rß+(hf]hg]hh]hi]hl]uhnMkhohhp]rà+(hyXrThese files typically contain function prototypes for foreign imports used by the package. This is in contrast to rá+…râ+}rã+(hTXrThese files typically contain function prototypes for foreign imports used by the package. This is in contrast to h`NhnNhohhUjÝ+ubjk)rä+}rå+(hTX:pkg-field:`install-includes`ræ+hUjÝ+h`hahbjohd}rç+(UreftypeX pkg-fieldjqˆjrXinstall-includesU refdomainXcabalrè+hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMkhp]ré+hß)rê+}rë+(hTjæ+hd}rì+(hf]hg]rí+(j|jè+Xcabal-pkg-fieldrî+ehh]hi]hl]uhUjä+hp]rï+hyXinstall-includesrð+…rñ+}rò+(hTUhUjê+ubahbhçubaubhyXv, which lists header files that are intended to be exposed to other packages that transitively depend on this library.ró+…rô+}rõ+(hTXv, which lists header files that are intended to be exposed to other packages that transitively depend on this library.h`NhnNhohhUjÝ+ubeubeubeubj¹)rö+}r÷+(hTUhUjg$h`hahbj¼hd}rø+(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rù+}rú+(hTUhUjg$h`hahbjÁhd}rû+(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrü+jÇjü+uhnNhohhp]rý+(jÉ)rþ+}rÿ+(hTXinstall-includes: filename listhUjù+h`hahbjÍhd}r,(hi]r,Xpkg-field-install-includesr,ahh]hf]hg]hl]jщuhnM‰hohhp]r,(j¹)r,}r,(hTUhUjþ+h`hahbj¼hd}r,(hi]hh]hf]hg]hl]Uentries]r,(j×X%install-includes; package.cabal fieldj,UNtr,auhnM‰hohhp]ubjÙ)r ,}r ,(hTXinstall-includesr ,hUjþ+h`hahbjÜhd}r ,(jÑjÒhi]hh]hf]hg]hl]uhnM‰hohhp]r ,hyXinstall-includesr,…r,}r,(hTUh`NhnNhohhUj ,ubaubjâ)r,}r,(hTj[hUjþ+h`hahbjåhd}r,(jÑjÒhi]hh]hf]hg]hl]uhnM‰hohhp]r,hyX: r,…r,}r,(hTUh`NhnNhohhUj,ubaubja)r,}r,(hTX filename listhUjþ+h`hahbjdhd}r,(jÑjÒhi]hh]hf]hg]hl]uhnM‰hohhp]r,hyX filename listr,…r,}r,(hTUh`NhnNhohhUj,ubaubeubjê)r,}r ,(hTUhUjù+h`hahbjíhd}r!,(hf]hg]hh]hi]hl]uhnM‰hohhp]r",(h})r#,}r$,(hTX$A list of header files from this package to be installed into ``$libdir/includes`` when the package is installed. Files listed in :pkg-field:`install-includes` should be found in relative to the top of the source tree or relative to one of the directories listed in :pkg-field:`include-dirs`.hUj,h`hahbhhd}r%,(hf]hg]hh]hi]hl]uhnMshohhp]r&,(hyX>A list of header files from this package to be installed into r',…r(,}r),(hTX>A list of header files from this package to be installed into h`NhnNhohhUj#,ubhß)r*,}r+,(hTX``$libdir/includes``hd}r,,(hf]hg]hh]hi]hl]uhUj#,hp]r-,hyX$libdir/includesr.,…r/,}r0,(hTUhUj*,ubahbhçubhyX0 when the package is installed. Files listed in r1,…r2,}r3,(hTX0 when the package is installed. Files listed in h`NhnNhohhUj#,ubjk)r4,}r5,(hTX:pkg-field:`install-includes`r6,hUj#,h`hahbjohd}r7,(UreftypeX pkg-fieldjqˆjrXinstall-includesU refdomainXcabalr8,hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMshp]r9,hß)r:,}r;,(hTj6,hd}r<,(hf]hg]r=,(j|j8,Xcabal-pkg-fieldr>,ehh]hi]hl]uhUj4,hp]r?,hyXinstall-includesr@,…rA,}rB,(hTUhUj:,ubahbhçubaubhyXk should be found in relative to the top of the source tree or relative to one of the directories listed in rC,…rD,}rE,(hTXk should be found in relative to the top of the source tree or relative to one of the directories listed in h`NhnNhohhUj#,ubjk)rF,}rG,(hTX:pkg-field:`include-dirs`rH,hUj#,h`hahbjohd}rI,(UreftypeX pkg-fieldjqˆjrX include-dirsU refdomainXcabalrJ,hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMshp]rK,hß)rL,}rM,(hTjH,hd}rN,(hf]hg]rO,(j|jJ,Xcabal-pkg-fieldrP,ehh]hi]hl]uhUjF,hp]rQ,hyX include-dirsrR,…rS,}rT,(hTUhUjL,ubahbhçubaubhyX.…rU,}rV,(hTX.h`NhnNhohhUj#,ubeubh})rW,}rX,(hTX\:pkg-field:`install-includes` is typically used to name header files that contain prototypes for foreign imports used in Haskell code in this package, for which the C implementations are also provided with the package. For example, here is a ``.cabal`` file for a hypothetical ``bindings-clib`` package that bundles the C source code for ``clib``::hUj,h`hahbhhd}rY,(hf]hg]hh]hi]hl]uhnMyhohhp]rZ,(jk)r[,}r\,(hTX:pkg-field:`install-includes`r],hUjW,h`hahbjohd}r^,(UreftypeX pkg-fieldjqˆjrXinstall-includesU refdomainXcabalr_,hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMyhp]r`,hß)ra,}rb,(hTj],hd}rc,(hf]hg]rd,(j|j_,Xcabal-pkg-fieldre,ehh]hi]hl]uhUj[,hp]rf,hyXinstall-includesrg,…rh,}ri,(hTUhUja,ubahbhçubaubhyXÕ is typically used to name header files that contain prototypes for foreign imports used in Haskell code in this package, for which the C implementations are also provided with the package. For example, here is a rj,…rk,}rl,(hTXÕ is typically used to name header files that contain prototypes for foreign imports used in Haskell code in this package, for which the C implementations are also provided with the package. For example, here is a h`NhnNhohhUjW,ubhß)rm,}rn,(hTX ``.cabal``hd}ro,(hf]hg]hh]hi]hl]uhUjW,hp]rp,hyX.cabalrq,…rr,}rs,(hTUhUjm,ubahbhçubhyX file for a hypothetical rt,…ru,}rv,(hTX file for a hypothetical h`NhnNhohhUjW,ubhß)rw,}rx,(hTX``bindings-clib``hd}ry,(hf]hg]hh]hi]hl]uhUjW,hp]rz,hyX bindings-clibr{,…r|,}r},(hTUhUjw,ubahbhçubhyX, package that bundles the C source code for r~,…r,}r€,(hTX, package that bundles the C source code for h`NhnNhohhUjW,ubhß)r,}r‚,(hTX``clib``hd}rƒ,(hf]hg]hh]hi]hl]uhUjW,hp]r„,hyXclibr…,…r†,}r‡,(hTUhUj,ubahbhçubhyX:…rˆ,}r‰,(hTX:h`NhnNhohhUjW,ubeubjÌ)rŠ,}r‹,(hTXIinclude-dirs: cbits c-sources: clib.c install-includes: clib.hhUj,h`hahbjÏhd}rŒ,(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]r,hyXIinclude-dirs: cbits c-sources: clib.c install-includes: clib.hrŽ,…r,}r,(hTUhUjŠ,ubaubh})r‘,}r’,(hTXlNow any package that depends (directly or transitively) on the ``bindings-clib`` library can use ``clib.h``.hUj,h`hahbhhd}r“,(hf]hg]hh]hi]hl]uhnMƒhohhp]r”,(hyX?Now any package that depends (directly or transitively) on the r•,…r–,}r—,(hTX?Now any package that depends (directly or transitively) on the h`NhnNhohhUj‘,ubhß)r˜,}r™,(hTX``bindings-clib``hd}rš,(hf]hg]hh]hi]hl]uhUj‘,hp]r›,hyX bindings-clibrœ,…r,}rž,(hTUhUj˜,ubahbhçubhyX library can use rŸ,…r ,}r¡,(hTX library can use h`NhnNhohhUj‘,ubhß)r¢,}r£,(hTX ``clib.h``hd}r¤,(hf]hg]hh]hi]hl]uhUj‘,hp]r¥,hyXclib.hr¦,…r§,}r¨,(hTUhUj¢,ubahbhçubhyX.…r©,}rª,(hTX.h`NhnNhohhUj‘,ubeubh})r«,}r¬,(hTX·Note that in order for files listed in :pkg-field:`install-includes` to be usable when compiling the package itself, they need to be listed in the :pkg-field:`includes` field as well.hUj,h`hahbhhd}r­,(hf]hg]hh]hi]hl]uhnM†hohhp]r®,(hyX'Note that in order for files listed in r¯,…r°,}r±,(hTX'Note that in order for files listed in h`NhnNhohhUj«,ubjk)r²,}r³,(hTX:pkg-field:`install-includes`r´,hUj«,h`hahbjohd}rµ,(UreftypeX pkg-fieldjqˆjrXinstall-includesU refdomainXcabalr¶,hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnM†hp]r·,hß)r¸,}r¹,(hTj´,hd}rº,(hf]hg]r»,(j|j¶,Xcabal-pkg-fieldr¼,ehh]hi]hl]uhUj²,hp]r½,hyXinstall-includesr¾,…r¿,}rÀ,(hTUhUj¸,ubahbhçubaubhyXO to be usable when compiling the package itself, they need to be listed in the rÁ,…rÂ,}rÃ,(hTXO to be usable when compiling the package itself, they need to be listed in the h`NhnNhohhUj«,ubjk)rÄ,}rÅ,(hTX:pkg-field:`includes`rÆ,hUj«,h`hahbjohd}rÇ,(UreftypeX pkg-fieldjqˆjrXincludesU refdomainXcabalrÈ,hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnM†hp]rÉ,hß)rÊ,}rË,(hTjÆ,hd}rÌ,(hf]hg]rÍ,(j|jÈ,Xcabal-pkg-fieldrÎ,ehh]hi]hl]uhUjÄ,hp]rÏ,hyXincludesrÐ,…rÑ,}rÒ,(hTUhUjÊ,ubahbhçubaubhyX field as well.rÓ,…rÔ,}rÕ,(hTX field as well.h`NhnNhohhUj«,ubeubeubeubj¹)rÖ,}r×,(hTUhUjg$h`hahbj¼hd}rØ,(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÙ,}rÚ,(hTUhUjg$h`hahbjÁhd}rÛ,(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrÜ,jÇjÜ,uhnNhohhp]rÝ,(jÉ)rÞ,}rß,(hTXinclude-dirs: directory listhUjÙ,h`hahbjÍhd}rà,(hi]rá,Xpkg-field-include-dirsrâ,ahh]hf]hg]hl]jщuhnM“hohhp]rã,(j¹)rä,}rå,(hTUhUjÞ,h`hahbj¼hd}ræ,(hi]hh]hf]hg]hl]Uentries]rç,(j×X!include-dirs; package.cabal fieldjâ,UNtrè,auhnM“hohhp]ubjÙ)ré,}rê,(hTX include-dirsrë,hUjÞ,h`hahbjÜhd}rì,(jÑjÒhi]hh]hf]hg]hl]uhnM“hohhp]rí,hyX include-dirsrî,…rï,}rð,(hTUh`NhnNhohhUjé,ubaubjâ)rñ,}rò,(hTj[hUjÞ,h`hahbjåhd}ró,(jÑjÒhi]hh]hf]hg]hl]uhnM“hohhp]rô,hyX: rõ,…rö,}r÷,(hTUh`NhnNhohhUjñ,ubaubja)rø,}rù,(hTXdirectory listhUjÞ,h`hahbjdhd}rú,(jÑjÒhi]hh]hf]hg]hl]uhnM“hohhp]rû,hyXdirectory listrü,…rý,}rþ,(hTUh`NhnNhohhUjø,ubaubeubjê)rÿ,}r-(hTUhUjÙ,h`hahbjíhd}r-(hf]hg]hh]hi]hl]uhnM“hohhp]r-h})r-}r-(hTXžA list of directories to search for header files, when preprocessing with ``c2hs``, ``hsc2hs``, ``cpphs`` or the C preprocessor, and also when compiling via C. Directories can be absolute paths (e.g., for system directories) or paths that are relative to the top of the source tree. Cabal looks in these directories when attempting to locate files listed in :pkg-field:`includes` and :pkg-field:`install-includes`.hUjÿ,h`hahbhhd}r-(hf]hg]hh]hi]hl]uhnMŒhohhp]r-(hyXJA list of directories to search for header files, when preprocessing with r-…r-}r -(hTXJA list of directories to search for header files, when preprocessing with h`NhnNhohhUj-ubhß)r -}r -(hTX``c2hs``hd}r -(hf]hg]hh]hi]hl]uhUj-hp]r -hyXc2hsr-…r-}r-(hTUhUj -ubahbhçubhyX, r-…r-}r-(hTX, r-h`NhnNhohhUj-ubhß)r-}r-(hTX ``hsc2hs``hd}r-(hf]hg]hh]hi]hl]uhUj-hp]r-hyXhsc2hsr-…r-}r-(hTUhUj-ubahbhçubhyX, r-…r-}r-(hTj-hUj-ubhß)r-}r -(hTX ``cpphs``hd}r!-(hf]hg]hh]hi]hl]uhUj-hp]r"-hyXcpphsr#-…r$-}r%-(hTUhUj-ubahbhçubhyXý or the C preprocessor, and also when compiling via C. Directories can be absolute paths (e.g., for system directories) or paths that are relative to the top of the source tree. Cabal looks in these directories when attempting to locate files listed in r&-…r'-}r(-(hTXý or the C preprocessor, and also when compiling via C. Directories can be absolute paths (e.g., for system directories) or paths that are relative to the top of the source tree. Cabal looks in these directories when attempting to locate files listed in h`NhnNhohhUj-ubjk)r)-}r*-(hTX:pkg-field:`includes`r+-hUj-h`hahbjohd}r,-(UreftypeX pkg-fieldjqˆjrXincludesU refdomainXcabalr--hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMŒhp]r.-hß)r/-}r0-(hTj+-hd}r1-(hf]hg]r2-(j|j--Xcabal-pkg-fieldr3-ehh]hi]hl]uhUj)-hp]r4-hyXincludesr5-…r6-}r7-(hTUhUj/-ubahbhçubaubhyX and r8-…r9-}r:-(hTX and h`NhnNhohhUj-ubjk)r;-}r<-(hTX:pkg-field:`install-includes`r=-hUj-h`hahbjohd}r>-(UreftypeX pkg-fieldjqˆjrXinstall-includesU refdomainXcabalr?-hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnMŒhp]r@-hß)rA-}rB-(hTj=-hd}rC-(hf]hg]rD-(j|j?-Xcabal-pkg-fieldrE-ehh]hi]hl]uhUj;-hp]rF-hyXinstall-includesrG-…rH-}rI-(hTUhUjA-ubahbhçubaubhyX.…rJ-}rK-(hTX.h`NhnNhohhUj-ubeubaubeubj¹)rL-}rM-(hTUhUjg$h`hahbj¼hd}rN-(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rO-}rP-(hTUhUjg$h`hahbjÁhd}rQ-(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrR-jÇjR-uhnNhohhp]rS-(jÉ)rT-}rU-(hTXc-sources: filename listhUjO-h`hahbjÍhd}rV-(hi]rW-Xpkg-field-c-sourcesrX-ahh]hf]hg]hl]jщuhnM˜hohhp]rY-(j¹)rZ-}r[-(hTUhUjT-h`hahbj¼hd}r\-(hi]hh]hf]hg]hl]Uentries]r]-(j×Xc-sources; package.cabal fieldjX-UNtr^-auhnM˜hohhp]ubjÙ)r_-}r`-(hTX c-sourcesra-hUjT-h`hahbjÜhd}rb-(jÑjÒhi]hh]hf]hg]hl]uhnM˜hohhp]rc-hyX c-sourcesrd-…re-}rf-(hTUh`NhnNhohhUj_-ubaubjâ)rg-}rh-(hTj[hUjT-h`hahbjåhd}ri-(jÑjÒhi]hh]hf]hg]hl]uhnM˜hohhp]rj-hyX: rk-…rl-}rm-(hTUh`NhnNhohhUjg-ubaubja)rn-}ro-(hTX filename listhUjT-h`hahbjdhd}rp-(jÑjÒhi]hh]hf]hg]hl]uhnM˜hohhp]rq-hyX filename listrr-…rs-}rt-(hTUh`NhnNhohhUjn-ubaubeubjê)ru-}rv-(hTUhUjO-h`hahbjíhd}rw-(hf]hg]hh]hi]hl]uhnM˜hohhp]rx-h})ry-}rz-(hTXJA list of C source files to be compiled and linked with the Haskell files.r{-hUju-h`hahbhhd}r|-(hf]hg]hh]hi]hl]uhnM–hohhp]r}-hyXJA list of C source files to be compiled and linked with the Haskell files.r~-…r-}r€-(hTj{-h`NhnNhohhUjy-ubaubaubeubj¹)r-}r‚-(hTUhUjg$h`hahbj¼hd}rƒ-(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r„-}r…-(hTUhUjg$h`hahbjÁhd}r†-(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr‡-jÇj‡-uhnNhohhp]rˆ-(jÉ)r‰-}rŠ-(hTXjs-sources: filename listhUj„-h`hahbjÍhd}r‹-(hi]rŒ-Xpkg-field-js-sourcesr-ahh]hf]hg]hl]jщuhnMhohhp]rŽ-(j¹)r-}r-(hTUhUj‰-h`hahbj¼hd}r‘-(hi]hh]hf]hg]hl]Uentries]r’-(j×Xjs-sources; package.cabal fieldj-UNtr“-auhnMhohhp]ubjÙ)r”-}r•-(hTX js-sourcesr–-hUj‰-h`hahbjÜhd}r—-(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]r˜-hyX js-sourcesr™-…rš-}r›-(hTUh`NhnNhohhUj”-ubaubjâ)rœ-}r-(hTj[hUj‰-h`hahbjåhd}rž-(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]rŸ-hyX: r -…r¡-}r¢-(hTUh`NhnNhohhUjœ-ubaubja)r£-}r¤-(hTX filename listhUj‰-h`hahbjdhd}r¥-(jÑjÒhi]hh]hf]hg]hl]uhnMhohhp]r¦-hyX filename listr§-…r¨-}r©-(hTUh`NhnNhohhUj£-ubaubeubjê)rª-}r«-(hTUhUj„-h`hahbjíhd}r¬-(hf]hg]hh]hi]hl]uhnMhohhp]r­-h})r®-}r¯-(hTXdA list of JavaScript source files to be linked with the Haskell files (only for JavaScript targets).r°-hUjª-h`hahbhhd}r±-(hf]hg]hh]hi]hl]uhnM›hohhp]r²-hyXdA list of JavaScript source files to be linked with the Haskell files (only for JavaScript targets).r³-…r´-}rµ-(hTj°-h`NhnNhohhUj®-ubaubaubeubj¹)r¶-}r·-(hTUhUjg$h`hahbj¼hd}r¸-(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r¹-}rº-(hTUhUjg$h`hahbjÁhd}r»-(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr¼-jÇj¼-uhnNhohhp]r½-(jÉ)r¾-}r¿-(hTXextra-libraries: token listhUj¹-h`hahbjÍhd}rÀ-(hi]rÁ-Xpkg-field-extra-librariesrÂ-ahh]hf]hg]hl]jщuhnM¡hohhp]rÃ-(j¹)rÄ-}rÅ-(hTUhUj¾-h`hahbj¼hd}rÆ-(hi]hh]hf]hg]hl]Uentries]rÇ-(j×X$extra-libraries; package.cabal fieldjÂ-UNtrÈ-auhnM¡hohhp]ubjÙ)rÉ-}rÊ-(hTXextra-librariesrË-hUj¾-h`hahbjÜhd}rÌ-(jÑjÒhi]hh]hf]hg]hl]uhnM¡hohhp]rÍ-hyXextra-librariesrÎ-…rÏ-}rÐ-(hTUh`NhnNhohhUjÉ-ubaubjâ)rÑ-}rÒ-(hTj[hUj¾-h`hahbjåhd}rÓ-(jÑjÒhi]hh]hf]hg]hl]uhnM¡hohhp]rÔ-hyX: rÕ-…rÖ-}r×-(hTUh`NhnNhohhUjÑ-ubaubja)rØ-}rÙ-(hTX token listhUj¾-h`hahbjdhd}rÚ-(jÑjÒhi]hh]hf]hg]hl]uhnM¡hohhp]rÛ-hyX token listrÜ-…rÝ-}rÞ-(hTUh`NhnNhohhUjØ-ubaubeubjê)rß-}rà-(hTUhUj¹-h`hahbjíhd}rá-(hf]hg]hh]hi]hl]uhnM¡hohhp]râ-h})rã-}rä-(hTX'A list of extra libraries to link with.rå-hUjß-h`hahbhhd}ræ-(hf]hg]hh]hi]hl]uhnM hohhp]rç-hyX'A list of extra libraries to link with.rè-…ré-}rê-(hTjå-h`NhnNhohhUjã-ubaubaubeubj¹)rë-}rì-(hTUhUjg$h`hahbj¼hd}rí-(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rî-}rï-(hTUhUjg$h`hahbjÁhd}rð-(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrñ-jÇjñ-uhnNhohhp]rò-(jÉ)ró-}rô-(hTX extra-ghci-libraries: token listhUjî-h`hahbjÍhd}rõ-(hi]rö-Xpkg-field-extra-ghci-librariesr÷-ahh]hf]hg]hl]jщuhnM¦hohhp]rø-(j¹)rù-}rú-(hTUhUjó-h`hahbj¼hd}rû-(hi]hh]hf]hg]hl]Uentries]rü-(j×X)extra-ghci-libraries; package.cabal fieldj÷-UNtrý-auhnM¦hohhp]ubjÙ)rþ-}rÿ-(hTXextra-ghci-librariesr.hUjó-h`hahbjÜhd}r.(jÑjÒhi]hh]hf]hg]hl]uhnM¦hohhp]r.hyXextra-ghci-librariesr.…r.}r.(hTUh`NhnNhohhUjþ-ubaubjâ)r.}r.(hTj[hUjó-h`hahbjåhd}r.(jÑjÒhi]hh]hf]hg]hl]uhnM¦hohhp]r .hyX: r .…r .}r .(hTUh`NhnNhohhUj.ubaubja)r .}r.(hTX token listhUjó-h`hahbjdhd}r.(jÑjÒhi]hh]hf]hg]hl]uhnM¦hohhp]r.hyX token listr.…r.}r.(hTUh`NhnNhohhUj .ubaubeubjê)r.}r.(hTUhUjî-h`hahbjíhd}r.(hf]hg]hh]hi]hl]uhnM¦hohhp]r.h})r.}r.(hTXgA list of extra libraries to be used instead of 'extra-libraries' when the package is loaded with GHCi.r.hUj.h`hahbhhd}r.(hf]hg]hh]hi]hl]uhnM¤hohhp]r.hyXkA list of extra libraries to be used instead of ‘extra-libraries’ when the package is loaded with GHCi.r.…r.}r.(hTj.h`NhnNhohhUj.ubaubaubeubj¹)r .}r!.(hTUhUjg$h`hahbj¼hd}r".(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r#.}r$.(hTUhUjg$h`hahbjÁhd}r%.(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr&.jÇj&.uhnNhohhp]r'.(jÉ)r(.}r).(hTXextra-lib-dirs: directory listhUj#.h`hahbjÍhd}r*.(hi]r+.Xpkg-field-extra-lib-dirsr,.ahh]hf]hg]hl]jщuhnMªhohhp]r-.(j¹)r..}r/.(hTUhUj(.h`hahbj¼hd}r0.(hi]hh]hf]hg]hl]Uentries]r1.(j×X#extra-lib-dirs; package.cabal fieldj,.UNtr2.auhnMªhohhp]ubjÙ)r3.}r4.(hTXextra-lib-dirsr5.hUj(.h`hahbjÜhd}r6.(jÑjÒhi]hh]hf]hg]hl]uhnMªhohhp]r7.hyXextra-lib-dirsr8.…r9.}r:.(hTUh`NhnNhohhUj3.ubaubjâ)r;.}r<.(hTj[hUj(.h`hahbjåhd}r=.(jÑjÒhi]hh]hf]hg]hl]uhnMªhohhp]r>.hyX: r?.…r@.}rA.(hTUh`NhnNhohhUj;.ubaubja)rB.}rC.(hTXdirectory listhUj(.h`hahbjdhd}rD.(jÑjÒhi]hh]hf]hg]hl]uhnMªhohhp]rE.hyXdirectory listrF.…rG.}rH.(hTUh`NhnNhohhUjB.ubaubeubjê)rI.}rJ.(hTUhUj#.h`hahbjíhd}rK.(hf]hg]hh]hi]hl]uhnMªhohhp]rL.h})rM.}rN.(hTX.A list of directories to search for libraries.rO.hUjI.h`hahbhhd}rP.(hf]hg]hh]hi]hl]uhnM©hohhp]rQ.hyX.A list of directories to search for libraries.rR.…rS.}rT.(hTjO.h`NhnNhohhUjM.ubaubaubeubj¹)rU.}rV.(hTUhUjg$h`hahbj¼hd}rW.(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rX.}rY.(hTUhUjg$h`hahbjÁhd}rZ.(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr[.jÇj[.uhnNhohhp]r\.(jÉ)r].}r^.(hTXcc-options: token listhUjX.h`hahbjÍhd}r_.(hi]r`.Xpkg-field-cc-optionsra.ahh]hf]hg]hl]jщuhnM°hohhp]rb.(j¹)rc.}rd.(hTUhUj].h`hahbj¼hd}re.(hi]hh]hf]hg]hl]Uentries]rf.(j×Xcc-options; package.cabal fieldja.UNtrg.auhnM°hohhp]ubjÙ)rh.}ri.(hTX cc-optionsrj.hUj].h`hahbjÜhd}rk.(jÑjÒhi]hh]hf]hg]hl]uhnM°hohhp]rl.hyX cc-optionsrm.…rn.}ro.(hTUh`NhnNhohhUjh.ubaubjâ)rp.}rq.(hTj[hUj].h`hahbjåhd}rr.(jÑjÒhi]hh]hf]hg]hl]uhnM°hohhp]rs.hyX: rt.…ru.}rv.(hTUh`NhnNhohhUjp.ubaubja)rw.}rx.(hTX token listhUj].h`hahbjdhd}ry.(jÑjÒhi]hh]hf]hg]hl]uhnM°hohhp]rz.hyX token listr{.…r|.}r}.(hTUh`NhnNhohhUjw.ubaubeubjê)r~.}r.(hTUhUjX.h`hahbjíhd}r€.(hf]hg]hh]hi]hl]uhnM°hohhp]r.h})r‚.}rƒ.(hTXÇCommand-line arguments to be passed to the C compiler. Since the arguments are compiler-dependent, this field is more useful with the setup described in the section on `system-dependent parameters`_.hUj~.h`hahbhhd}r„.(hf]hg]hh]hi]hl]uhnM­hohhp]r….(hyX¨Command-line arguments to be passed to the C compiler. Since the arguments are compiler-dependent, this field is more useful with the setup described in the section on r†.…r‡.}rˆ.(hTX¨Command-line arguments to be passed to the C compiler. Since the arguments are compiler-dependent, this field is more useful with the setup described in the section on h`NhnNhohhUj‚.ubj?)r‰.}rŠ.(hTX`system-dependent parameters`_jBKhUj‚.hbjChd}r‹.(UnameXsystem-dependent parametershi]hh]hf]hg]hl]jEjuhp]rŒ.hyXsystem-dependent parametersr.…rŽ.}r.(hTUhUj‰.ubaubhyX.…r.}r‘.(hTX.h`NhnNhohhUj‚.ubeubaubeubj¹)r’.}r“.(hTUhUjg$h`hahbj¼hd}r”.(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r•.}r–.(hTUhUjg$h`hahbjÁhd}r—.(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr˜.jÇj˜.uhnNhohhp]r™.(jÉ)rš.}r›.(hTXcpp-options: token listhUj•.h`hahbjÍhd}rœ.(hi]r.Xpkg-field-cpp-optionsrž.ahh]hf]hg]hl]jщuhnM¶hohhp]rŸ.(j¹)r .}r¡.(hTUhUjš.h`hahbj¼hd}r¢.(hi]hh]hf]hg]hl]Uentries]r£.(j×X cpp-options; package.cabal fieldjž.UNtr¤.auhnM¶hohhp]ubjÙ)r¥.}r¦.(hTX cpp-optionsr§.hUjš.h`hahbjÜhd}r¨.(jÑjÒhi]hh]hf]hg]hl]uhnM¶hohhp]r©.hyX cpp-optionsrª.…r«.}r¬.(hTUh`NhnNhohhUj¥.ubaubjâ)r­.}r®.(hTj[hUjš.h`hahbjåhd}r¯.(jÑjÒhi]hh]hf]hg]hl]uhnM¶hohhp]r°.hyX: r±.…r².}r³.(hTUh`NhnNhohhUj­.ubaubja)r´.}rµ.(hTX token listhUjš.h`hahbjdhd}r¶.(jÑjÒhi]hh]hf]hg]hl]uhnM¶hohhp]r·.hyX token listr¸.…r¹.}rº.(hTUh`NhnNhohhUj´.ubaubeubjê)r».}r¼.(hTUhUj•.h`hahbjíhd}r½.(hf]hg]hh]hi]hl]uhnM¶hohhp]r¾.h})r¿.}rÀ.(hTXÁCommand-line arguments for pre-processing Haskell code. Applies to haskell source and other pre-processed Haskell source like .hsc .chs. Does not apply to C code, that's what cc-options is for.rÁ.hUj».h`hahbhhd}rÂ.(hf]hg]hh]hi]hl]uhnM³hohhp]rÃ.hyXÃCommand-line arguments for pre-processing Haskell code. Applies to haskell source and other pre-processed Haskell source like .hsc .chs. Does not apply to C code, that’s what cc-options is for.rÄ.…rÅ.}rÆ.(hTjÁ.h`NhnNhohhUj¿.ubaubaubeubj¹)rÇ.}rÈ.(hTUhUjg$h`hahbj¼hd}rÉ.(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÊ.}rË.(hTUhUjg$h`hahbjÁhd}rÌ.(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrÍ.jÇjÍ.uhnNhohhp]rÎ.(jÉ)rÏ.}rÐ.(hTXld-options: token listhUjÊ.h`hahbjÍhd}rÑ.(hi]rÒ.Xpkg-field-ld-optionsrÓ.ahh]hf]hg]hl]jщuhnM¼hohhp]rÔ.(j¹)rÕ.}rÖ.(hTUhUjÏ.h`hahbj¼hd}r×.(hi]hh]hf]hg]hl]Uentries]rØ.(j×Xld-options; package.cabal fieldjÓ.UNtrÙ.auhnM¼hohhp]ubjÙ)rÚ.}rÛ.(hTX ld-optionsrÜ.hUjÏ.h`hahbjÜhd}rÝ.(jÑjÒhi]hh]hf]hg]hl]uhnM¼hohhp]rÞ.hyX ld-optionsrß.…rà.}rá.(hTUh`NhnNhohhUjÚ.ubaubjâ)râ.}rã.(hTj[hUjÏ.h`hahbjåhd}rä.(jÑjÒhi]hh]hf]hg]hl]uhnM¼hohhp]rå.hyX: ræ.…rç.}rè.(hTUh`NhnNhohhUjâ.ubaubja)ré.}rê.(hTX token listhUjÏ.h`hahbjdhd}rë.(jÑjÒhi]hh]hf]hg]hl]uhnM¼hohhp]rì.hyX token listrí.…rî.}rï.(hTUh`NhnNhohhUjé.ubaubeubjê)rð.}rñ.(hTUhUjÊ.h`hahbjíhd}rò.(hf]hg]hh]hi]hl]uhnM¼hohhp]ró.h})rô.}rõ.(hTXÃCommand-line arguments to be passed to the linker. Since the arguments are compiler-dependent, this field is more useful with the setup described in the section on `system-dependent parameters`_.hUjð.h`hahbhhd}rö.(hf]hg]hh]hi]hl]uhnM¹hohhp]r÷.(hyX¤Command-line arguments to be passed to the linker. Since the arguments are compiler-dependent, this field is more useful with the setup described in the section on rø.…rù.}rú.(hTX¤Command-line arguments to be passed to the linker. Since the arguments are compiler-dependent, this field is more useful with the setup described in the section on h`NhnNhohhUjô.ubj?)rû.}rü.(hTX`system-dependent parameters`_jBKhUjô.hbjChd}rý.(UnameXsystem-dependent parametershi]hh]hf]hg]hl]jEjuhp]rþ.hyXsystem-dependent parametersrÿ.…r/}r/(hTUhUjû.ubaubhyX.…r/}r/(hTX.h`NhnNhohhUjô.ubeubaubeubj¹)r/}r/(hTUhUjg$h`hahbj¼hd}r/(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r/}r/(hTUhUjg$h`hahbjÁhd}r /(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr /jÇj /uhnNhohhp]r /(jÉ)r /}r /(hTXpkgconfig-depends: package listhUj/h`hahbjÍhd}r/(hi]r/Xpkg-field-pkgconfig-dependsr/ahh]hf]hg]hl]jщuhnMÌhohhp]r/(j¹)r/}r/(hTUhUj /h`hahbj¼hd}r/(hi]hh]hf]hg]hl]Uentries]r/(j×X&pkgconfig-depends; package.cabal fieldj/UNtr/auhnMÌhohhp]ubjÙ)r/}r/(hTXpkgconfig-dependsr/hUj /h`hahbjÜhd}r/(jÑjÒhi]hh]hf]hg]hl]uhnMÌhohhp]r/hyXpkgconfig-dependsr/…r/}r/(hTUh`NhnNhohhUj/ubaubjâ)r/}r /(hTj[hUj /h`hahbjåhd}r!/(jÑjÒhi]hh]hf]hg]hl]uhnMÌhohhp]r"/hyX: r#/…r$/}r%/(hTUh`NhnNhohhUj/ubaubja)r&/}r'/(hTX package listhUj /h`hahbjdhd}r(/(jÑjÒhi]hh]hf]hg]hl]uhnMÌhohhp]r)/hyX package listr*/…r+/}r,/(hTUh`NhnNhohhUj&/ubaubeubjê)r-/}r./(hTUhUj/h`hahbjíhd}r//(hf]hg]hh]hi]hl]uhnMÌhohhp]r0/(h})r1/}r2/(hTX´A list of `pkg-config `__ packages, needed to build this package. They can be annotated with versions, e.g. ``gtk+-2.0 >= 2.10, cairo >= 1.0``. If no version constraint is specified, any version is assumed to be acceptable. Cabal uses ``pkg-config`` to find if the packages are available on the system and to find the extra compilation and linker options needed to use the packages.hUj-/h`hahbhhd}r3/(hf]hg]hh]hi]hl]uhnM¿hohhp]r4/(hyX A list of r5/…r6/}r7/(hTX A list of h`NhnNhohhUj1/ubj?)r8/}r9/(hTXE`pkg-config `__hd}r:/(UnameX pkg-configj~X4http://www.freedesktop.org/wiki/Software/pkg-config/hi]hh]hf]hg]hl]uhUj1/hp]r;/hyX pkg-configr/(hTUhUj8/ubahbjCubhyXS packages, needed to build this package. They can be annotated with versions, e.g. r?/…r@/}rA/(hTXS packages, needed to build this package. They can be annotated with versions, e.g. h`NhnNhohhUj1/ubhß)rB/}rC/(hTX"``gtk+-2.0 >= 2.10, cairo >= 1.0``hd}rD/(hf]hg]hh]hi]hl]uhUj1/hp]rE/hyXgtk+-2.0 >= 2.10, cairo >= 1.0rF/…rG/}rH/(hTUhUjB/ubahbhçubhyX]. If no version constraint is specified, any version is assumed to be acceptable. Cabal uses rI/…rJ/}rK/(hTX]. If no version constraint is specified, any version is assumed to be acceptable. Cabal uses h`NhnNhohhUj1/ubhß)rL/}rM/(hTX``pkg-config``hd}rN/(hf]hg]hh]hi]hl]uhUj1/hp]rO/hyX pkg-configrP/…rQ/}rR/(hTUhUjL/ubahbhçubhyX… to find if the packages are available on the system and to find the extra compilation and linker options needed to use the packages.rS/…rT/}rU/(hTX… to find if the packages are available on the system and to find the extra compilation and linker options needed to use the packages.h`NhnNhohhUj1/ubeubh})rV/}rW/(hTXàIf you need to bind to a C library that supports ``pkg-config`` (use ``pkg-config --list-all`` to find out if it is supported) then it is much preferable to use this field rather than hard code options into the other fields.hUj-/h`hahbhhd}rX/(hf]hg]hh]hi]hl]uhnMÈhohhp]rY/(hyX1If you need to bind to a C library that supports rZ/…r[/}r\/(hTX1If you need to bind to a C library that supports h`NhnNhohhUjV/ubhß)r]/}r^/(hTX``pkg-config``hd}r_/(hf]hg]hh]hi]hl]uhUjV/hp]r`/hyX pkg-configra/…rb/}rc/(hTUhUj]/ubahbhçubhyX (use rd/…re/}rf/(hTX (use h`NhnNhohhUjV/ubhß)rg/}rh/(hTX``pkg-config --list-all``hd}ri/(hf]hg]hh]hi]hl]uhUjV/hp]rj/hyXpkg-config --list-allrk/…rl/}rm/(hTUhUjg/ubahbhçubhyX‚ to find out if it is supported) then it is much preferable to use this field rather than hard code options into the other fields.rn/…ro/}rp/(hTX‚ to find out if it is supported) then it is much preferable to use this field rather than hard code options into the other fields.h`NhnNhohhUjV/ubeubeubeubj¹)rq/}rr/(hTUhUjg$h`hahbj¼hd}rs/(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rt/}ru/(hTUhUjg$h`hahbjÁhd}rv/(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrw/jÇjw/uhnNhohhp]rx/(jÉ)ry/}rz/(hTXframeworks: token listhUjt/h`hahbjÍhd}r{/(hi]r|/Xpkg-field-frameworksr}/ahh]hf]hg]hl]jщuhnMÒhohhp]r~/(j¹)r/}r€/(hTUhUjy/h`hahbj¼hd}r/(hi]hh]hf]hg]hl]Uentries]r‚/(j×Xframeworks; package.cabal fieldj}/UNtrƒ/auhnMÒhohhp]ubjÙ)r„/}r…/(hTX frameworksr†/hUjy/h`hahbjÜhd}r‡/(jÑjÒhi]hh]hf]hg]hl]uhnMÒhohhp]rˆ/hyX frameworksr‰/…rŠ/}r‹/(hTUh`NhnNhohhUj„/ubaubjâ)rŒ/}r/(hTj[hUjy/h`hahbjåhd}rŽ/(jÑjÒhi]hh]hf]hg]hl]uhnMÒhohhp]r/hyX: r/…r‘/}r’/(hTUh`NhnNhohhUjŒ/ubaubja)r“/}r”/(hTX token listhUjy/h`hahbjdhd}r•/(jÑjÒhi]hh]hf]hg]hl]uhnMÒhohhp]r–/hyX token listr—/…r˜/}r™/(hTUh`NhnNhohhUj“/ubaubeubjê)rš/}r›/(hTUhUjt/h`hahbjíhd}rœ/(hf]hg]hh]hi]hl]uhnMÒhohhp]r/h})rž/}rŸ/(hTX¥On Darwin/MacOS X, a list of frameworks to link to. See Apple's developer documentation for more details on frameworks. This entry is ignored on all other platforms.r /hUjš/h`hahbhhd}r¡/(hf]hg]hh]hi]hl]uhnMÏhohhp]r¢/hyX§On Darwin/MacOS X, a list of frameworks to link to. See Apple’s developer documentation for more details on frameworks. This entry is ignored on all other platforms.r£/…r¤/}r¥/(hTj /h`NhnNhohhUjž/ubaubaubeubj¹)r¦/}r§/(hTUhUjg$h`hahbj¼hd}r¨/(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r©/}rª/(hTUhUjg$h`hahbjÁhd}r«/(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr¬/jÇj¬/uhnNhohhp]r­/(jÉ)r®/}r¯/(hTX%extra-frameworks-dirs: directory listhUj©/h`hahbjÍhd}r°/(hi]r±/Xpkg-field-extra-frameworks-dirsr²/ahh]hf]hg]hl]jщuhnM×hohhp]r³/(j¹)r´/}rµ/(hTUhUj®/h`hahbj¼hd}r¶/(hi]hh]hf]hg]hl]Uentries]r·/(j×X*extra-frameworks-dirs; package.cabal fieldj²/UNtr¸/auhnM×hohhp]ubjÙ)r¹/}rº/(hTXextra-frameworks-dirsr»/hUj®/h`hahbjÜhd}r¼/(jÑjÒhi]hh]hf]hg]hl]uhnM×hohhp]r½/hyXextra-frameworks-dirsr¾/…r¿/}rÀ/(hTUh`NhnNhohhUj¹/ubaubjâ)rÁ/}rÂ/(hTj[hUj®/h`hahbjåhd}rÃ/(jÑjÒhi]hh]hf]hg]hl]uhnM×hohhp]rÄ/hyX: rÅ/…rÆ/}rÇ/(hTUh`NhnNhohhUjÁ/ubaubja)rÈ/}rÉ/(hTXdirectory listhUj®/h`hahbjdhd}rÊ/(jÑjÒhi]hh]hf]hg]hl]uhnM×hohhp]rË/hyXdirectory listrÌ/…rÍ/}rÎ/(hTUh`NhnNhohhUjÈ/ubaubeubjê)rÏ/}rÐ/(hTUhUj©/h`hahbjíhd}rÑ/(hf]hg]hh]hi]hl]uhnM×hohhp]rÒ/h})rÓ/}rÔ/(hTXpOn Darwin/MacOS X, a list of directories to search for frameworks. This entry is ignored on all other platforms.rÕ/hUjÏ/h`hahbhhd}rÖ/(hf]hg]hh]hi]hl]uhnMÕhohhp]r×/hyXpOn Darwin/MacOS X, a list of directories to search for frameworks. This entry is ignored on all other platforms.rØ/…rÙ/}rÚ/(hTjÕ/h`NhnNhohhUjÓ/ubaubaubeubeubhV)rÛ/}rÜ/(hTUhYKhUh\h`hahbhchd}rÝ/(hf]hg]hh]hi]rÞ/jœahl]rß/hLauhnMÙhohhp]rà/(hr)rá/}râ/(hTXConfigurationsrã/hUjÛ/h`hahbhvhd}rä/(hf]hg]hh]hi]hl]uhnMÙhohhp]rå/hyXConfigurationsræ/…rç/}rè/(hTjã/h`NhnNhohhUjá/ubaubh})ré/}rê/(hTXVLibrary and executable sections may include conditional blocks, which test for various system parameters and configuration flags. The flags mechanism is rather generic, but most of the time a flag represents certain feature, that can be switched on or off by the package user. Here is an example package description file using configurations:rë/hUjÛ/h`hahbhhd}rì/(hf]hg]hh]hi]hl]uhnMÛhohhp]rí/hyXVLibrary and executable sections may include conditional blocks, which test for various system parameters and configuration flags. The flags mechanism is rather generic, but most of the time a flag represents certain feature, that can be switched on or off by the package user. Here is an example package description file using configurations:rî/…rï/}rð/(hTjë/h`NhnNhohhUjé/ubaubhV)rñ/}rò/(hTUhYKhUjÛ/h`hahbhchd}ró/(hf]rô/jFahg]hh]hi]rõ/Uid2rö/ahl]uhnMâhohhp]r÷/(hr)rø/}rù/(hTX?Example: A package containing a library and executable programsrú/hUjñ/h`hahbhvhd}rû/(hf]hg]hh]hi]hl]uhnMâhohhp]rü/hyX?Example: A package containing a library and executable programsrý/…rþ/}rÿ/(hTjú/h`NhnNhohhUjø/ubaubjÌ)r0}r0(hTX^Name: Test1 Version: 0.0.1 Cabal-Version: >= 1.2 License: BSD3 Author: Jane Doe Synopsis: Test package to test configurations Category: Example Flag Debug Description: Enable debug support Default: False Flag WebFrontend Description: Include API for web frontend. -- Cabal checks if the configuration is possible, first -- with this flag set to True and if not it tries with False Library Build-Depends: base Exposed-Modules: Testing.Test1 Extensions: CPP if flag(debug) GHC-Options: -DDEBUG if !os(windows) CC-Options: "-DDEBUG" else CC-Options: "-DNDEBUG" if flag(webfrontend) Build-Depends: cgi > 0.42 Other-Modules: Testing.WebStuff Executable test1 Main-is: T1.hs Other-Modules: Testing.Test1 Build-Depends: base if flag(debug) CC-Options: "-DDEBUG" GHC-Options: -DDEBUGhUjñ/h`hahbjÏhd}r0(jÑjÒhi]hh]hf]hg]hl]uhnMæhohhp]r0hyX^Name: Test1 Version: 0.0.1 Cabal-Version: >= 1.2 License: BSD3 Author: Jane Doe Synopsis: Test package to test configurations Category: Example Flag Debug Description: Enable debug support Default: False Flag WebFrontend Description: Include API for web frontend. -- Cabal checks if the configuration is possible, first -- with this flag set to True and if not it tries with False Library Build-Depends: base Exposed-Modules: Testing.Test1 Extensions: CPP if flag(debug) GHC-Options: -DDEBUG if !os(windows) CC-Options: "-DDEBUG" else CC-Options: "-DNDEBUG" if flag(webfrontend) Build-Depends: cgi > 0.42 Other-Modules: Testing.WebStuff Executable test1 Main-is: T1.hs Other-Modules: Testing.Test1 Build-Depends: base if flag(debug) CC-Options: "-DDEBUG" GHC-Options: -DDEBUGr0…r0}r0(hTUhUj0ubaubeubhV)r0}r0(hTUhUjÛ/h`hahbhchd}r 0(hf]hg]hh]hi]r 0Ulayoutr 0ahl]r 0h:auhnMhohhp]r 0(hr)r0}r0(hTXLayoutr0hUj0h`hahbhvhd}r0(hf]hg]hh]hi]hl]uhnMhohhp]r0hyXLayoutr0…r0}r0(hTj0h`NhnNhohhUj0ubaubh})r0}r0(hTX#Flags, conditionals, library and executable sections use layout to indicate structure. This is very similar to the Haskell layout rule. Entries in a section have to all be indented to the same level which must be more than the section header. Tabs are not allowed to be used for indentation.r0hUj0h`hahbhhd}r0(hf]hg]hh]hi]hl]uhnMhohhp]r0hyX#Flags, conditionals, library and executable sections use layout to indicate structure. This is very similar to the Haskell layout rule. Entries in a section have to all be indented to the same level which must be more than the section header. Tabs are not allowed to be used for indentation.r0…r0}r0(hTj0h`NhnNhohhUj0ubaubh})r0}r0(hTX As an alternative to using layout you can also use explicit braces ``{}``. In this case the indentation of entries in a section does not matter, though different fields within a block must be on different lines. Here is a bit of the above example again, using braces:hUj0h`hahbhhd}r 0(hf]hg]hh]hi]hl]uhnMhohhp]r!0(hyXCAs an alternative to using layout you can also use explicit braces r"0…r#0}r$0(hTXCAs an alternative to using layout you can also use explicit braces h`NhnNhohhUj0ubhß)r%0}r&0(hTX``{}``hd}r'0(hf]hg]hh]hi]hl]uhUj0hp]r(0hyX{}r)0…r*0}r+0(hTUhUj%0ubahbhçubhyXÂ. In this case the indentation of entries in a section does not matter, though different fields within a block must be on different lines. Here is a bit of the above example again, using braces:r,0…r-0}r.0(hTXÂ. In this case the indentation of entries in a section does not matter, though different fields within a block must be on different lines. Here is a bit of the above example again, using braces:h`NhnNhohhUj0ubeubeubhV)r/0}r00(hTUhUjÛ/h`hahbhchd}r10(hf]hg]hh]hi]r20U@example-using-explicit-braces-rather-than-indentation-for-layoutr30ahl]r40h4auhnMhohhp]r50(hr)r60}r70(hTXAExample: Using explicit braces rather than indentation for layoutr80hUj/0h`hahbhvhd}r90(hf]hg]hh]hi]hl]uhnMhohhp]r:0hyXAExample: Using explicit braces rather than indentation for layoutr;0…r<0}r=0(hTj80h`NhnNhohhUj60ubaubjÌ)r>0}r?0(hTXÈName: Test1 Version: 0.0.1 Cabal-Version: >= 1.2 License: BSD3 Author: Jane Doe Synopsis: Test package to test configurations Category: Example Flag Debug { Description: Enable debug support Default: False } Library { Build-Depends: base Exposed-Modules: Testing.Test1 Extensions: CPP if flag(debug) { GHC-Options: -DDEBUG if !os(windows) { CC-Options: "-DDEBUG" } else { CC-Options: "-DNDEBUG" } } }hUj/0h`hahbjÏhd}r@0(jÑjÒhi]hh]hf]hg]hl]uhnM#hohhp]rA0hyXÈName: Test1 Version: 0.0.1 Cabal-Version: >= 1.2 License: BSD3 Author: Jane Doe Synopsis: Test package to test configurations Category: Example Flag Debug { Description: Enable debug support Default: False } Library { Build-Depends: base Exposed-Modules: Testing.Test1 Extensions: CPP if flag(debug) { GHC-Options: -DDEBUG if !os(windows) { CC-Options: "-DDEBUG" } else { CC-Options: "-DNDEBUG" } } }rB0…rC0}rD0(hTUhUj>0ubaubeubhV)rE0}rF0(hTUhUjÛ/h`hahbhchd}rG0(hf]hg]hh]hi]rH0Uconfiguration-flagsrI0ahl]rJ0h'auhnM?hohhp]rK0(hr)rL0}rM0(hTXConfiguration FlagsrN0hUjE0h`hahbhvhd}rO0(hf]hg]hh]hi]hl]uhnM?hohhp]rP0hyXConfiguration FlagsrQ0…rR0}rS0(hTjN0h`NhnNhohhUjL0ubaubj¹)rT0}rU0(hTUhUjE0h`hahbj¼hd}rV0(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rW0}rX0(hTUhUjE0h`hahbjÁhd}rY0(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-sectionrZ0jÇjZ0uhnNhohhp]r[0(jÉ)r\0}r]0(hTX flag namehUjW0h`hahbjÍhd}r^0(hi]r_0Xpkg-section-flag-flagr`0ahh]hf]hg]hl]jщuhnNhohhp]ra0(j¹)rb0}rc0(hTUhUj\0h`hahbj¼hd}rd0(hi]hh]hf]hg]hl]Uentries]re0(j×X flag:flag; package.cabal sectionj`0UNtrf0auhnNhohhp]ubjÙ)rg0}rh0(hTXflagri0hUj\0h`hahbjÜhd}rj0(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rk0hyXflagrl0…rm0}rn0(hTUh`NhnNhohhUjg0ubaubjâ)ro0}rp0(hTU hUj\0h`hahbjåhd}rq0(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rr0hyX …rs0}rt0(hTUh`NhnNhohhUjo0ubaubja)ru0}rv0(hTXnamehUj\0h`hahbjdhd}rw0(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rx0hyXnamery0…rz0}r{0(hTUh`NhnNhohhUju0ubaubeubjê)r|0}r}0(hTUhUjW0h`hahbjíhd}r~0(hf]hg]hh]hi]hl]uhnNhohhp]r0h})r€0}r0(hTXHFlag section declares a flag which can be used in `conditional blocks`_.hUj|0h`hahbhhd}r‚0(hf]hg]hh]hi]hl]uhnMDhohhp]rƒ0(hyX2Flag section declares a flag which can be used in r„0…r…0}r†0(hTX2Flag section declares a flag which can be used in h`NhnNhohhUj€0ubj?)r‡0}rˆ0(hTX`conditional blocks`_jBKhUj€0hbjChd}r‰0(UnameXconditional blockshi]hh]hf]hg]hl]jEUconditional-blocksrŠ0uhp]r‹0hyXconditional blocksrŒ0…r0}rŽ0(hTUhUj‡0ubaubhyX.…r0}r0(hTX.h`NhnNhohhUj€0ubeubaubeubh})r‘0}r’0(hTXaFlag names are case-insensitive and must match ``[[:alnum:]_][[:alnum:]_-]*`` regular expression.hUjE0h`hahbhhd}r“0(hf]hg]hh]hi]hl]uhnMFhohhp]r”0(hyX/Flag names are case-insensitive and must match r•0…r–0}r—0(hTX/Flag names are case-insensitive and must match h`NhnNhohhUj‘0ubhß)r˜0}r™0(hTX``[[:alnum:]_][[:alnum:]_-]*``hd}rš0(hf]hg]hh]hi]hl]uhUj‘0hp]r›0hyX[[:alnum:]_][[:alnum:]_-]*rœ0…r0}rž0(hTUhUj˜0ubahbhçubhyX regular expression.rŸ0…r 0}r¡0(hTX regular expression.h`NhnNhohhUj‘0ubeubhë)r¢0}r£0(hTXHHackage accepts ASCII-only flags, ``[a-zA-Z0-9_][a-zA-Z0-9_-]*`` regexp.r¤0hUjE0h`hahbhîhd}r¥0(hf]hg]hh]hi]hl]uhnNhohhp]r¦0h})r§0}r¨0(hTj¤0hUj¢0h`hahbhhd}r©0(hf]hg]hh]hi]hl]uhnMKhp]rª0(hyX"Hackage accepts ASCII-only flags, r«0…r¬0}r­0(hTX"Hackage accepts ASCII-only flags, hUj§0ubhß)r®0}r¯0(hTX``[a-zA-Z0-9_][a-zA-Z0-9_-]*``hd}r°0(hf]hg]hh]hi]hl]uhUj§0hp]r±0hyX[a-zA-Z0-9_][a-zA-Z0-9_-]*r²0…r³0}r´0(hTUhUj®0ubahbhçubhyX regexp.rµ0…r¶0}r·0(hTX regexp.hUj§0ubeubaubj¹)r¸0}r¹0(hTUhUjE0h`hahbj¼hd}rº0(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r»0}r¼0(hTUhUjE0h`hahbjÁhd}r½0(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr¾0jÇj¾0uhnNhohhp]r¿0(jÉ)rÀ0}rÁ0(hTXdescription: freeformhUj»0h`hahbjÍhd}rÂ0(hi]rÃ0Xpkg-field-flag-descriptionrÄ0ahh]hf]hg]hl]jщuhnMPhohhp]rÅ0(j¹)rÆ0}rÇ0(hTUhUjÀ0h`hahbj¼hd}rÈ0(hi]hh]hf]hg]hl]Uentries]rÉ0(j×X%flag:description; package.cabal fieldjÄ0UNtrÊ0auhnMPhohhp]ubjÙ)rË0}rÌ0(hTX descriptionrÍ0hUjÀ0h`hahbjÜhd}rÎ0(jÑjÒhi]hh]hf]hg]hl]uhnMPhohhp]rÏ0hyX descriptionrÐ0…rÑ0}rÒ0(hTUh`NhnNhohhUjË0ubaubjâ)rÓ0}rÔ0(hTj[hUjÀ0h`hahbjåhd}rÕ0(jÑjÒhi]hh]hf]hg]hl]uhnMPhohhp]rÖ0hyX: r×0…rØ0}rÙ0(hTUh`NhnNhohhUjÓ0ubaubja)rÚ0}rÛ0(hTXfreeformhUjÀ0h`hahbjdhd}rÜ0(jÑjÒhi]hh]hf]hg]hl]uhnMPhohhp]rÝ0hyXfreeformrÞ0…rß0}rà0(hTUh`NhnNhohhUjÚ0ubaubeubjê)rá0}râ0(hTUhUj»0h`hahbjíhd}rã0(hf]hg]hh]hi]hl]uhnMPhohhp]rä0h})rå0}ræ0(hTXThe description of this flag.rç0hUjá0h`hahbhhd}rè0(hf]hg]hh]hi]hl]uhnMOhohhp]ré0hyXThe description of this flag.rê0…rë0}rì0(hTjç0h`NhnNhohhUjå0ubaubaubeubj¹)rí0}rî0(hTUhUjE0h`Nhbj¼hd}rï0(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rð0}rñ0(hTUhUjE0h`NhbjÁhd}rò0(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldró0jÇjó0uhnNhohhp]rô0(jÉ)rõ0}rö0(hTXdefault: booleanhUjð0h`hahbjÍhd}r÷0(hi]rø0Xpkg-field-flag-defaultrù0ahh]hf]hg]hl]jщuhnM`hohhp]rú0(j¹)rû0}rü0(hTUhUjõ0h`hahbj¼hd}rý0(hi]hh]hf]hg]hl]Uentries]rþ0(j×X!flag:default; package.cabal fieldjù0UNtrÿ0auhnM`hohhp]ubjÙ)r1}r1(hTXdefaultr1hUjõ0h`hahbjÜhd}r1(jÑjÒhi]hh]hf]hg]hl]uhnM`hohhp]r1hyXdefaultr1…r1}r1(hTUh`NhnNhohhUj1ubaubjâ)r1}r 1(hTj[hUjõ0h`hahbjåhd}r 1(jÑjÒhi]hh]hf]hg]hl]uhnM`hohhp]r 1hyX: r 1…r 1}r1(hTUh`NhnNhohhUj1ubaubja)r1}r1(hTXbooleanhUjõ0h`hahbjdhd}r1(jÑjÒhi]hh]hf]hg]hl]uhnM`hohhp]r1hyXbooleanr1…r1}r1(hTUh`NhnNhohhUj1ubaubeubjê)r1}r1(hTUhUjð0h`hahbjíhd}r1(hf]hg]hh]hi]hl]uhnM`hohhp]r1(jð)r1}r1(hTUhUj1h`Nhbjóhd}r1(hf]hg]hh]hi]hl]uhnNhohhp]r1jö)r1}r1(hTUhd}r 1(hf]hg]hh]hi]hl]uhUj1hp]r!1(jü)r"1}r#1(hTX Default valuehUj1h`hahbjhd}r$1(hf]hg]hh]hi]hl]uhnKhp]r%1hyX Default valuer&1…r'1}r(1(hTUhUj"1ubaubj)r)1}r*1(hTUhd}r+1(hf]hg]hh]hi]hl]uhUj1hp]r,1h})r-1}r.1(hTXTruehd}r/1(hf]hg]hh]hi]hl]uhUj)1hp]r01hß)r11}r21(hTX``True``hUj-1h`Nhbhçhd}r31(hf]hg]hh]hi]hl]uhnNhohhp]r41hyXTruer51…r61}r71(hTUh`NhnNhohhUj11ubaubahbhubahbjubehbjùubaubh})r81}r91(hTXThe default value of this flag.r:1hUj1h`hahbhhd}r;1(hf]hg]hh]hi]hl]uhnMUhohhp]r<1hyXThe default value of this flag.r=1…r>1}r?1(hTj:1h`NhnNhohhUj81ubaubhë)r@1}rA1(hTX™This value may be `overridden in several ways `__. The rationale for having flags default to True is that users usually want new features as soon as they are available. Flags representing features that are not (yet) recommended for most users (such as experimental features or debugging support) should therefore explicitly override the default to False.hUj1h`hahbhîhd}rB1(hf]hg]hh]hi]hl]uhnNhohhp]rC1h})rD1}rE1(hTX™This value may be `overridden in several ways `__. The rationale for having flags default to True is that users usually want new features as soon as they are available. Flags representing features that are not (yet) recommended for most users (such as experimental features or debugging support) should therefore explicitly override the default to False.hUj@1h`hahbhhd}rF1(hf]hg]hh]hi]hl]uhnMYhp]rG1(hyXThis value may be rH1…rI1}rJ1(hTXThis value may be hUjD1ubj?)rK1}rL1(hTXV`overridden in several ways `__hd}rM1(UnameXoverridden in several waysj~X5installing-packages.html#controlling-flag-assignmentshi]hh]hf]hg]hl]uhUjD1hp]rN1hyXoverridden in several waysrO1…rP1}rQ1(hTUhUjK1ubahbjCubhyX1. The rationale for having flags default to True is that users usually want new features as soon as they are available. Flags representing features that are not (yet) recommended for most users (such as experimental features or debugging support) should therefore explicitly override the default to False.rR1…rS1}rT1(hTX1. The rationale for having flags default to True is that users usually want new features as soon as they are available. Flags representing features that are not (yet) recommended for most users (such as experimental features or debugging support) should therefore explicitly override the default to False.hUjD1ubeubaubeubeubj¹)rU1}rV1(hTUhUjE0h`hahbj¼hd}rW1(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rX1}rY1(hTUhUjE0h`hahbjÁhd}rZ1(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr[1jÇj[1uhnNhohhp]r\1(jÉ)r]1}r^1(hTXmanual: booleanhUjX1h`hahbjÍhd}r_1(hi]r`1Xpkg-field-flag-manualra1ahh]hf]hg]hl]jщuhnMihohhp]rb1(j¹)rc1}rd1(hTUhUj]1h`hahbj¼hd}re1(hi]hh]hf]hg]hl]Uentries]rf1(j×X flag:manual; package.cabal fieldja1UNtrg1auhnMihohhp]ubjÙ)rh1}ri1(hTXmanualrj1hUj]1h`hahbjÜhd}rk1(jÑjÒhi]hh]hf]hg]hl]uhnMihohhp]rl1hyXmanualrm1…rn1}ro1(hTUh`NhnNhohhUjh1ubaubjâ)rp1}rq1(hTj[hUj]1h`hahbjåhd}rr1(jÑjÒhi]hh]hf]hg]hl]uhnMihohhp]rs1hyX: rt1…ru1}rv1(hTUh`NhnNhohhUjp1ubaubja)rw1}rx1(hTXbooleanhUj]1h`hahbjdhd}ry1(jÑjÒhi]hh]hf]hg]hl]uhnMihohhp]rz1hyXbooleanr{1…r|1}r}1(hTUh`NhnNhohhUjw1ubaubeubjê)r~1}r1(hTUhUjX1h`hahbjíhd}r€1(hf]hg]hh]hi]hl]uhnMihohhp]r1(jð)r‚1}rƒ1(hTUhUj~1h`hahbjóhd}r„1(hf]hg]hh]hi]hl]uhnNhohhp]r…1jö)r†1}r‡1(hTUhd}rˆ1(hf]hg]hh]hi]hl]uhUj‚1hp]r‰1(jü)rŠ1}r‹1(hTX Default valuehUj†1h`hahbjhd}rŒ1(hf]hg]hh]hi]hl]uhnKhp]r1hyX Default valuerŽ1…r1}r1(hTUhUjŠ1ubaubj)r‘1}r’1(hTUhd}r“1(hf]hg]hh]hi]hl]uhUj†1hp]r”1h})r•1}r–1(hTXFalsehd}r—1(hf]hg]hh]hi]hl]uhUj‘1hp]r˜1hß)r™1}rš1(hTX ``False``hUj•1h`hahbhçhd}r›1(hf]hg]hh]hi]hl]uhnNhohhp]rœ1hyXFalser1…rž1}rŸ1(hTUh`NhnNhohhUj™1ubaubahbhubahbjubehbjùubaubh})r 1}r¡1(hTXBy default, Cabal will first try to satisfy dependencies with the default flag value and then, if that is not possible, with the negated value. However, if the flag is manual, then the default value (which can be overridden by commandline flags) will be used.r¢1hUj~1h`hahbhhd}r£1(hf]hg]hh]hi]hl]uhnMehohhp]r¤1hyXBy default, Cabal will first try to satisfy dependencies with the default flag value and then, if that is not possible, with the negated value. However, if the flag is manual, then the default value (which can be overridden by commandline flags) will be used.r¥1…r¦1}r§1(hTj¢1h`NhnNhohhUj 1ubaubeubeubeubeubhV)r¨1}r©1(hTUhYKhUh\h`hahbhchd}rª1(hf]hg]hh]hi]r«1jŠ0ahl]r¬1hCauhnMkhohhp]r­1(hr)r®1}r¯1(hTXConditional Blocksr°1hUj¨1h`hahbhvhd}r±1(hf]hg]hh]hi]hl]uhnMkhohhp]r²1hyXConditional Blocksr³1…r´1}rµ1(hTj°1h`NhnNhohhUj®1ubaubh})r¶1}r·1(hTX±Conditional blocks may appear anywhere inside a library or executable section. They have to follow rather strict formatting rules. Conditional blocks must always be of the shaper¸1hUj¨1h`hahbhhd}r¹1(hf]hg]hh]hi]hl]uhnMmhohhp]rº1hyX±Conditional blocks may appear anywhere inside a library or executable section. They have to follow rather strict formatting rules. Conditional blocks must always be of the shaper»1…r¼1}r½1(hTj¸1h`NhnNhohhUj¶1ubaubjÌ)r¾1}r¿1(hTX5if condition property-descriptions-or-conditionalshUj¨1h`hahbjÏhd}rÀ1(jÑjÒhi]hh]hf]hg]hl]uhnMshohhp]rÁ1hyX5if condition property-descriptions-or-conditionalsrÂ1…rÃ1}rÄ1(hTUhUj¾1ubaubh})rÅ1}rÆ1(hTXorrÇ1hUj¨1h`hahbhhd}rÈ1(hf]hg]hh]hi]hl]uhnMvhohhp]rÉ1hyXorrÊ1…rË1}rÌ1(hTjÇ1h`NhnNhohhUjÅ1ubaubjÌ)rÍ1}rÎ1(hTXgif condition property-descriptions-or-conditionals else property-descriptions-or-conditionalshUj¨1h`hahbjÏhd}rÏ1(jÑjÒhi]hh]hf]hg]hl]uhnMzhohhp]rÐ1hyXgif condition property-descriptions-or-conditionals else property-descriptions-or-conditionalsrÑ1…rÒ1}rÓ1(hTUhUjÍ1ubaubh})rÔ1}rÕ1(hTXGNote that the ``if`` and the condition have to be all on the same line.rÖ1hUj¨1h`hahbhhd}r×1(hf]hg]hh]hi]hl]uhnMhohhp]rØ1(hyXNote that the rÙ1…rÚ1}rÛ1(hTXNote that the h`NhnNhohhUjÔ1ubhß)rÜ1}rÝ1(hTX``if``hd}rÞ1(hf]hg]hh]hi]hl]uhUjÔ1hp]rß1hyXifrà1…rá1}râ1(hTUhUjÜ1ubahbhçubhyX3 and the condition have to be all on the same line.rã1…rä1}rå1(hTX3 and the condition have to be all on the same line.h`NhnNhohhUjÔ1ubeubhV)ræ1}rç1(hTUhUj¨1h`hahbhchd}rè1(hf]hg]hh]hi]ré1U conditionsrê1ahl]rë1h(auhnM‚hohhp]rì1(hr)rí1}rî1(hTX Conditionsrï1hUjæ1h`hahbhvhd}rð1(hf]hg]hh]hi]hl]uhnM‚hohhp]rñ1hyX Conditionsrò1…ró1}rô1(hTjï1h`NhnNhohhUjí1ubaubh})rõ1}rö1(hTX¶Conditions can be formed using boolean tests and the boolean operators ``||`` (disjunction / logical "or"), ``&&`` (conjunction / logical "and"), or ``!`` (negation / logical "not"). The unary ``!`` takes highest precedence, ``||`` takes lowest. Precedence levels may be overridden through the use of parentheses. For example, ``os(darwin) && !arch(i386) || os(freebsd)`` is equivalent to ``(os(darwin) && !(arch(i386))) || os(freebsd)``.hUjæ1h`hahbhhd}r÷1(hf]hg]hh]hi]hl]uhnM„hohhp]rø1(hyXGConditions can be formed using boolean tests and the boolean operators rù1…rú1}rû1(hTXGConditions can be formed using boolean tests and the boolean operators h`NhnNhohhUjõ1ubhß)rü1}rý1(hTX``||``hd}rþ1(hf]hg]hh]hi]hl]uhUjõ1hp]rÿ1hyX||r2…r2}r2(hTUhUjü1ubahbhçubhyX# (disjunction / logical “orâ€), r2…r2}r2(hTX (disjunction / logical "or"), h`NhnNhohhUjõ1ubhß)r2}r2(hTX``&&``hd}r2(hf]hg]hh]hi]hl]uhUjõ1hp]r 2hyX&&r 2…r 2}r 2(hTUhUj2ubahbhçubhyX' (conjunction / logical “andâ€), or r 2…r2}r2(hTX# (conjunction / logical "and"), or h`NhnNhohhUjõ1ubhß)r2}r2(hTX``!``hd}r2(hf]hg]hh]hi]hl]uhUjõ1hp]r2hyX!…r2}r2(hTUhUj2ubahbhçubhyX+ (negation / logical “notâ€). The unary r2…r2}r2(hTX' (negation / logical "not"). The unary h`NhnNhohhUjõ1ubhß)r2}r2(hTX``!``hd}r2(hf]hg]hh]hi]hl]uhUjõ1hp]r2hyX!…r2}r2(hTUhUj2ubahbhçubhyX takes highest precedence, r2…r 2}r!2(hTX takes highest precedence, h`NhnNhohhUjõ1ubhß)r"2}r#2(hTX``||``hd}r$2(hf]hg]hh]hi]hl]uhUjõ1hp]r%2hyX||r&2…r'2}r(2(hTUhUj"2ubahbhçubhyX` takes lowest. Precedence levels may be overridden through the use of parentheses. For example, r)2…r*2}r+2(hTX` takes lowest. Precedence levels may be overridden through the use of parentheses. For example, h`NhnNhohhUjõ1ubhß)r,2}r-2(hTX,``os(darwin) && !arch(i386) || os(freebsd)``hd}r.2(hf]hg]hh]hi]hl]uhUjõ1hp]r/2hyX(os(darwin) && !arch(i386) || os(freebsd)r02…r12}r22(hTUhUj,2ubahbhçubhyX is equivalent to r32…r42}r52(hTX is equivalent to h`NhnNhohhUjõ1ubhß)r62}r72(hTX0``(os(darwin) && !(arch(i386))) || os(freebsd)``hd}r82(hf]hg]hh]hi]hl]uhUjõ1hp]r92hyX,(os(darwin) && !(arch(i386))) || os(freebsd)r:2…r;2}r<2(hTUhUj62ubahbhçubhyX.…r=2}r>2(hTX.h`NhnNhohhUjõ1ubeubh})r?2}r@2(hTX,The following tests are currently supported.rA2hUjæ1h`hahbhhd}rB2(hf]hg]hh]hi]hl]uhnMŒhohhp]rC2hyX,The following tests are currently supported.rD2…rE2}rF2(hTjA2h`NhnNhohhUj?2ubaubj)rG2}rH2(hTUhUjæ1h`hahbjhd}rI2(hf]hg]hh]hi]hl]uhnNhohhp]rJ2(j)rK2}rL2(hTXÒ:samp:`os({name})` Tests if the current operating system is *name*. The argument is tested against ``System.Info.os`` on the target system. There is unfortunately some disagreement between Haskell implementations about the standard values of ``System.Info.os``. Cabal canonicalises it so that in particular ``os(windows)`` works on all implementations. If the canonicalised os names match, this test evaluates to true, otherwise false. The match is case-insensitive.hUjG2h`hahbjhd}rM2(hf]hg]hh]hi]hl]uhnM”hp]rN2(j)rO2}rP2(hTX:samp:`os({name})`rQ2hUjK2h`hahbj hd}rR2(hf]hg]hh]hi]hl]uhnM”hp]rS2hß)rT2}rU2(hTXos(name)hd}rV2(hi]hh]hf]hg]rW2XsamprX2aUrolejX2hl]uhUjO2hp]rY2(hyXos(rZ2…r[2}r\2(hTXos(hUjT2ubh¿)r]2}r^2(hTXnamehd}r_2(hf]hg]hh]hi]hl]uhUjT2hp]r`2hyXnamera2…rb2}rc2(hTUhUj]2ubahbhÇubhyX)…rd2}re2(hTX)hUjT2ubehbhçubaubj3)rf2}rg2(hTUhd}rh2(hf]hg]hh]hi]hl]uhUjK2hp]ri2h})rj2}rk2(hTX¿Tests if the current operating system is *name*. The argument is tested against ``System.Info.os`` on the target system. There is unfortunately some disagreement between Haskell implementations about the standard values of ``System.Info.os``. Cabal canonicalises it so that in particular ``os(windows)`` works on all implementations. If the canonicalised os names match, this test evaluates to true, otherwise false. The match is case-insensitive.hUjf2h`hahbhhd}rl2(hf]hg]hh]hi]hl]uhnMhp]rm2(hyX)Tests if the current operating system is rn2…ro2}rp2(hTX)Tests if the current operating system is hUjj2ubh¿)rq2}rr2(hTX*name*hd}rs2(hf]hg]hh]hi]hl]uhUjj2hp]rt2hyXnameru2…rv2}rw2(hTUhUjq2ubahbhÇubhyX!. The argument is tested against rx2…ry2}rz2(hTX!. The argument is tested against hUjj2ubhß)r{2}r|2(hTX``System.Info.os``hd}r}2(hf]hg]hh]hi]hl]uhUjj2hp]r~2hyXSystem.Info.osr2…r€2}r2(hTUhUj{2ubahbhçubhyX} on the target system. There is unfortunately some disagreement between Haskell implementations about the standard values of r‚2…rƒ2}r„2(hTX} on the target system. There is unfortunately some disagreement between Haskell implementations about the standard values of hUjj2ubhß)r…2}r†2(hTX``System.Info.os``hd}r‡2(hf]hg]hh]hi]hl]uhUjj2hp]rˆ2hyXSystem.Info.osr‰2…rŠ2}r‹2(hTUhUj…2ubahbhçubhyX/. Cabal canonicalises it so that in particular rŒ2…r2}rŽ2(hTX/. Cabal canonicalises it so that in particular hUjj2ubhß)r2}r2(hTX``os(windows)``hd}r‘2(hf]hg]hh]hi]hl]uhUjj2hp]r’2hyX os(windows)r“2…r”2}r•2(hTUhUj2ubahbhçubhyX works on all implementations. If the canonicalised os names match, this test evaluates to true, otherwise false. The match is case-insensitive.r–2…r—2}r˜2(hTX works on all implementations. If the canonicalised os names match, this test evaluates to true, otherwise false. The match is case-insensitive.hUjj2ubeubahbjMubeubj)r™2}rš2(hTXò:samp:`arch({name})` Tests if the current architecture is *name*. The argument is matched against ``System.Info.arch`` on the target system. If the arch names match, this test evaluates to true, otherwise false. The match is case-insensitive.hUjG2h`hahbjhd}r›2(hf]hg]hh]hi]hl]uhnM™hohhp]rœ2(j)r2}rž2(hTX:samp:`arch({name})`rŸ2hUj™2h`hahbj hd}r 2(hf]hg]hh]hi]hl]uhnM™hp]r¡2hß)r¢2}r£2(hTX arch(name)hd}r¤2(hi]hh]hf]hg]r¥2Xsampr¦2aUrolej¦2hl]uhUj2hp]r§2(hyXarch(r¨2…r©2}rª2(hTXarch(hUj¢2ubh¿)r«2}r¬2(hTXnamehd}r­2(hf]hg]hh]hi]hl]uhUj¢2hp]r®2hyXnamer¯2…r°2}r±2(hTUhUj«2ubahbhÇubhyX)…r²2}r³2(hTX)hUj¢2ubehbhçubaubj3)r´2}rµ2(hTUhd}r¶2(hf]hg]hh]hi]hl]uhUj™2hp]r·2h})r¸2}r¹2(hTXÝTests if the current architecture is *name*. The argument is matched against ``System.Info.arch`` on the target system. If the arch names match, this test evaluates to true, otherwise false. The match is case-insensitive.hUj´2h`hahbhhd}rº2(hf]hg]hh]hi]hl]uhnM—hp]r»2(hyX%Tests if the current architecture is r¼2…r½2}r¾2(hTX%Tests if the current architecture is hUj¸2ubh¿)r¿2}rÀ2(hTX*name*hd}rÁ2(hf]hg]hh]hi]hl]uhUj¸2hp]rÂ2hyXnamerÃ2…rÄ2}rÅ2(hTUhUj¿2ubahbhÇubhyX". The argument is matched against rÆ2…rÇ2}rÈ2(hTX". The argument is matched against hUj¸2ubhß)rÉ2}rÊ2(hTX``System.Info.arch``hd}rË2(hf]hg]hh]hi]hl]uhUj¸2hp]rÌ2hyXSystem.Info.archrÍ2…rÎ2}rÏ2(hTUhUjÉ2ubahbhçubhyX| on the target system. If the arch names match, this test evaluates to true, otherwise false. The match is case-insensitive.rÐ2…rÑ2}rÒ2(hTX| on the target system. If the arch names match, this test evaluates to true, otherwise false. The match is case-insensitive.hUj¸2ubeubahbjMubeubj)rÓ2}rÔ2(hTX:samp:`impl({compiler})` Tests for the configured Haskell implementation. An optional version constraint may be specified (for example ``impl(ghc >= 6.6.1)``). If the configured implementation is of the right type and matches the version constraint, then this evaluates to true, otherwise false. The match is case-insensitive. Note that including a version constraint in an ``impl`` test causes it to check for two properties: - The current compiler has the specified name, and - The compiler's version satisfied the specified version constraint As a result, ``!impl(ghc >= x.y.z)`` is not entirely equivalent to ``impl(ghc < x.y.z)``. The test ``!impl(ghc >= x.y.z)`` checks that: - The current compiler is not GHC, or - The version of GHC is earlier than version x.y.z. hUjG2h`hahbjhd}rÕ2(hf]hg]hh]hi]hl]uhnM®hohhp]rÖ2(j)r×2}rØ2(hTX:samp:`impl({compiler})`rÙ2hUjÓ2h`hahbj hd}rÚ2(hf]hg]hh]hi]hl]uhnM®hp]rÛ2hß)rÜ2}rÝ2(hTXimpl(compiler)hd}rÞ2(hi]hh]hf]hg]rß2Xsamprà2aUrolejà2hl]uhUj×2hp]rá2(hyXimpl(râ2…rã2}rä2(hTXimpl(hUjÜ2ubh¿)rå2}ræ2(hTXcompilerhd}rç2(hf]hg]hh]hi]hl]uhUjÜ2hp]rè2hyXcompilerré2…rê2}rë2(hTUhUjå2ubahbhÇubhyX)…rì2}rí2(hTX)hUjÜ2ubehbhçubaubj3)rî2}rï2(hTUhd}rð2(hf]hg]hh]hi]hl]uhUjÓ2hp]rñ2(h})rò2}ró2(hTX-Tests for the configured Haskell implementation. An optional version constraint may be specified (for example ``impl(ghc >= 6.6.1)``). If the configured implementation is of the right type and matches the version constraint, then this evaluates to true, otherwise false. The match is case-insensitive.hUjî2h`hahbhhd}rô2(hf]hg]hh]hi]hl]uhnMœhp]rõ2(hyXnTests for the configured Haskell implementation. An optional version constraint may be specified (for example rö2…r÷2}rø2(hTXnTests for the configured Haskell implementation. An optional version constraint may be specified (for example hUjò2ubhß)rù2}rú2(hTX``impl(ghc >= 6.6.1)``hd}rû2(hf]hg]hh]hi]hl]uhUjò2hp]rü2hyXimpl(ghc >= 6.6.1)rý2…rþ2}rÿ2(hTUhUjù2ubahbhçubhyX©). If the configured implementation is of the right type and matches the version constraint, then this evaluates to true, otherwise false. The match is case-insensitive.r3…r3}r3(hTX©). If the configured implementation is of the right type and matches the version constraint, then this evaluates to true, otherwise false. The match is case-insensitive.hUjò2ubeubh})r3}r3(hTXcNote that including a version constraint in an ``impl`` test causes it to check for two properties:hUjî2h`hahbhhd}r3(hf]hg]hh]hi]hl]uhnM¢hp]r3(hyX/Note that including a version constraint in an r3…r3}r 3(hTX/Note that including a version constraint in an hUj3ubhß)r 3}r 3(hTX``impl``hd}r 3(hf]hg]hh]hi]hl]uhUj3hp]r 3hyXimplr3…r3}r3(hTUhUj 3ubahbhçubhyX, test causes it to check for two properties:r3…r3}r3(hTX, test causes it to check for two properties:hUj3ubeubh‡)r3}r3(hTUhUjî2h`hahbhŠhd}r3(hŒX-hi]hh]hf]hg]hl]uhnM¥hp]r3(hŽ)r3}r3(hTX1The current compiler has the specified name, and hd}r3(hf]hg]hh]hi]hl]uhUj3hp]r3h})r3}r3(hTX0The current compiler has the specified name, andr3hUj3h`hahbhhd}r3(hf]hg]hh]hi]hl]uhnM¥hp]r 3hyX0The current compiler has the specified name, andr!3…r"3}r#3(hTj3hUj3ubaubahbh‘ubhŽ)r$3}r%3(hTXBThe compiler's version satisfied the specified version constraint hd}r&3(hf]hg]hh]hi]hl]uhUj3hp]r'3h})r(3}r)3(hTXAThe compiler's version satisfied the specified version constraintr*3hUj$3h`hahbhhd}r+3(hf]hg]hh]hi]hl]uhnM§hp]r,3hyXCThe compiler’s version satisfied the specified version constraintr-3…r.3}r/3(hTj*3hUj(3ubaubahbh‘ubeubh})r03}r13(hTX‡As a result, ``!impl(ghc >= x.y.z)`` is not entirely equivalent to ``impl(ghc < x.y.z)``. The test ``!impl(ghc >= x.y.z)`` checks that:hUjî2h`hahbhhd}r23(hf]hg]hh]hi]hl]uhnM©hp]r33(hyX As a result, r43…r53}r63(hTX As a result, hUj03ubhß)r73}r83(hTX``!impl(ghc >= x.y.z)``hd}r93(hf]hg]hh]hi]hl]uhUj03hp]r:3hyX!impl(ghc >= x.y.z)r;3…r<3}r=3(hTUhUj73ubahbhçubhyX is not entirely equivalent to r>3…r?3}r@3(hTX is not entirely equivalent to hUj03ubhß)rA3}rB3(hTX``impl(ghc < x.y.z)``hd}rC3(hf]hg]hh]hi]hl]uhUj03hp]rD3hyXimpl(ghc < x.y.z)rE3…rF3}rG3(hTUhUjA3ubahbhçubhyX . The test rH3…rI3}rJ3(hTX . The test hUj03ubhß)rK3}rL3(hTX``!impl(ghc >= x.y.z)``hd}rM3(hf]hg]hh]hi]hl]uhUj03hp]rN3hyX!impl(ghc >= x.y.z)rO3…rP3}rQ3(hTUhUjK3ubahbhçubhyX checks that:rR3…rS3}rT3(hTX checks that:hUj03ubeubh‡)rU3}rV3(hTUhUjî2h`hahbhŠhd}rW3(hŒX-hi]hh]hf]hg]hl]uhnM¬hp]rX3(hŽ)rY3}rZ3(hTX$The current compiler is not GHC, or hd}r[3(hf]hg]hh]hi]hl]uhUjU3hp]r\3h})r]3}r^3(hTX#The current compiler is not GHC, orr_3hUjY3h`hahbhhd}r`3(hf]hg]hh]hi]hl]uhnM¬hp]ra3hyX#The current compiler is not GHC, orrb3…rc3}rd3(hTj_3hUj]3ubaubahbh‘ubhŽ)re3}rf3(hTX2The version of GHC is earlier than version x.y.z. hd}rg3(hf]hg]hh]hi]hl]uhUjU3hp]rh3h})ri3}rj3(hTX1The version of GHC is earlier than version x.y.z.rk3hUje3h`hahbhhd}rl3(hf]hg]hh]hi]hl]uhnM®hp]rm3hyX1The version of GHC is earlier than version x.y.z.rn3…ro3}rp3(hTjk3hUji3ubaubahbh‘ubeubehbjMubeubj)rq3}rr3(hTXÉ:samp:`flag({name})` Evaluates to the current assignment of the flag of the given name. Flag names are case insensitive. Testing for flags that have not been introduced with a flag section is an error.hUjG2h`hahbjhd}rs3(hf]hg]hh]hi]hl]uhnM²hohhp]rt3(j)ru3}rv3(hTX:samp:`flag({name})`rw3hUjq3h`hahbj hd}rx3(hf]hg]hh]hi]hl]uhnM²hp]ry3hß)rz3}r{3(hTX flag(name)hd}r|3(hi]hh]hf]hg]r}3Xsampr~3aUrolej~3hl]uhUju3hp]r3(hyXflag(r€3…r3}r‚3(hTXflag(hUjz3ubh¿)rƒ3}r„3(hTXnamehd}r…3(hf]hg]hh]hi]hl]uhUjz3hp]r†3hyXnamer‡3…rˆ3}r‰3(hTUhUjƒ3ubahbhÇubhyX)…rŠ3}r‹3(hTX)hUjz3ubehbhçubaubj3)rŒ3}r3(hTUhd}rŽ3(hf]hg]hh]hi]hl]uhUjq3hp]r3h})r3}r‘3(hTX´Evaluates to the current assignment of the flag of the given name. Flag names are case insensitive. Testing for flags that have not been introduced with a flag section is an error.r’3hUjŒ3h`hahbhhd}r“3(hf]hg]hh]hi]hl]uhnM±hp]r”3hyX´Evaluates to the current assignment of the flag of the given name. Flag names are case insensitive. Testing for flags that have not been introduced with a flag section is an error.r•3…r–3}r—3(hTj’3hUj3ubaubahbjMubeubj)r˜3}r™3(hTX``true`` Constant value true.hUjG2h`hahbjhd}rš3(hf]hg]hh]hi]hl]uhnM´hohhp]r›3(j)rœ3}r3(hTX``true``rž3hUj˜3h`hahbj hd}rŸ3(hf]hg]hh]hi]hl]uhnM´hp]r 3hß)r¡3}r¢3(hTjž3hd}r£3(hf]hg]hh]hi]hl]uhUjœ3hp]r¤3hyXtruer¥3…r¦3}r§3(hTUhUj¡3ubahbhçubaubj3)r¨3}r©3(hTUhd}rª3(hf]hg]hh]hi]hl]uhUj˜3hp]r«3h})r¬3}r­3(hTXConstant value true.r®3hUj¨3h`hahbhhd}r¯3(hf]hg]hh]hi]hl]uhnMµhp]r°3hyXConstant value true.r±3…r²3}r³3(hTj®3hUj¬3ubaubahbjMubeubj)r´3}rµ3(hTX ``false`` Constant value false. hUjG2h`hahbjhd}r¶3(hf]hg]hh]hi]hl]uhnM·hohhp]r·3(j)r¸3}r¹3(hTX ``false``rº3hUj´3h`hahbj hd}r»3(hf]hg]hh]hi]hl]uhnM·hp]r¼3hß)r½3}r¾3(hTjº3hd}r¿3(hf]hg]hh]hi]hl]uhUj¸3hp]rÀ3hyXfalserÁ3…rÂ3}rÃ3(hTUhUj½3ubahbhçubaubj3)rÄ3}rÅ3(hTUhd}rÆ3(hf]hg]hh]hi]hl]uhUj´3hp]rÇ3h})rÈ3}rÉ3(hTXConstant value false.rÊ3hUjÄ3h`hahbhhd}rË3(hf]hg]hh]hi]hl]uhnM·hp]rÌ3hyXConstant value false.rÍ3…rÎ3}rÏ3(hTjÊ3hUjÈ3ubaubahbjMubeubeubeubhV)rÐ3}rÑ3(hTUhUj¨1h`hahbhchd}rÒ3(hf]hg]hh]hi]rÓ3U"resolution-of-conditions-and-flagsrÔ3ahl]rÕ3h%auhnMºhohhp]rÖ3(hr)r×3}rØ3(hTX"Resolution of Conditions and FlagsrÙ3hUjÐ3h`hahbhvhd}rÚ3(hf]hg]hh]hi]hl]uhnMºhohhp]rÛ3hyX"Resolution of Conditions and FlagsrÜ3…rÝ3}rÞ3(hTjÙ3h`NhnNhohhUj×3ubaubh})rß3}rà3(hTXIf a package descriptions specifies configuration flags the package user can `control these in several ways `__. If the user does not fix the value of a flag, Cabal will try to find a flag assignment in the following way.hUjÐ3h`hahbhhd}rá3(hf]hg]hh]hi]hl]uhnM¼hohhp]râ3(hyXMIf a package descriptions specifies configuration flags the package user can rã3…rä3}rå3(hTXMIf a package descriptions specifies configuration flags the package user can h`NhnNhohhUjß3ubj?)ræ3}rç3(hTXY`control these in several ways `__hd}rè3(UnameXcontrol these in several waysj~X5installing-packages.html#controlling-flag-assignmentshi]hh]hf]hg]hl]uhUjß3hp]ré3hyXcontrol these in several waysrê3…rë3}rì3(hTUhUjæ3ubahbjCubhyXn. If the user does not fix the value of a flag, Cabal will try to find a flag assignment in the following way.rí3…rî3}rï3(hTXn. If the user does not fix the value of a flag, Cabal will try to find a flag assignment in the following way.h`NhnNhohhUjß3ubeubh‡)rð3}rñ3(hTUhUjÐ3h`hahbhŠhd}rò3(hŒX-hi]hh]hf]hg]hl]uhnMÂhohhp]ró3(hŽ)rô3}rõ3(hTXóFor each flag specified, it will assign its default value, evaluate all conditions with this flag assignment, and check if all dependencies can be satisfied. If this check succeeded, the package will be configured with those flag assignments. hUjð3h`hahbh‘hd}rö3(hf]hg]hh]hi]hl]uhnNhohhp]r÷3h})rø3}rù3(hTXòFor each flag specified, it will assign its default value, evaluate all conditions with this flag assignment, and check if all dependencies can be satisfied. If this check succeeded, the package will be configured with those flag assignments.rú3hUjô3h`hahbhhd}rû3(hf]hg]hh]hi]hl]uhnMÂhp]rü3hyXòFor each flag specified, it will assign its default value, evaluate all conditions with this flag assignment, and check if all dependencies can be satisfied. If this check succeeded, the package will be configured with those flag assignments.rý3…rþ3}rÿ3(hTjú3hUjø3ubaubaubhŽ)r4}r4(hTX9If dependencies were missing, the last flag (as by the order in which the flags were introduced in the package description) is tried with its alternative value and so on. This continues until either an assignment is found where all dependencies can be satisfied, or all possible flag assignments have been tried. hUjð3h`hahbh‘hd}r4(hf]hg]hh]hi]hl]uhnNhohhp]r4h})r4}r4(hTX8If dependencies were missing, the last flag (as by the order in which the flags were introduced in the package description) is tried with its alternative value and so on. This continues until either an assignment is found where all dependencies can be satisfied, or all possible flag assignments have been tried.r4hUj4h`hahbhhd}r4(hf]hg]hh]hi]hl]uhnMÇhp]r4hyX8If dependencies were missing, the last flag (as by the order in which the flags were introduced in the package description) is tried with its alternative value and so on. This continues until either an assignment is found where all dependencies can be satisfied, or all possible flag assignments have been tried.r 4…r 4}r 4(hTj4hUj4ubaubaubeubh})r 4}r 4(hTXTo put it another way, Cabal does a complete backtracking search to find a satisfiable package configuration. It is only the dependencies specified in the :pkg-field:`build-depends` field in conditional blocks that determine if a particular flag assignment is satisfiable (:pkg-field:`build-tools` are not considered). The order of the declaration and the default value of the flags determines the search order. Flags overridden on the command line fix the assignment of that flag, so no backtracking will be tried for that flag.hUjÐ3h`hahbhhd}r4(hf]hg]hh]hi]hl]uhnMÍhohhp]r4(hyX›To put it another way, Cabal does a complete backtracking search to find a satisfiable package configuration. It is only the dependencies specified in the r4…r4}r4(hTX›To put it another way, Cabal does a complete backtracking search to find a satisfiable package configuration. It is only the dependencies specified in the h`NhnNhohhUj 4ubjk)r4}r4(hTX:pkg-field:`build-depends`r4hUj 4h`hahbjohd}r4(UreftypeX pkg-fieldjqˆjrX build-dependsU refdomainXcabalr4hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹Xflagr4uhnMÍhp]r4hß)r4}r4(hTj4hd}r4(hf]hg]r4(j|j4Xcabal-pkg-fieldr4ehh]hi]hl]uhUj4hp]r4hyX build-dependsr 4…r!4}r"4(hTUhUj4ubahbhçubaubhyX\ field in conditional blocks that determine if a particular flag assignment is satisfiable (r#4…r$4}r%4(hTX\ field in conditional blocks that determine if a particular flag assignment is satisfiable (h`NhnNhohhUj 4ubjk)r&4}r'4(hTX:pkg-field:`build-tools`r(4hUj 4h`hahbjohd}r)4(UreftypeX pkg-fieldjqˆjrX build-toolsU refdomainXcabalr*4hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹j4uhnMÍhp]r+4hß)r,4}r-4(hTj(4hd}r.4(hf]hg]r/4(j|j*4Xcabal-pkg-fieldr04ehh]hi]hl]uhUj&4hp]r14hyX build-toolsr24…r34}r44(hTUhUj,4ubahbhçubaubhyXè are not considered). The order of the declaration and the default value of the flags determines the search order. Flags overridden on the command line fix the assignment of that flag, so no backtracking will be tried for that flag.r54…r64}r74(hTXè are not considered). The order of the declaration and the default value of the flags determines the search order. Flags overridden on the command line fix the assignment of that flag, so no backtracking will be tried for that flag.h`NhnNhohhUj 4ubeubh})r84}r94(hTXbIf no suitable flag assignment could be found, the configuration phase will fail and a list of missing dependencies will be printed. Note that this resolution process is exponential in the worst case (i.e., in the case where dependencies cannot be satisfied). There are some optimizations applied internally, but the overall complexity remains unchanged.r:4hUjÐ3h`hahbhhd}r;4(hf]hg]hh]hi]hl]uhnMÖhohhp]r<4hyXbIf no suitable flag assignment could be found, the configuration phase will fail and a list of missing dependencies will be printed. Note that this resolution process is exponential in the worst case (i.e., in the case where dependencies cannot be satisfied). There are some optimizations applied internally, but the overall complexity remains unchanged.r=4…r>4}r?4(hTj:4h`NhnNhohhUj84ubaubeubeubhV)r@4}rA4(hTUhUh\h`hahbhchd}rB4(hf]hg]hh]hi]rC4U/meaning-of-field-values-when-using-conditionalsrD4ahl]rE4hauhnMÞhohhp]rF4(hr)rG4}rH4(hTX/Meaning of field values when using conditionalsrI4hUj@4h`hahbhvhd}rJ4(hf]hg]hh]hi]hl]uhnMÞhohhp]rK4hyX/Meaning of field values when using conditionalsrL4…rM4}rN4(hTjI4h`NhnNhohhUjG4ubaubh})rO4}rP4(hTXDuring the configuration phase, a flag assignment is chosen, all conditionals are evaluated, and the package description is combined into a flat package descriptions. If the same field both inside a conditional and outside then they are combined using the following rules.rQ4hUj@4h`hahbhhd}rR4(hf]hg]hh]hi]hl]uhnMàhohhp]rS4hyXDuring the configuration phase, a flag assignment is chosen, all conditionals are evaluated, and the package description is combined into a flat package descriptions. If the same field both inside a conditional and outside then they are combined using the following rules.rT4…rU4}rV4(hTjQ4h`NhnNhohhUjO4ubaubh‡)rW4}rX4(hTUhUj@4h`hahbhŠhd}rY4(hŒX-hi]hh]hf]hg]hl]uhnMåhohhp]rZ4(hŽ)r[4}r\4(hTX?Boolean fields are combined using conjunction (logical "and"). hUjW4h`hahbh‘hd}r]4(hf]hg]hh]hi]hl]uhnNhohhp]r^4h})r_4}r`4(hTX>Boolean fields are combined using conjunction (logical "and").ra4hUj[4h`hahbhhd}rb4(hf]hg]hh]hi]hl]uhnMåhp]rc4hyXBBoolean fields are combined using conjunction (logical “andâ€).rd4…re4}rf4(hTja4hUj_4ubaubaubhŽ)rg4}rh4(hTX¸List fields are combined by appending the inner items to the outer items, for example :: other-extensions: CPP if impl(ghc) other-extensions: MultiParamTypeClasses when compiled using GHC will be combined to :: other-extensions: CPP, MultiParamTypeClasses Similarly, if two conditional sections appear at the same nesting level, properties specified in the latter will come after properties specified in the former. hUjW4h`hahbh‘hd}ri4(hf]hg]hh]hi]hl]uhnNhohhp]rj4(h})rk4}rl4(hTXUList fields are combined by appending the inner items to the outer items, for examplerm4hUjg4h`hahbhhd}rn4(hf]hg]hh]hi]hl]uhnMçhp]ro4hyXUList fields are combined by appending the inner items to the outer items, for examplerp4…rq4}rr4(hTjm4hUjk4ubaubjÌ)rs4}rt4(hTXLother-extensions: CPP if impl(ghc) other-extensions: MultiParamTypeClasseshUjg4hbjÏhd}ru4(jÑjÒhi]hh]hf]hg]hl]uhnMìhp]rv4hyXLother-extensions: CPP if impl(ghc) other-extensions: MultiParamTypeClassesrw4…rx4}ry4(hTUhUjs4ubaubh})rz4}r{4(hTX+when compiled using GHC will be combined tor|4hUjg4h`hahbhhd}r}4(hf]hg]hh]hi]hl]uhnMðhp]r~4hyX+when compiled using GHC will be combined tor4…r€4}r4(hTj|4hUjz4ubaubjÌ)r‚4}rƒ4(hTX,other-extensions: CPP, MultiParamTypeClasseshUjg4hbjÏhd}r„4(jÑjÒhi]hh]hf]hg]hl]uhnMôhp]r…4hyX,other-extensions: CPP, MultiParamTypeClassesr†4…r‡4}rˆ4(hTUhUj‚4ubaubh})r‰4}rŠ4(hTXŸSimilarly, if two conditional sections appear at the same nesting level, properties specified in the latter will come after properties specified in the former.r‹4hUjg4h`hahbhhd}rŒ4(hf]hg]hh]hi]hl]uhnMöhp]r4hyXŸSimilarly, if two conditional sections appear at the same nesting level, properties specified in the latter will come after properties specified in the former.rŽ4…r4}r4(hTj‹4hUj‰4ubaubeubhŽ)r‘4}r’4(hTXAll other fields must not be specified in ambiguous ways. For example :: Main-is: Main.hs if flag(useothermain) Main-is: OtherMain.hs will lead to an error. Instead use :: if flag(useothermain) Main-is: OtherMain.hs else Main-is: Main.hs hUjW4h`hahbh‘hd}r“4(hf]hg]hh]hi]hl]uhnNhohhp]r”4(h})r•4}r–4(hTXEAll other fields must not be specified in ambiguous ways. For exampler—4hUj‘4h`hahbhhd}r˜4(hf]hg]hh]hi]hl]uhnMúhp]r™4hyXEAll other fields must not be specified in ambiguous ways. For examplerš4…r›4}rœ4(hTj—4hUj•4ubaubjÌ)r4}rž4(hTX>Main-is: Main.hs if flag(useothermain) Main-is: OtherMain.hshUj‘4hbjÏhd}rŸ4(jÑjÒhi]hh]hf]hg]hl]uhnMþhp]r 4hyX>Main-is: Main.hs if flag(useothermain) Main-is: OtherMain.hsr¡4…r¢4}r£4(hTUhUj4ubaubh})r¤4}r¥4(hTX"will lead to an error. Instead user¦4hUj‘4h`hahbhhd}r§4(hf]hg]hh]hi]hl]uhnM hp]r¨4hyX"will lead to an error. Instead user©4…rª4}r«4(hTj¦4hUj¤4ubaubjÌ)r¬4}r­4(hTXEif flag(useothermain) Main-is: OtherMain.hs else Main-is: Main.hshUj‘4hbjÏhd}r®4(jÑjÒhi]hh]hf]hg]hl]uhnM hp]r¯4hyXEif flag(useothermain) Main-is: OtherMain.hs else Main-is: Main.hsr°4…r±4}r²4(hTUhUj¬4ubaubeubeubeubhV)r³4}r´4(hTUhUh\h`hahbhchd}rµ4(hf]hg]hh]hi]r¶4Usource-repositoriesr·4ahl]r¸4h,auhnM hohhp]r¹4(hr)rº4}r»4(hTXSource Repositoriesr¼4hUj³4h`hahbhvhd}r½4(hf]hg]hh]hi]hl]uhnM hohhp]r¾4hyXSource Repositoriesr¿4…rÀ4}rÁ4(hTj¼4h`NhnNhohhUjº4ubaubj¹)rÂ4}rÃ4(hTUhUj³4h`Nhbj¼hd}rÄ4(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÅ4}rÆ4(hTUhUj³4h`NhbjÁhd}rÇ4(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-sectionrÈ4jÇjÈ4uhnNhohhp]rÉ4(jÉ)rÊ4}rË4(hTXsource-repositoryrÌ4hUjÅ4h`hahbjÍhd}rÍ4(hi]rÎ4X/pkg-section-source-repository-source-repositoryrÏ4ahh]hf]hg]hl]jщuhnM hohhp]rÐ4(j¹)rÑ4}rÒ4(hTUhUjÊ4h`hahbj¼hd}rÓ4(hi]hh]hf]hg]hl]Uentries]rÔ4(j×X:source-repository:source-repository; package.cabal sectionjÏ4UNtrÕ4auhnM hohhp]ubjÙ)rÖ4}r×4(hTjÌ4hUjÊ4h`hahbjÜhd}rØ4(jÑjÒhi]hh]hf]hg]hl]uhnM hohhp]rÙ4hyXsource-repositoryrÚ4…rÛ4}rÜ4(hTUh`NhnNhohhUjÖ4ubaubjâ)rÝ4}rÞ4(hTU hUjÊ4h`hahbjåhd}rß4(jÑjÒhi]hh]hf]hg]hl]uhnM hohhp]rà4hyX …rá4}râ4(hTUh`NhnNhohhUjÝ4ubaubeubjê)rã4}rä4(hTUhUjÅ4h`hahbjíhd}rå4(hf]hg]hh]hi]hl]uhnM hohhp]ubeubh})ræ4}rç4(hTXYIt is often useful to be able to specify a source revision control repository for a package. Cabal lets you specifying this information in a relatively structured form which enables other tools to interpret and make effective use of the information. For example the information should be sufficient for an automatic tool to checkout the sources.rè4hUj³4h`hahbhhd}ré4(hf]hg]hh]hi]hl]uhnM hohhp]rê4hyXYIt is often useful to be able to specify a source revision control repository for a package. Cabal lets you specifying this information in a relatively structured form which enables other tools to interpret and make effective use of the information. For example the information should be sufficient for an automatic tool to checkout the sources.rë4…rì4}rí4(hTjè4h`NhnNhohhUjæ4ubaubh})rî4}rï4(hTX¥Cabal supports specifying different information for various common source control systems. Obviously not all automated tools will support all source control systems.rð4hUj³4h`hahbhhd}rñ4(hf]hg]hh]hi]hl]uhnM hohhp]rò4hyX¥Cabal supports specifying different information for various common source control systems. Obviously not all automated tools will support all source control systems.ró4…rô4}rõ4(hTjð4h`NhnNhohhUjî4ubaubh})rö4}r÷4(hTXªCabal supports specifying repositories for different use cases. By declaring which case we mean automated tools can be more useful. There are currently two kinds defined:rø4hUj³4h`hahbhhd}rù4(hf]hg]hh]hi]hl]uhnM hohhp]rú4hyXªCabal supports specifying repositories for different use cases. By declaring which case we mean automated tools can be more useful. There are currently two kinds defined:rû4…rü4}rý4(hTjø4h`NhnNhohhUjö4ubaubh‡)rþ4}rÿ4(hTUhUj³4h`hahbhŠhd}r5(hŒX-hi]hh]hf]hg]hl]uhnM hohhp]r5(hŽ)r5}r5(hTXâThe ``head`` kind refers to the latest development branch of the package. This may be used for example to track activity of a project or as an indication to outside developers what sources to get for making new contributions. hUjþ4h`hahbh‘hd}r5(hf]hg]hh]hi]hl]uhnNhohhp]r5h})r5}r5(hTXáThe ``head`` kind refers to the latest development branch of the package. This may be used for example to track activity of a project or as an indication to outside developers what sources to get for making new contributions.hUj5h`hahbhhd}r5(hf]hg]hh]hi]hl]uhnM hp]r 5(hyXThe r 5…r 5}r 5(hTXThe hUj5ubhß)r 5}r5(hTX``head``hd}r5(hf]hg]hh]hi]hl]uhUj5hp]r5hyXheadr5…r5}r5(hTUhUj 5ubahbhçubhyXÕ kind refers to the latest development branch of the package. This may be used for example to track activity of a project or as an indication to outside developers what sources to get for making new contributions.r5…r5}r5(hTXÕ kind refers to the latest development branch of the package. This may be used for example to track activity of a project or as an indication to outside developers what sources to get for making new contributions.hUj5ubeubaubhŽ)r5}r5(hTXâThe ``this`` kind refers to the branch and tag of a repository that contains the sources for this version or release of a package. For most source control systems this involves specifying a tag, id or hash of some form and perhaps a branch. The purpose is to be able to reconstruct the sources corresponding to a particular package version. This might be used to indicate what sources to get if someone needs to fix a bug in an older branch that is no longer an active head branch. hUjþ4h`hahbh‘hd}r5(hf]hg]hh]hi]hl]uhnNhohhp]r5h})r5}r5(hTXáThe ``this`` kind refers to the branch and tag of a repository that contains the sources for this version or release of a package. For most source control systems this involves specifying a tag, id or hash of some form and perhaps a branch. The purpose is to be able to reconstruct the sources corresponding to a particular package version. This might be used to indicate what sources to get if someone needs to fix a bug in an older branch that is no longer an active head branch.hUj5h`hahbhhd}r5(hf]hg]hh]hi]hl]uhnM# hp]r5(hyXThe r5…r 5}r!5(hTXThe hUj5ubhß)r"5}r#5(hTX``this``hd}r$5(hf]hg]hh]hi]hl]uhUj5hp]r%5hyXthisr&5…r'5}r(5(hTUhUj"5ubahbhçubhyXÕ kind refers to the branch and tag of a repository that contains the sources for this version or release of a package. For most source control systems this involves specifying a tag, id or hash of some form and perhaps a branch. The purpose is to be able to reconstruct the sources corresponding to a particular package version. This might be used to indicate what sources to get if someone needs to fix a bug in an older branch that is no longer an active head branch.r)5…r*5}r+5(hTXÕ kind refers to the branch and tag of a repository that contains the sources for this version or release of a package. For most source control systems this involves specifying a tag, id or hash of some form and perhaps a branch. The purpose is to be able to reconstruct the sources corresponding to a particular package version. This might be used to indicate what sources to get if someone needs to fix a bug in an older branch that is no longer an active head branch.hUj5ubeubaubeubh})r,5}r-5(hTX¨You can specify one kind or the other or both. As an example here are the repositories for the Cabal library. Note that the ``this`` kind of repository specifies a tag.hUj³4h`hahbhhd}r.5(hf]hg]hh]hi]hl]uhnM, hohhp]r/5(hyX|You can specify one kind or the other or both. As an example here are the repositories for the Cabal library. Note that the r05…r15}r25(hTX|You can specify one kind or the other or both. As an example here are the repositories for the Cabal library. Note that the h`NhnNhohhUj,5ubhß)r35}r45(hTX``this``hd}r55(hf]hg]hh]hi]hl]uhUj,5hp]r65hyXthisr75…r85}r95(hTUhUj35ubahbhçubhyX$ kind of repository specifies a tag.r:5…r;5}r<5(hTX$ kind of repository specifies a tag.h`NhnNhohhUj,5ubeubjÌ)r=5}r>5(hTXÏsource-repository head type: darcs location: http://darcs.haskell.org/cabal/ source-repository this type: darcs location: http://darcs.haskell.org/cabal-branches/cabal-1.6/ tag: 1.6.1hUj³4h`hahbjÏhd}r?5(jÑjÒhi]hh]hf]hg]hl]uhnM2 hohhp]r@5hyXÏsource-repository head type: darcs location: http://darcs.haskell.org/cabal/ source-repository this type: darcs location: http://darcs.haskell.org/cabal-branches/cabal-1.6/ tag: 1.6.1rA5…rB5}rC5(hTUhUj=5ubaubh})rD5}rE5(hTX The exact fields are as follows:rF5hUj³4h`hahbhhd}rG5(hf]hg]hh]hi]hl]uhnM; hohhp]rH5hyX The exact fields are as follows:rI5…rJ5}rK5(hTjF5h`NhnNhohhUjD5ubaubj¹)rL5}rM5(hTUhUj³4h`hahbj¼hd}rN5(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rO5}rP5(hTUhUj³4h`hahbjÁhd}rQ5(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrR5jÇjR5uhnNhohhp]rS5(jÉ)rT5}rU5(hTX type: tokenhUjO5h`hahbjÍhd}rV5(hi]rW5X pkg-field-source-repository-typerX5ahh]hf]hg]hl]jщuhnML hohhp]rY5(j¹)rZ5}r[5(hTUhUjT5h`hahbj¼hd}r\5(hi]hh]hf]hg]hl]Uentries]r]5(j×X+source-repository:type; package.cabal fieldjX5UNtr^5auhnML hohhp]ubjÙ)r_5}r`5(hTXtypera5hUjT5h`hahbjÜhd}rb5(jÑjÒhi]hh]hf]hg]hl]uhnML hohhp]rc5hyXtyperd5…re5}rf5(hTUh`NhnNhohhUj_5ubaubjâ)rg5}rh5(hTj[hUjT5h`hahbjåhd}ri5(jÑjÒhi]hh]hf]hg]hl]uhnML hohhp]rj5hyX: rk5…rl5}rm5(hTUh`NhnNhohhUjg5ubaubja)rn5}ro5(hTXtokenhUjT5h`hahbjdhd}rp5(jÑjÒhi]hh]hf]hg]hl]uhnML hohhp]rq5hyXtokenrr5…rs5}rt5(hTUh`NhnNhohhUjn5ubaubeubjê)ru5}rv5(hTUhUjO5h`hahbjíhd}rw5(hf]hg]hh]hi]hl]uhnML hohhp]rx5(h})ry5}rz5(hTXcThe name of the source control system used for this repository. The currently recognised types are:r{5hUju5h`hahbhhd}r|5(hf]hg]hh]hi]hl]uhnM? hohhp]r}5hyXcThe name of the source control system used for this repository. The currently recognised types are:r~5…r5}r€5(hTj{5h`NhnNhohhUjy5ubaubh‡)r5}r‚5(hTUhUju5h`hahbhŠhd}rƒ5(hŒX-hi]hh]hf]hg]hl]uhnMB hohhp]r„5(hŽ)r…5}r†5(hTX ``darcs``r‡5hUj5h`hahbh‘hd}rˆ5(hf]hg]hh]hi]hl]uhnNhohhp]r‰5h})rŠ5}r‹5(hTj‡5hUj…5h`hahbhhd}rŒ5(hf]hg]hh]hi]hl]uhnMB hp]r5hß)rŽ5}r5(hTj‡5hd}r5(hf]hg]hh]hi]hl]uhUjŠ5hp]r‘5hyXdarcsr’5…r“5}r”5(hTUhUjŽ5ubahbhçubaubaubhŽ)r•5}r–5(hTX``git``r—5hUj5h`hahbh‘hd}r˜5(hf]hg]hh]hi]hl]uhnNhohhp]r™5h})rš5}r›5(hTj—5hUj•5h`hahbhhd}rœ5(hf]hg]hh]hi]hl]uhnMC hp]r5hß)rž5}rŸ5(hTj—5hd}r 5(hf]hg]hh]hi]hl]uhUjš5hp]r¡5hyXgitr¢5…r£5}r¤5(hTUhUjž5ubahbhçubaubaubhŽ)r¥5}r¦5(hTX``svn``r§5hUj5h`hahbh‘hd}r¨5(hf]hg]hh]hi]hl]uhnNhohhp]r©5h})rª5}r«5(hTj§5hUj¥5h`hahbhhd}r¬5(hf]hg]hh]hi]hl]uhnMD hp]r­5hß)r®5}r¯5(hTj§5hd}r°5(hf]hg]hh]hi]hl]uhUjª5hp]r±5hyXsvnr²5…r³5}r´5(hTUhUj®5ubahbhçubaubaubhŽ)rµ5}r¶5(hTX``cvs``r·5hUj5h`hahbh‘hd}r¸5(hf]hg]hh]hi]hl]uhnNhohhp]r¹5h})rº5}r»5(hTj·5hUjµ5h`hahbhhd}r¼5(hf]hg]hh]hi]hl]uhnME hp]r½5hß)r¾5}r¿5(hTj·5hd}rÀ5(hf]hg]hh]hi]hl]uhUjº5hp]rÁ5hyXcvsrÂ5…rÃ5}rÄ5(hTUhUj¾5ubahbhçubaubaubhŽ)rÅ5}rÆ5(hTX``mercurial`` (or alias ``hg``)rÇ5hUj5h`hahbh‘hd}rÈ5(hf]hg]hh]hi]hl]uhnNhohhp]rÉ5h})rÊ5}rË5(hTjÇ5hUjÅ5h`hahbhhd}rÌ5(hf]hg]hh]hi]hl]uhnMF hp]rÍ5(hß)rÎ5}rÏ5(hTX ``mercurial``hd}rÐ5(hf]hg]hh]hi]hl]uhUjÊ5hp]rÑ5hyX mercurialrÒ5…rÓ5}rÔ5(hTUhUjÎ5ubahbhçubhyX (or alias rÕ5…rÖ5}r×5(hTX (or alias hUjÊ5ubhß)rØ5}rÙ5(hTX``hg``hd}rÚ5(hf]hg]hh]hi]hl]uhUjÊ5hp]rÛ5hyXhgrÜ5…rÝ5}rÞ5(hTUhUjØ5ubahbhçubhyX)…rß5}rà5(hTX)hUjÊ5ubeubaubhŽ)rá5}râ5(hTX``bazaar`` (or alias ``bzr``)rã5hUj5h`hahbh‘hd}rä5(hf]hg]hh]hi]hl]uhnNhohhp]rå5h})ræ5}rç5(hTjã5hUjá5h`hahbhhd}rè5(hf]hg]hh]hi]hl]uhnMG hp]ré5(hß)rê5}rë5(hTX ``bazaar``hd}rì5(hf]hg]hh]hi]hl]uhUjæ5hp]rí5hyXbazaarrî5…rï5}rð5(hTUhUjê5ubahbhçubhyX (or alias rñ5…rò5}ró5(hTX (or alias hUjæ5ubhß)rô5}rõ5(hTX``bzr``hd}rö5(hf]hg]hh]hi]hl]uhUjæ5hp]r÷5hyXbzrrø5…rù5}rú5(hTUhUjô5ubahbhçubhyX)…rû5}rü5(hTX)hUjæ5ubeubaubhŽ)rý5}rþ5(hTX``arch``rÿ5hUj5h`hahbh‘hd}r6(hf]hg]hh]hi]hl]uhnNhohhp]r6h})r6}r6(hTjÿ5hUjý5h`hahbhhd}r6(hf]hg]hh]hi]hl]uhnMH hp]r6hß)r6}r6(hTjÿ5hd}r6(hf]hg]hh]hi]hl]uhUj6hp]r 6hyXarchr 6…r 6}r 6(hTUhUj6ubahbhçubaubaubhŽ)r 6}r6(hTX ``monotone`` hUj5h`hahbh‘hd}r6(hf]hg]hh]hi]hl]uhnNhohhp]r6h})r6}r6(hTX ``monotone``r6hUj 6h`hahbhhd}r6(hf]hg]hh]hi]hl]uhnMI hp]r6hß)r6}r6(hTj6hd}r6(hf]hg]hh]hi]hl]uhUj6hp]r6hyXmonotoner6…r6}r6(hTUhUj6ubahbhçubaubaubeubh})r6}r6(hTXThis field is required.r6hUju5h`hahbhhd}r 6(hf]hg]hh]hi]hl]uhnMK hohhp]r!6hyXThis field is required.r"6…r#6}r$6(hTj6h`NhnNhohhUj6ubaubeubeubj¹)r%6}r&6(hTUhUj³4h`hahbj¼hd}r'6(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r(6}r)6(hTUhUj³4h`hahbjÁhd}r*6(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr+6jÇj+6uhnNhohhp]r,6(jÉ)r-6}r.6(hTX location: URLhUj(6h`hahbjÍhd}r/6(hi]r06X$pkg-field-source-repository-locationr16ahh]hf]hg]hl]jщuhnMW hohhp]r26(j¹)r36}r46(hTUhUj-6h`hahbj¼hd}r56(hi]hh]hf]hg]hl]Uentries]r66(j×X/source-repository:location; package.cabal fieldj16UNtr76auhnMW hohhp]ubjÙ)r86}r96(hTXlocationr:6hUj-6h`hahbjÜhd}r;6(jÑjÒhi]hh]hf]hg]hl]uhnMW hohhp]r<6hyXlocationr=6…r>6}r?6(hTUh`NhnNhohhUj86ubaubjâ)r@6}rA6(hTj[hUj-6h`hahbjåhd}rB6(jÑjÒhi]hh]hf]hg]hl]uhnMW hohhp]rC6hyX: rD6…rE6}rF6(hTUh`NhnNhohhUj@6ubaubja)rG6}rH6(hTXURLhUj-6h`hahbjdhd}rI6(jÑjÒhi]hh]hf]hg]hl]uhnMW hohhp]rJ6hyXURLrK6…rL6}rM6(hTUh`NhnNhohhUjG6ubaubeubjê)rN6}rO6(hTUhUj(6h`hahbjíhd}rP6(hf]hg]hh]hi]hl]uhnMW hohhp]rQ6(h})rR6}rS6(hTXiThe location of the repository. The exact form of this field depends on the repository type. For example:rT6hUjN6h`hahbhhd}rU6(hf]hg]hh]hi]hl]uhnMO hohhp]rV6hyXiThe location of the repository. The exact form of this field depends on the repository type. For example:rW6…rX6}rY6(hTjT6h`NhnNhohhUjR6ubaubh‡)rZ6}r[6(hTUhUjN6h`hahbhŠhd}r\6(hŒX-hi]hh]hf]hg]hl]uhnMR hohhp]r]6(hŽ)r^6}r_6(hTX+for darcs: ``http://code.haskell.org/foo/``r`6hUjZ6h`hahbh‘hd}ra6(hf]hg]hh]hi]hl]uhnNhohhp]rb6h})rc6}rd6(hTj`6hUj^6h`hahbhhd}re6(hf]hg]hh]hi]hl]uhnMR hp]rf6(hyX for darcs: rg6…rh6}ri6(hTX for darcs: hUjc6ubhß)rj6}rk6(hTX ``http://code.haskell.org/foo/``hd}rl6(hf]hg]hh]hi]hl]uhUjc6hp]rm6hyXhttp://code.haskell.org/foo/rn6…ro6}rp6(hTUhUjj6ubahbhçubeubaubhŽ)rq6}rr6(hTX)for git: ``git://github.com/foo/bar.git``rs6hUjZ6h`hahbh‘hd}rt6(hf]hg]hh]hi]hl]uhnNhohhp]ru6h})rv6}rw6(hTjs6hUjq6h`hahbhhd}rx6(hf]hg]hh]hi]hl]uhnMS hp]ry6(hyX for git: rz6…r{6}r|6(hTX for git: hUjv6ubhß)r}6}r~6(hTX ``git://github.com/foo/bar.git``hd}r6(hf]hg]hh]hi]hl]uhUjv6hp]r€6hyXgit://github.com/foo/bar.gitr6…r‚6}rƒ6(hTUhUj}6ubahbhçubeubaubhŽ)r„6}r…6(hTX&for CVS: ``anoncvs@cvs.foo.org:/cvs`` hUjZ6h`hahbh‘hd}r†6(hf]hg]hh]hi]hl]uhnNhohhp]r‡6h})rˆ6}r‰6(hTX%for CVS: ``anoncvs@cvs.foo.org:/cvs``rŠ6hUj„6h`hahbhhd}r‹6(hf]hg]hh]hi]hl]uhnMT hp]rŒ6(hyX for CVS: r6…rŽ6}r6(hTX for CVS: hUjˆ6ubhß)r6}r‘6(hTX``anoncvs@cvs.foo.org:/cvs``hd}r’6(hf]hg]hh]hi]hl]uhUjˆ6hp]r“6hyXanoncvs@cvs.foo.org:/cvsr”6…r•6}r–6(hTUhUj6ubahbhçubeubaubeubh})r—6}r˜6(hTXThis field is required.r™6hUjN6h`hahbhhd}rš6(hf]hg]hh]hi]hl]uhnMV hohhp]r›6hyXThis field is required.rœ6…r6}rž6(hTj™6h`NhnNhohhUj—6ubaubeubeubj¹)rŸ6}r 6(hTUhUj³4h`hahbj¼hd}r¡6(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r¢6}r£6(hTUhUj³4h`hahbjÁhd}r¤6(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr¥6jÇj¥6uhnNhohhp]r¦6(jÉ)r§6}r¨6(hTX module: tokenhUj¢6h`hahbjÍhd}r©6(hi]rª6X"pkg-field-source-repository-moduler«6ahh]hf]hg]hl]jщuhnM_ hohhp]r¬6(j¹)r­6}r®6(hTUhUj§6h`hahbj¼hd}r¯6(hi]hh]hf]hg]hl]Uentries]r°6(j×X-source-repository:module; package.cabal fieldj«6UNtr±6auhnM_ hohhp]ubjÙ)r²6}r³6(hTXmoduler´6hUj§6h`hahbjÜhd}rµ6(jÑjÒhi]hh]hf]hg]hl]uhnM_ hohhp]r¶6hyXmoduler·6…r¸6}r¹6(hTUh`NhnNhohhUj²6ubaubjâ)rº6}r»6(hTj[hUj§6h`hahbjåhd}r¼6(jÑjÒhi]hh]hf]hg]hl]uhnM_ hohhp]r½6hyX: r¾6…r¿6}rÀ6(hTUh`NhnNhohhUjº6ubaubja)rÁ6}rÂ6(hTXtokenhUj§6h`hahbjdhd}rÃ6(jÑjÒhi]hh]hf]hg]hl]uhnM_ hohhp]rÄ6hyXtokenrÅ6…rÆ6}rÇ6(hTUh`NhnNhohhUjÁ6ubaubeubjê)rÈ6}rÉ6(hTUhUj¢6h`hahbjíhd}rÊ6(hf]hg]hh]hi]hl]uhnM_ hohhp]rË6(h})rÌ6}rÍ6(hTXUCVS requires a named module, as each CVS server can host multiple named repositories.rÎ6hUjÈ6h`hahbhhd}rÏ6(hf]hg]hh]hi]hl]uhnMZ hohhp]rÐ6hyXUCVS requires a named module, as each CVS server can host multiple named repositories.rÑ6…rÒ6}rÓ6(hTjÎ6h`NhnNhohhUjÌ6ubaubh})rÔ6}rÕ6(hTXTThis field is required for the CVS repository type and should not be used otherwise.rÖ6hUjÈ6h`hahbhhd}r×6(hf]hg]hh]hi]hl]uhnM] hohhp]rØ6hyXTThis field is required for the CVS repository type and should not be used otherwise.rÙ6…rÚ6}rÛ6(hTjÖ6h`NhnNhohhUjÔ6ubaubeubeubj¹)rÜ6}rÝ6(hTUhUj³4h`hahbj¼hd}rÞ6(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rß6}rà6(hTUhUj³4h`hahbjÁhd}rá6(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrâ6jÇjâ6uhnNhohhp]rã6(jÉ)rä6}rå6(hTX branch: tokenhUjß6h`hahbjÍhd}ræ6(hi]rç6X"pkg-field-source-repository-branchrè6ahh]hf]hg]hl]jщuhnMi hohhp]ré6(j¹)rê6}rë6(hTUhUjä6h`hahbj¼hd}rì6(hi]hh]hf]hg]hl]Uentries]rí6(j×X-source-repository:branch; package.cabal fieldjè6UNtrî6auhnMi hohhp]ubjÙ)rï6}rð6(hTXbranchrñ6hUjä6h`hahbjÜhd}rò6(jÑjÒhi]hh]hf]hg]hl]uhnMi hohhp]ró6hyXbranchrô6…rõ6}rö6(hTUh`NhnNhohhUjï6ubaubjâ)r÷6}rø6(hTj[hUjä6h`hahbjåhd}rù6(jÑjÒhi]hh]hf]hg]hl]uhnMi hohhp]rú6hyX: rû6…rü6}rý6(hTUh`NhnNhohhUj÷6ubaubja)rþ6}rÿ6(hTXtokenhUjä6h`hahbjdhd}r7(jÑjÒhi]hh]hf]hg]hl]uhnMi hohhp]r7hyXtokenr7…r7}r7(hTUh`NhnNhohhUjþ6ubaubeubjê)r7}r7(hTUhUjß6h`hahbjíhd}r7(hf]hg]hh]hi]hl]uhnMi hohhp]r7(h})r 7}r 7(hTXIMany source control systems support the notion of a branch, as a distinct concept from having repositories in separate locations. For example CVS, SVN and git use branches while for darcs uses different locations for different branches. If you need to specify a branch to identify a your repository then specify it in this field.r 7hUj7h`hahbhhd}r 7(hf]hg]hh]hi]hl]uhnMb hohhp]r 7hyXIMany source control systems support the notion of a branch, as a distinct concept from having repositories in separate locations. For example CVS, SVN and git use branches while for darcs uses different locations for different branches. If you need to specify a branch to identify a your repository then specify it in this field.r7…r7}r7(hTj 7h`NhnNhohhUj 7ubaubh})r7}r7(hTXThis field is optional.r7hUj7h`hahbhhd}r7(hf]hg]hh]hi]hl]uhnMh hohhp]r7hyXThis field is optional.r7…r7}r7(hTj7h`NhnNhohhUj7ubaubeubeubj¹)r7}r7(hTUhUj³4h`hahbj¼hd}r7(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r7}r7(hTUhUj³4h`hahbjÁhd}r7(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr7jÇj7uhnNhohhp]r 7(jÉ)r!7}r"7(hTX tag: tokenhUj7h`hahbjÍhd}r#7(hi]r$7Xpkg-field-source-repository-tagr%7ahh]hf]hg]hl]jщuhnMr hohhp]r&7(j¹)r'7}r(7(hTUhUj!7h`hahbj¼hd}r)7(hi]hh]hf]hg]hl]Uentries]r*7(j×X*source-repository:tag; package.cabal fieldj%7UNtr+7auhnMr hohhp]ubjÙ)r,7}r-7(hTXtagr.7hUj!7h`hahbjÜhd}r/7(jÑjÒhi]hh]hf]hg]hl]uhnMr hohhp]r07hyXtagr17…r27}r37(hTUh`NhnNhohhUj,7ubaubjâ)r47}r57(hTj[hUj!7h`hahbjåhd}r67(jÑjÒhi]hh]hf]hg]hl]uhnMr hohhp]r77hyX: r87…r97}r:7(hTUh`NhnNhohhUj47ubaubja)r;7}r<7(hTXtokenhUj!7h`hahbjdhd}r=7(jÑjÒhi]hh]hf]hg]hl]uhnMr hohhp]r>7hyXtokenr?7…r@7}rA7(hTUh`NhnNhohhUj;7ubaubeubjê)rB7}rC7(hTUhUj7h`hahbjíhd}rD7(hf]hg]hh]hi]hl]uhnMr hohhp]rE7(h})rF7}rG7(hTX A tag identifies a particular state of a source repository. The tag can be used with a ``this`` repository kind to identify the state of a repository corresponding to a particular package version or release. The exact form of the tag depends on the repository type.hUjB7h`hahbhhd}rH7(hf]hg]hh]hi]hl]uhnMl hohhp]rI7(hyXWA tag identifies a particular state of a source repository. The tag can be used with a rJ7…rK7}rL7(hTXWA tag identifies a particular state of a source repository. The tag can be used with a h`NhnNhohhUjF7ubhß)rM7}rN7(hTX``this``hd}rO7(hf]hg]hh]hi]hl]uhUjF7hp]rP7hyXthisrQ7…rR7}rS7(hTUhUjM7ubahbhçubhyXª repository kind to identify the state of a repository corresponding to a particular package version or release. The exact form of the tag depends on the repository type.rT7…rU7}rV7(hTXª repository kind to identify the state of a repository corresponding to a particular package version or release. The exact form of the tag depends on the repository type.h`NhnNhohhUjF7ubeubh})rW7}rX7(hTX8This field is required for the ``this`` repository kind.hUjB7h`hahbhhd}rY7(hf]hg]hh]hi]hl]uhnMq hohhp]rZ7(hyXThis field is required for the r[7…r\7}r]7(hTXThis field is required for the h`NhnNhohhUjW7ubhß)r^7}r_7(hTX``this``hd}r`7(hf]hg]hh]hi]hl]uhUjW7hp]ra7hyXthisrb7…rc7}rd7(hTUhUj^7ubahbhçubhyX repository kind.re7…rf7}rg7(hTX repository kind.h`NhnNhohhUjW7ubeubeubeubj¹)rh7}ri7(hTUhUj³4h`hahbj¼hd}rj7(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rk7}rl7(hTUhUj³4h`hahbjÁhd}rm7(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrn7jÇjn7uhnNhohhp]ro7(jÉ)rp7}rq7(hTXsubdir: directoryhUjk7h`hahbjÍhd}rr7(hi]rs7X"pkg-field-source-repository-subdirrt7ahh]hf]hg]hl]jщuhnM} hohhp]ru7(j¹)rv7}rw7(hTUhUjp7h`hahbj¼hd}rx7(hi]hh]hf]hg]hl]Uentries]ry7(j×X-source-repository:subdir; package.cabal fieldjt7UNtrz7auhnM} hohhp]ubjÙ)r{7}r|7(hTXsubdirr}7hUjp7h`hahbjÜhd}r~7(jÑjÒhi]hh]hf]hg]hl]uhnM} hohhp]r7hyXsubdirr€7…r7}r‚7(hTUh`NhnNhohhUj{7ubaubjâ)rƒ7}r„7(hTj[hUjp7h`hahbjåhd}r…7(jÑjÒhi]hh]hf]hg]hl]uhnM} hohhp]r†7hyX: r‡7…rˆ7}r‰7(hTUh`NhnNhohhUjƒ7ubaubja)rŠ7}r‹7(hTX directoryhUjp7h`hahbjdhd}rŒ7(jÑjÒhi]hh]hf]hg]hl]uhnM} hohhp]r7hyX directoryrŽ7…r7}r7(hTUh`NhnNhohhUjŠ7ubaubeubjê)r‘7}r’7(hTUhUjk7h`hahbjíhd}r“7(hf]hg]hh]hi]hl]uhnM} hohhp]r”7(h})r•7}r–7(hTXSome projects put the sources for multiple packages under a single source repository. This field lets you specify the relative path from the root of the repository to the top directory for the package, i.e. the directory containing the package's ``.cabal`` file.hUj‘7h`hahbhhd}r—7(hf]hg]hh]hi]hl]uhnMu hohhp]r˜7(hyXøSome projects put the sources for multiple packages under a single source repository. This field lets you specify the relative path from the root of the repository to the top directory for the package, i.e. the directory containing the package’s r™7…rš7}r›7(hTXöSome projects put the sources for multiple packages under a single source repository. This field lets you specify the relative path from the root of the repository to the top directory for the package, i.e. the directory containing the package's h`NhnNhohhUj•7ubhß)rœ7}r7(hTX ``.cabal``hd}rž7(hf]hg]hh]hi]hl]uhUj•7hp]rŸ7hyX.cabalr 7…r¡7}r¢7(hTUhUjœ7ubahbhçubhyX file.r£7…r¤7}r¥7(hTX file.h`NhnNhohhUj•7ubeubh})r¦7}r§7(hTXfThis field is optional. It default to empty which corresponds to the root directory of the repository.r¨7hUj‘7h`hahbhhd}r©7(hf]hg]hh]hi]hl]uhnM{ hohhp]rª7hyXfThis field is optional. It default to empty which corresponds to the root directory of the repository.r«7…r¬7}r­7(hTj¨7h`NhnNhohhUj¦7ubaubeubeubeubhV)r®7}r¯7(hTUhUh\h`hahbhchd}r°7(hf]hg]hh]hi]r±7Udownloading-a-package-s-sourcer²7ahl]r³7h auhnM hohhp]r´7(hr)rµ7}r¶7(hTXDownloading a package's sourcer·7hUj®7h`hahbhvhd}r¸7(hf]hg]hh]hi]hl]uhnM hohhp]r¹7hyX Downloading a package’s sourcerº7…r»7}r¼7(hTj·7h`NhnNhohhUjµ7ubaubh})r½7}r¾7(hTXÐThe ``cabal get`` command allows to access a package's source code - either by unpacking a tarball downloaded from Hackage (the default) or by checking out a working copy from the package's source repository.hUj®7h`hahbhhd}r¿7(hf]hg]hh]hi]hl]uhnM hohhp]rÀ7(hyXThe rÁ7…rÂ7}rÃ7(hTXThe h`NhnNhohhUj½7ubhß)rÄ7}rÅ7(hTX ``cabal get``hd}rÆ7(hf]hg]hh]hi]hl]uhUj½7hp]rÇ7hyX cabal getrÈ7…rÉ7}rÊ7(hTUhUjÄ7ubahbhçubhyXà command allows to access a package’s source code - either by unpacking a tarball downloaded from Hackage (the default) or by checking out a working copy from the package’s source repository.rË7…rÌ7}rÍ7(hTX¿ command allows to access a package's source code - either by unpacking a tarball downloaded from Hackage (the default) or by checking out a working copy from the package's source repository.h`NhnNhohhUj½7ubeubjÌ)rÎ7}rÏ7(hTX$ cabal get [FLAGS] PACKAGEShUj®7h`hahbjÏhd}rÐ7(jÑjÒhi]hh]hf]hg]hl]uhnM‡ hohhp]rÑ7hyX$ cabal get [FLAGS] PACKAGESrÒ7…rÓ7}rÔ7(hTUhUjÎ7ubaubh})rÕ7}rÖ7(hTX3The ``get`` command supports the following options:r×7hUj®7h`hahbhhd}rØ7(hf]hg]hh]hi]hl]uhnM‰ hohhp]rÙ7(hyXThe rÚ7…rÛ7}rÜ7(hTXThe h`NhnNhohhUjÕ7ubhß)rÝ7}rÞ7(hTX``get``hd}rß7(hf]hg]hh]hi]hl]uhUjÕ7hp]rà7hyXgetrá7…râ7}rã7(hTUhUjÝ7ubahbhçubhyX( command supports the following options:rä7…rå7}ræ7(hTX( command supports the following options:h`NhnNhohhUjÕ7ubeubj)rç7}rè7(hTUhUj®7h`hahbjhd}ré7(hf]hg]hh]hi]hl]uhnNhohhp]rê7(j)rë7}rì7(hTXq``-d --destdir`` *PATH* Where to place the package source, defaults to (a subdirectory of) the current directory.hUjç7h`hahbjhd}rí7(hf]hg]hh]hi]hl]uhnMŒ hp]rî7(j)rï7}rð7(hTX``-d --destdir`` *PATH*rñ7hUjë7h`hahbj hd}rò7(hf]hg]hh]hi]hl]uhnMŒ hp]ró7(hß)rô7}rõ7(hTX``-d --destdir``hd}rö7(hf]hg]hh]hi]hl]uhUjï7hp]r÷7hyX -d --destdirrø7…rù7}rú7(hTUhUjô7ubahbhçubhyX …rû7}rü7(hTX hUjï7ubh¿)rý7}rþ7(hTX*PATH*hd}rÿ7(hf]hg]hh]hi]hl]uhUjï7hp]r8hyXPATHr8…r8}r8(hTUhUjý7ubahbhÇubeubj3)r8}r8(hTUhd}r8(hf]hg]hh]hi]hl]uhUjë7hp]r8h})r8}r 8(hTXYWhere to place the package source, defaults to (a subdirectory of) the current directory.r 8hUj8h`hahbhhd}r 8(hf]hg]hh]hi]hl]uhnMŒ hp]r 8hyXYWhere to place the package source, defaults to (a subdirectory of) the current directory.r 8…r8}r8(hTj 8hUj8ubaubahbjMubeubj)r8}r8(hTXÄ``-s --source-repository`` *[head\|this\|...]* Fork the package's source repository using the appropriate version control system. The optional argument allows to choose a specific repository kind.hUjç7h`hahbjhd}r8(hf]hg]hh]hi]hl]uhnM hohhp]r8(j)r8}r8(hTX.``-s --source-repository`` *[head\|this\|...]*r8hUj8h`hahbj hd}r8(hf]hg]hh]hi]hl]uhnM hp]r8(hß)r8}r8(hTX``-s --source-repository``hd}r8(hf]hg]hh]hi]hl]uhUj8hp]r8hyX-s --source-repositoryr8…r8}r8(hTUhUj8ubahbhçubhyX …r 8}r!8(hTX hUj8ubh¿)r"8}r#8(hTX*[head\|this\|...]*hd}r$8(hf]hg]hh]hi]hl]uhUj8hp]r%8hyX[head|this|…]r&8…r'8}r(8(hTUhUj"8ubahbhÇubeubj3)r)8}r*8(hTUhd}r+8(hf]hg]hh]hi]hl]uhUj8hp]r,8h})r-8}r.8(hTX•Fork the package's source repository using the appropriate version control system. The optional argument allows to choose a specific repository kind.r/8hUj)8h`hahbhhd}r08(hf]hg]hh]hi]hl]uhnM hp]r18hyX—Fork the package’s source repository using the appropriate version control system. The optional argument allows to choose a specific repository kind.r28…r38}r48(hTj/8hUj-8ubaubahbjMubeubj)r58}r68(hTX’``--index-state`` *[HEAD\|@\|]* Use source package index state as it existed at a previous time. Accepts unix-timestamps (e.g. ``@1474732068``), ISO8601 UTC timestamps (e.g. ``2016-09-24T17:47:48Z``), or ``HEAD`` (default). This determines which package versions are available as well as which ``.cabal`` file revision is selected (unless ``--pristine`` is used).hUjç7h`hahbjhd}r78(hf]hg]hh]hi]hl]uhnM– hohhp]r88(j)r98}r:8(hTXF``--index-state`` *[HEAD\|@\|]*r;8hUj58h`hahbj hd}r<8(hf]hg]hh]hi]hl]uhnM– hp]r=8(hß)r>8}r?8(hTX``--index-state``hd}r@8(hf]hg]hh]hi]hl]uhUj98hp]rA8hyX --index-staterB8…rC8}rD8(hTUhUj>8ubahbhçubhyX …rE8}rF8(hTX hUj98ubh¿)rG8}rH8(hTX4*[HEAD\|@\|]*hd}rI8(hf]hg]hh]hi]hl]uhUj98hp]rJ8hyX0[HEAD|@|]rK8…rL8}rM8(hTUhUjG8ubahbhÇubeubj3)rN8}rO8(hTUhd}rP8(hf]hg]hh]hi]hl]uhUj58hp]rQ8h})rR8}rS8(hTXKUse source package index state as it existed at a previous time. Accepts unix-timestamps (e.g. ``@1474732068``), ISO8601 UTC timestamps (e.g. ``2016-09-24T17:47:48Z``), or ``HEAD`` (default). This determines which package versions are available as well as which ``.cabal`` file revision is selected (unless ``--pristine`` is used).hUjN8h`hahbhhd}rT8(hf]hg]hh]hi]hl]uhnM“ hp]rU8(hyX_Use source package index state as it existed at a previous time. Accepts unix-timestamps (e.g. rV8…rW8}rX8(hTX_Use source package index state as it existed at a previous time. Accepts unix-timestamps (e.g. hUjR8ubhß)rY8}rZ8(hTX``@1474732068``hd}r[8(hf]hg]hh]hi]hl]uhUjR8hp]r\8hyX @1474732068r]8…r^8}r_8(hTUhUjY8ubahbhçubhyX ), ISO8601 UTC timestamps (e.g. r`8…ra8}rb8(hTX ), ISO8601 UTC timestamps (e.g. hUjR8ubhß)rc8}rd8(hTX``2016-09-24T17:47:48Z``hd}re8(hf]hg]hh]hi]hl]uhUjR8hp]rf8hyX2016-09-24T17:47:48Zrg8…rh8}ri8(hTUhUjc8ubahbhçubhyX), or rj8…rk8}rl8(hTX), or hUjR8ubhß)rm8}rn8(hTX``HEAD``hd}ro8(hf]hg]hh]hi]hl]uhUjR8hp]rp8hyXHEADrq8…rr8}rs8(hTUhUjm8ubahbhçubhyXR (default). This determines which package versions are available as well as which rt8…ru8}rv8(hTXR (default). This determines which package versions are available as well as which hUjR8ubhß)rw8}rx8(hTX ``.cabal``hd}ry8(hf]hg]hh]hi]hl]uhUjR8hp]rz8hyX.cabalr{8…r|8}r}8(hTUhUjw8ubahbhçubhyX# file revision is selected (unless r~8…r8}r€8(hTX# file revision is selected (unless hUjR8ubhß)r8}r‚8(hTX``--pristine``hd}rƒ8(hf]hg]hh]hi]hl]uhUjR8hp]r„8hyX --pristiner…8…r†8}r‡8(hTUhUj8ubahbhçubhyX is used).rˆ8…r‰8}rŠ8(hTX is used).hUjR8ubeubahbjMubeubj)r‹8}rŒ8(hTX‘``--pristine`` Unpack the original pristine tarball, rather than updating the ``.cabal`` file with the latest revision from the package archive. hUjç7h`hahbjhd}r8(hf]hg]hh]hi]hl]uhnMš hohhp]rŽ8(j)r8}r8(hTX``--pristine``r‘8hUj‹8h`hahbj hd}r’8(hf]hg]hh]hi]hl]uhnMš hp]r“8hß)r”8}r•8(hTj‘8hd}r–8(hf]hg]hh]hi]hl]uhUj8hp]r—8hyX --pristiner˜8…r™8}rš8(hTUhUj”8ubahbhçubaubj3)r›8}rœ8(hTUhd}r8(hf]hg]hh]hi]hl]uhUj‹8hp]rž8h})rŸ8}r 8(hTXUnpack the original pristine tarball, rather than updating the ``.cabal`` file with the latest revision from the package archive.hUj›8h`hahbhhd}r¡8(hf]hg]hh]hi]hl]uhnM™ hp]r¢8(hyX?Unpack the original pristine tarball, rather than updating the r£8…r¤8}r¥8(hTX?Unpack the original pristine tarball, rather than updating the hUjŸ8ubhß)r¦8}r§8(hTX ``.cabal``hd}r¨8(hf]hg]hh]hi]hl]uhUjŸ8hp]r©8hyX.cabalrª8…r«8}r¬8(hTUhUj¦8ubahbhçubhyX8 file with the latest revision from the package archive.r­8…r®8}r¯8(hTX8 file with the latest revision from the package archive.hUjŸ8ubeubahbjMubeubeubeubeubh`hahbhchd}r°8(hf]hg]hh]hi]r±8U benchmarksr²8ahl]r³8hGauhnM’hohhp]r´8(hr)rµ8}r¶8(hTX Benchmarksr·8hUhZh`hahbhvhd}r¸8(hf]hg]hh]hi]hl]uhnM’hohhp]r¹8hyX Benchmarksrº8…r»8}r¼8(hTj·8h`NhnNhohhUjµ8ubaubj¹)r½8}r¾8(hTUhUhZh`hahbj¼hd}r¿8(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rÀ8}rÁ8(hTUhUhZh`hahbjÁhd}rÂ8(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-sectionrÃ8jÇjÃ8uhnNhohhp]rÄ8(jÉ)rÅ8}rÆ8(hTXbenchmark namehUjÀ8h`hahbjÍhd}rÇ8(hi]rÈ8Xpkg-section-benchmark-benchmarkrÉ8ahh]hf]hg]hl]jщuhnNhohhp]rÊ8(j¹)rË8}rÌ8(hTUhUjÅ8h`hahbj¼hd}rÍ8(hi]hh]hf]hg]hl]Uentries]rÎ8(j×X*benchmark:benchmark; package.cabal sectionjÉ8UNtrÏ8auhnNhohhp]ubjÙ)rÐ8}rÑ8(hTX benchmarkrÒ8hUjÅ8h`hahbjÜhd}rÓ8(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rÔ8hyX benchmarkrÕ8…rÖ8}r×8(hTUh`NhnNhohhUjÐ8ubaubjâ)rØ8}rÙ8(hTU hUjÅ8h`hahbjåhd}rÚ8(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rÛ8hyX …rÜ8}rÝ8(hTUh`NhnNhohhUjØ8ubaubja)rÞ8}rß8(hTXnamehUjÅ8h`hahbjdhd}rà8(jÑjÒhi]hh]hf]hg]hl]uhnNhohhp]rá8hyXnamerâ8…rã8}rä8(hTUh`NhnNhohhUjÞ8ubaubeubjê)rå8}ræ8(hTUhUjÀ8h`hahbjíhd}rç8(hf]hg]hh]hi]hl]uhnNhohhp]rè8(jð)ré8}rê8(hTUhUjå8h`hahbjóhd}rë8(hf]hg]hh]hi]hl]uhnNhohhp]rì8jö)rí8}rî8(hTUhUjé8h`hahbjùhd}rï8(hf]hg]hh]hi]hl]uhnNhohhp]rð8(jü)rñ8}rò8(hTjÿhUjí8h`hahbjhd}ró8(hf]hg]hh]hi]hl]uhnKhp]rô8hyXSincerõ8…rö8}r÷8(hTUhUjñ8ubaubj)rø8}rù8(hTU Cabal 1.9.2rú8hd}rû8(hf]hg]hh]hi]hl]uhUjí8hp]rü8h})rý8}rþ8(hTjú8hd}rÿ8(hf]hg]hh]hi]hl]uhUjø8hp]r9hyX Cabal 1.9.2r9…r9}r9(hTUhUjý8ubahbhubahbjubeubaubh})r9}r9(hTX¶Benchmark sections (if present) describe benchmarks contained in the package and must have an argument after the section label, which defines the name of the benchmark. This is a freeform argument, but may not contain spaces. It should be unique among the names of the package's other benchmarks, the package's test suites, the package's executables, and the package itself. Using benchmark sections requires at least Cabal version 1.9.2.r9hUjå8h`hahbhhd}r9(hf]hg]hh]hi]hl]uhnM˜hohhp]r9hyX¼Benchmark sections (if present) describe benchmarks contained in the package and must have an argument after the section label, which defines the name of the benchmark. This is a freeform argument, but may not contain spaces. It should be unique among the names of the package’s other benchmarks, the package’s test suites, the package’s executables, and the package itself. Using benchmark sections requires at least Cabal version 1.9.2.r 9…r 9}r 9(hTj9h`NhnNhohhUj9ubaubeubeubh})r 9}r 9(hTX‰The benchmark may be described using the following fields, as well as build information fields (see the section on `build information`_).hUhZh`hahbhhd}r9(hf]hg]hh]hi]hl]uhnM hohhp]r9(hyXsThe benchmark may be described using the following fields, as well as build information fields (see the section on r9…r9}r9(hTXsThe benchmark may be described using the following fields, as well as build information fields (see the section on h`NhnNhohhUj 9ubj?)r9}r9(hTX`build information`_jBKhUj 9hbjChd}r9(UnameXbuild informationhi]hh]hf]hg]hl]jEj(uhp]r9hyXbuild informationr9…r9}r9(hTUhUj9ubaubhyX).r9…r9}r9(hTX).h`NhnNhohhUj 9ubeubj¹)r9}r9(hTUhUhZh`hahbj¼hd}r9(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)r 9}r!9(hTUhUhZh`hahbjÁhd}r"9(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldr#9jÇj#9uhnNhohhp]r$9(jÉ)r%9}r&9(hTXtype: interface (required)hUj 9h`hahbjÍhd}r'9(hi]r(9Xpkg-field-benchmark-typer)9ahh]hf]hg]hl]jщuhnM§hohhp]r*9(j¹)r+9}r,9(hTUhUj%9h`hahbj¼hd}r-9(hi]hh]hf]hg]hl]Uentries]r.9(j×X#benchmark:type; package.cabal fieldj)9UNtr/9auhnM§hohhp]ubjÙ)r09}r19(hTXtyper29hUj%9h`hahbjÜhd}r39(jÑjÒhi]hh]hf]hg]hl]uhnM§hohhp]r49hyXtyper59…r69}r79(hTUh`NhnNhohhUj09ubaubjâ)r89}r99(hTj[hUj%9h`hahbjåhd}r:9(jÑjÒhi]hh]hf]hg]hl]uhnM§hohhp]r;9hyX: r<9…r=9}r>9(hTUh`NhnNhohhUj89ubaubja)r?9}r@9(hTXinterface (required)hUj%9h`hahbjdhd}rA9(jÑjÒhi]hh]hf]hg]hl]uhnM§hohhp]rB9hyXinterface (required)rC9…rD9}rE9(hTUh`NhnNhohhUj?9ubaubeubjê)rF9}rG9(hTUhUj 9h`hahbjíhd}rH9(hf]hg]hh]hi]hl]uhnM§hohhp]rI9h})rJ9}rK9(hTX‰The interface type and version of the benchmark. At the moment Cabal only support one benchmark interface, called ``exitcode-stdio-1.0``.hUjF9h`hahbhhd}rL9(hf]hg]hh]hi]hl]uhnM¥hohhp]rM9(hyXrThe interface type and version of the benchmark. At the moment Cabal only support one benchmark interface, called rN9…rO9}rP9(hTXrThe interface type and version of the benchmark. At the moment Cabal only support one benchmark interface, called h`NhnNhohhUjJ9ubhß)rQ9}rR9(hTX``exitcode-stdio-1.0``hd}rS9(hf]hg]hh]hi]hl]uhUjJ9hp]rT9hyXexitcode-stdio-1.0rU9…rV9}rW9(hTUhUjQ9ubahbhçubhyX.…rX9}rY9(hTX.h`NhnNhohhUjJ9ubeubaubeubh})rZ9}r[9(hTXðBenchmarks using the ``exitcode-stdio-1.0`` interface are executables that indicate failure to run the benchmark with a non-zero exit code when run; they may provide human-readable information through the standard output and error channels.hUhZh`hahbhhd}r\9(hf]hg]hh]hi]hl]uhnM¨hohhp]r]9(hyXBenchmarks using the r^9…r_9}r`9(hTXBenchmarks using the h`NhnNhohhUjZ9ubhß)ra9}rb9(hTX``exitcode-stdio-1.0``hd}rc9(hf]hg]hh]hi]hl]uhUjZ9hp]rd9hyXexitcode-stdio-1.0re9…rf9}rg9(hTUhUja9ubahbhçubhyXÅ interface are executables that indicate failure to run the benchmark with a non-zero exit code when run; they may provide human-readable information through the standard output and error channels.rh9…ri9}rj9(hTXÅ interface are executables that indicate failure to run the benchmark with a non-zero exit code when run; they may provide human-readable information through the standard output and error channels.h`NhnNhohhUjZ9ubeubj¹)rk9}rl9(hTUhUhZh`hahbj¼hd}rm9(hi]hh]hf]hg]hl]Uentries]uhnNhohhp]ubj¾)rn9}ro9(hTUhUhZh`hahbjÁhd}rp9(jÉjÄXcabalhi]hh]hf]hg]hl]jÅX pkg-fieldrq9jÇjq9uhnNhohhp]rr9(jÉ)rs9}rt9(hTXmain-is: filenamehUjn9h`hahbjÍhd}ru9(hi]rv9Xpkg-field-benchmark-main-isrw9ahh]hf]hg]hl]jщuhnM·hohhp]rx9(j¹)ry9}rz9(hTUhUjs9h`hahbj¼hd}r{9(hi]hh]hf]hg]hl]Uentries]r|9(j×X&benchmark:main-is; package.cabal fieldjw9UNtr}9auhnM·hohhp]ubjÙ)r~9}r9(hTXmain-isr€9hUjs9h`hahbjÜhd}r9(jÑjÒhi]hh]hf]hg]hl]uhnM·hohhp]r‚9hyXmain-isrƒ9…r„9}r…9(hTUh`NhnNhohhUj~9ubaubjâ)r†9}r‡9(hTj[hUjs9h`hahbjåhd}rˆ9(jÑjÒhi]hh]hf]hg]hl]uhnM·hohhp]r‰9hyX: rŠ9…r‹9}rŒ9(hTUh`NhnNhohhUj†9ubaubja)r9}rŽ9(hTXfilenamehUjs9h`hahbjdhd}r9(jÑjÒhi]hh]hf]hg]hl]uhnM·hohhp]r9hyXfilenamer‘9…r’9}r“9(hTUh`NhnNhohhUj9ubaubeubjê)r”9}r•9(hTUhUjn9h`hahbjíhd}r–9(hf]hg]hh]hi]hl]uhnM·hohhp]r—9(jð)r˜9}r™9(hTUhUj”9h`hahbjóhd}rš9(hf]hg]hh]hi]hl]uhnNhohhp]r›9jö)rœ9}r9(hTUhUj˜9h`hahbjùhd}rž9(hf]hg]hh]hi]hl]uhnM¯hohhp]rŸ9(jü)r 9}r¡9(hTXrequiredhUjœ9h`hahbjhd}r¢9(hf]hg]hh]hi]hl]uhnKhp]r£9hyXRequiredr¤9…r¥9}r¦9(hTUhUj 9ubaubj)r§9}r¨9(hTX``exitcode-stdio-1.0`` hd}r©9(hf]hg]hh]hi]hl]uhUjœ9hp]rª9h})r«9}r¬9(hTX``exitcode-stdio-1.0``r­9hUj§9h`hahbhhd}r®9(hf]hg]hh]hi]hl]uhnM¯hp]r¯9hß)r°9}r±9(hTj­9hd}r²9(hf]hg]hh]hi]hl]uhUj«9hp]r³9hyXexitcode-stdio-1.0r´9…rµ9}r¶9(hTUhUj°9ubahbhçubaubahbjubeubaubh})r·9}r¸9(hTXdThe name of the ``.hs`` or ``.lhs`` file containing the ``Main`` module. Note that it is the ``.hs`` filename that must be listed, even if that file is generated using a preprocessor. The source file must be relative to one of the directories listed in :pkg-field:`hs-source-dirs`. This field is analogous to the ``main-is`` field of an executable section.hUj”9h`hahbhhd}r¹9(hf]hg]hh]hi]hl]uhnM±hohhp]rº9(hyXThe name of the r»9…r¼9}r½9(hTXThe name of the h`NhnNhohhUj·9ubhß)r¾9}r¿9(hTX``.hs``hd}rÀ9(hf]hg]hh]hi]hl]uhUj·9hp]rÁ9hyX.hsrÂ9…rÃ9}rÄ9(hTUhUj¾9ubahbhçubhyX or rÅ9…rÆ9}rÇ9(hTX or h`NhnNhohhUj·9ubhß)rÈ9}rÉ9(hTX``.lhs``hd}rÊ9(hf]hg]hh]hi]hl]uhUj·9hp]rË9hyX.lhsrÌ9…rÍ9}rÎ9(hTUhUjÈ9ubahbhçubhyX file containing the rÏ9…rÐ9}rÑ9(hTX file containing the h`NhnNhohhUj·9ubhß)rÒ9}rÓ9(hTX``Main``hd}rÔ9(hf]hg]hh]hi]hl]uhUj·9hp]rÕ9hyXMainrÖ9…r×9}rØ9(hTUhUjÒ9ubahbhçubhyX module. Note that it is the rÙ9…rÚ9}rÛ9(hTX module. Note that it is the h`NhnNhohhUj·9ubhß)rÜ9}rÝ9(hTX``.hs``hd}rÞ9(hf]hg]hh]hi]hl]uhUj·9hp]rß9hyX.hsrà9…rá9}râ9(hTUhUjÜ9ubahbhçubhyX™ filename that must be listed, even if that file is generated using a preprocessor. The source file must be relative to one of the directories listed in rã9…rä9}rå9(hTX™ filename that must be listed, even if that file is generated using a preprocessor. The source file must be relative to one of the directories listed in h`NhnNhohhUj·9ubjk)ræ9}rç9(hTX:pkg-field:`hs-source-dirs`rè9hUj·9h`hahbjohd}ré9(UreftypeX pkg-fieldjqˆjrXhs-source-dirsU refdomainXcabalrê9hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹X benchmarkrë9uhnM±hp]rì9hß)rí9}rî9(hTjè9hd}rï9(hf]hg]rð9(j|jê9Xcabal-pkg-fieldrñ9ehh]hi]hl]uhUjæ9hp]rò9hyXhs-source-dirsró9…rô9}rõ9(hTUhUjí9ubahbhçubaubhyX!. This field is analogous to the rö9…r÷9}rø9(hTX!. This field is analogous to the h`NhnNhohhUj·9ubhß)rù9}rú9(hTX ``main-is``hd}rû9(hf]hg]hh]hi]hl]uhUj·9hp]rü9hyXmain-isrý9…rþ9}rÿ9(hTUhUjù9ubahbhçubhyX field of an executable section.r:…r:}r:(hTX field of an executable section.h`NhnNhohhUj·9ubeubeubeubhWhV)r:}r:(hTUhUhZh`hahbhchd}r:(hf]hg]hh]hi]r:Urunning-benchmarksr:ahl]r:h&auhnMàhohhp]r :(hr)r :}r :(hTXRunning benchmarksr :hUj:h`hahbhvhd}r :(hf]hg]hh]hi]hl]uhnMàhohhp]r:hyXRunning benchmarksr:…r:}r:(hTj :h`NhnNhohhUj :ubaubh})r:}r:(hTXJYou can have Cabal run your benchmark using its built-in benchmark runner:r:hUj:h`hahbhhd}r:(hf]hg]hh]hi]hl]uhnMâhohhp]r:hyXJYou can have Cabal run your benchmark using its built-in benchmark runner:r:…r:}r:(hTj:h`NhnNhohhUj:ubaubjÌ)r:}r:(hTXA$ cabal configure --enable-benchmarks $ cabal build $ cabal benchhUj:h`hahbjÏhd}r:(jÑjÒhi]hh]hf]hg]hl]uhnMçhohhp]r:hyXA$ cabal configure --enable-benchmarks $ cabal build $ cabal benchr:…r:}r :(hTUhUj:ubaubh})r!:}r":(hTX]See the output of ``cabal help bench`` for a list of options you can pass to ``cabal bench``.hUj:h`hahbhhd}r#:(hf]hg]hh]hi]hl]uhnMëhohhp]r$:(hyXSee the output of r%:…r&:}r':(hTXSee the output of h`NhnNhohhUj!:ubhß)r(:}r):(hTX``cabal help bench``hd}r*:(hf]hg]hh]hi]hl]uhUj!:hp]r+:hyXcabal help benchr,:…r-:}r.:(hTUhUj(:ubahbhçubhyX' for a list of options you can pass to r/:…r0:}r1:(hTX' for a list of options you can pass to h`NhnNhohhUj!:ubhß)r2:}r3:(hTX``cabal bench``hd}r4:(hf]hg]hh]hi]hl]uhUj!:hp]r5:hyX cabal benchr6:…r7:}r8:(hTUhUj2:ubahbhçubhyX.…r9:}r::(hTX.h`NhnNhohhUj!:ubeubeubeubh`hahbhchd}r;:(hf]r<:j“ ahg]hh]hi]r=:Uid1r>:ahl]uhnM¹hohhp]r?:(hr)r@:}rA:(hTX7Example: Package using ``exitcode-stdio-1.0`` interfacerB:hUhWh`hahbhvhd}rC:(hf]hg]hh]hi]hl]uhnM¹hohhp]rD:(hyXExample: Package using rE:…rF:}rG:(hTXExample: Package using rH:h`NhnNhohhUj@:ubhß)rI:}rJ:(hTX``exitcode-stdio-1.0``rK:hd}rL:(hf]hg]hh]hi]hl]uhUj@:hp]rM:hyXexitcode-stdio-1.0rN:…rO:}rP:(hTUhUjI:ubahbhçubhyX interfacerQ:…rR:}rS:(hTX interfacerT:h`NhnNhohhUj@:ubeubh})rU:}rV:(hTX}The example package description and executable source file below demonstrate the use of the ``exitcode-stdio-1.0`` interface.hUhWh`hahbhhd}rW:(hf]hg]hh]hi]hl]uhnM»hohhp]rX:(hyX\The example package description and executable source file below demonstrate the use of the rY:…rZ:}r[:(hTX\The example package description and executable source file below demonstrate the use of the h`NhnNhohhUjU:ubhß)r\:}r]:(hTX``exitcode-stdio-1.0``hd}r^:(hf]hg]hh]hi]hl]uhUjU:hp]r_:hyXexitcode-stdio-1.0r`:…ra:}rb:(hTUhUj\:ubahbhçubhyX interface.rc:…rd:}re:(hTX interface.h`NhnNhohhUjU:ubeubj½ )rf:}rg:(hTUhYKhUhWh`UhbjÀ hd}rh:(hi]ri:Ufoo-bench-cabalrj:ahh]hf]rk:h2ahg]rl:jÅ ahl]U literal_blockˆuhnNhohhp]rm:(jÇ )rn:}ro:(hTX foo.cabalrp:hUjf:h`hahbjË hd}rq:(hf]hg]hh]hi]hl]uhnM¾hp]rr:hyX foo.cabalrs:…rt:}ru:(hTjp:hUjn:ubaubjÌ)rv:}rw:(hTXßName: foo Version: 1.0 License: BSD3 Cabal-Version: >= 1.9.2 Build-Type: Simple Benchmark bench-foo type: exitcode-stdio-1.0 main-is: bench-foo.hs build-depends: base, timehUjf:h`hahbjÏhd}rx:(j‰jXcabaljÑjÒhi]hh]hf]j}hg]hl]uhnM¾hp]ry:hyXßName: foo Version: 1.0 License: BSD3 Cabal-Version: >= 1.9.2 Build-Type: Simple Benchmark bench-foo type: exitcode-stdio-1.0 main-is: bench-foo.hs build-depends: base, timerz:…r{:}r|:(hTUhUjv:ubaubeubj½ )r}:}r~:(hTUhUhWh`UhbjÀ hd}r:(hi]r€:Uid7r:ahh]hf]hg]r‚:jÅ ahl]U literal_blockˆuhnNhohhp]rƒ:(jÇ )r„:}r…:(hTX bench-foo.hsr†:hUj}:h`hahbjË hd}r‡:(hf]hg]hh]hi]hl]uhnMÍhp]rˆ:hyX bench-foo.hsr‰:…rŠ:}r‹:(hTj†:hUj„:ubaubjÌ)rŒ:}r:(hTX {-# LANGUAGE BangPatterns #-} module Main where import Data.Time.Clock fib 0 = 1 fib 1 = 1 fib n = fib (n-1) + fib (n-2) main = do start <- getCurrentTime let !r = fib 20 end <- getCurrentTime putStrLn $ "fib 20 took " ++ show (diffUTCTime end start)hUj}:h`hahbjÏhd}rŽ:(j‰jXhaskelljÑjÒhi]hh]hf]j}hg]hl]uhnMÍhp]r:hyX {-# LANGUAGE BangPatterns #-} module Main where import Data.Time.Clock fib 0 = 1 fib 1 = 1 fib n = fib (n-1) + fib (n-2) main = do start <- getCurrentTime let !r = fib 20 end <- getCurrentTime putStrLn $ "fib 20 took " ++ show (diffUTCTime end start)r:…r‘:}r’:(hTUhUjŒ:ubaubeubeubh`hahbUsystem_messager“:hd}r”:(hf]UlevelKhi]hh]r•:j>:aUsourcehahg]hl]UlineM¹UtypeUINFOr–:uhnM¹hohhp]r—:h})r˜:}r™:(hTXVDuplicate implicit target name: "example: package using exitcode-stdio-1.0 interface".hd}rš:(hf]hg]hh]hi]hl]uhUhRhp]r›:hyXZDuplicate implicit target name: “example: package using exitcode-stdio-1.0 interfaceâ€.rœ:…r:}rž:(hTUhUj˜:ubahbhubaubhQ)rŸ:}r :(hTUhd}r¡:(hf]UlevelKhi]hh]Usourcehahg]hl]UlineMÄUtypeUSEVEREr¢:uhp]r£:h})r¤:}r¥:(hTUhd}r¦:(hf]hg]hh]hi]hl]uhUjŸ:hp]r§:hyX)Duplicate ID: "pkg-field-benchmark-type".r¨:…r©:}rª:(hTUhUj¤:ubahbhubahbj“:ubhQ)r«:}r¬:(hTUhUjñ/h`hahbj“:hd}r­:(hf]UlevelKhi]hh]r®:jö/aUsourcehahg]hl]UlineMâUtypej–:uhnMâhohhp]r¯:h})r°:}r±:(hTXbDuplicate implicit target name: "example: a package containing a library and executable programs".hd}r²:(hf]hg]hh]hi]hl]uhUj«:hp]r³:hyXfDuplicate implicit target name: “example: a package containing a library and executable programsâ€.r´:…rµ:}r¶:(hTUhUj°:ubahbhubaubeUcurrent_sourcer·:NU decorationr¸:NUautofootnote_startr¹:KUnameidsrº:}r»:(hjáhjØ hjŽh U quickstartr¼:h jÛh Uthe-point-of-packagesr½:h U6explicit-dependencies-and-automatic-package-managementr¾:h j²7hjFhj hjKhjÐ hUmodules-included-in-the-packager¿:hj hj5hj# hjÏhjá hUediting-the-cabal-filerÀ:hjöhjhj hj¦hjD4hj—hjí h Ubuilding-the-packagerÁ:h!j h"hkh#jh$jô h%jÔ3h&j:h'jI0h(jê1h)j h*jû h+j!h,j·4h-jò h.jX h/hýh0j #h1Upackage-names-and-versionsrÂ:h2jj:h3jÊh4j30h5jI h6U next-stepsrÃ:h7Uunit-of-distributionrÄ:h8U$modules-imported-from-other-packagesrÅ:h9júh:j 0h;NhU portabilityrÇ:h?jU!h@j(hAU'kinds-of-package-cabal-vs-ghc-vs-systemrÈ:hBUpackage-conceptsrÉ:hCjŠ0hDj®hEjç hFjDhGj²8hHNhIj°hJjÈhKjÑ(hLjœuhp]rÊ:(hV)rË:}rÌ:(hTUhUhh`hahbhchd}rÍ:(hf]hg]hh]hi]rÎ:j¼:ahl]rÏ:h auhnKhohhp]rÐ:(hr)rÑ:}rÒ:(hTX QuickstartrÓ:hUjË:h`hahbhvhd}rÔ:(hf]hg]hh]hi]hl]uhnKhohhp]rÕ:hyX QuickstartrÖ:…r×:}rØ:(hTjÓ:h`NhnNhohhUjÑ:ubaubh})rÙ:}rÚ:(hTXYLets assume we have created a project directory and already have a Haskell module or two.rÛ:hUjË:h`hahbhhd}rÜ:(hf]hg]hh]hi]hl]uhnKhohhp]rÝ:hyXYLets assume we have created a project directory and already have a Haskell module or two.rÞ:…rß:}rà:(hTjÛ:h`NhnNhohhUjÙ:ubaubh})rá:}râ:(hTX>Every project needs a name, we'll call this example "proglet".rã:hUjË:h`hahbhhd}rä:(hf]hg]hh]hi]hl]uhnKhohhp]rå:hyXDEvery project needs a name, we’ll call this example “progletâ€.ræ:…rç:}rè:(hTjã:h`NhnNhohhUjá:ubaubcsphinx.addnodes highlightlang ré:)rê:}rë:(hTUhUjË:h`hahbU highlightlangrì:hd}rí:(UlangXconsoleUlinenothresholdI9223372036854775807 hi]hh]hf]hg]hl]uhnK hohhp]ubjÌ)rî:}rï:(hTX$ cd proglet/ $ ls Proglet.hshUjË:h`hahbjÏhd}rð:(jÑjÒhi]hh]hf]hg]hl]uhnK hohhp]rñ:hyX$ cd proglet/ $ ls Proglet.hsrò:…ró:}rô:(hTUhUjî:ubaubh})rõ:}rö:(hTXýIt is assumed that (apart from external dependencies) all the files that make up a package live under a common project root directory. This simple example has all the project files in one directory, but most packages will use one or more subdirectories.r÷:hUjË:h`hahbhhd}rø:(hf]hg]hh]hi]hl]uhnKhohhp]rù:hyXýIt is assumed that (apart from external dependencies) all the files that make up a package live under a common project root directory. This simple example has all the project files in one directory, but most packages will use one or more subdirectories.rú:…rû:}rü:(hTj÷:h`NhnNhohhUjõ:ubaubh})rý:}rþ:(hTXZTo turn this into a Cabal package we need two extra files in the project's root directory:rÿ:hUjË:h`hahbhhd}r;(hf]hg]hh]hi]hl]uhnKhohhp]r;hyX\To turn this into a Cabal package we need two extra files in the project’s root directory:r;…r;}r;(hTjÿ:h`NhnNhohhUjý:ubaubh‡)r;}r;(hTUhUjË:h`hahbhŠhd}r;(hŒX-hi]hh]hf]hg]hl]uhnKhohhp]r;(hŽ)r ;}r ;(hTXF``proglet.cabal``: containing package metadata and build information. hUj;h`hahbh‘hd}r ;(hf]hg]hh]hi]hl]uhnNhohhp]r ;h})r ;}r;(hTXE``proglet.cabal``: containing package metadata and build information.hUj ;h`hahbhhd}r;(hf]hg]hh]hi]hl]uhnKhp]r;(hß)r;}r;(hTX``proglet.cabal``hd}r;(hf]hg]hh]hi]hl]uhUj ;hp]r;hyX proglet.cabalr;…r;}r;(hTUhUj;ubahbhçubhyX4: containing package metadata and build information.r;…r;}r;(hTX4: containing package metadata and build information.hUj ;ubeubaubhŽ)r;}r;(hTXg``Setup.hs``: usually containing a few standardized lines of code, but can be customized if necessary. hUj;h`hahbh‘hd}r;(hf]hg]hh]hi]hl]uhnNhohhp]r;h})r;}r ;(hTXf``Setup.hs``: usually containing a few standardized lines of code, but can be customized if necessary.hUj;h`hahbhhd}r!;(hf]hg]hh]hi]hl]uhnKhp]r";(hß)r#;}r$;(hTX ``Setup.hs``hd}r%;(hf]hg]hh]hi]hl]uhUj;hp]r&;hyXSetup.hsr';…r(;}r);(hTUhUj#;ubahbhçubhyXZ: usually containing a few standardized lines of code, but can be customized if necessary.r*;…r+;}r,;(hTXZ: usually containing a few standardized lines of code, but can be customized if necessary.hUj;ubeubaubeubh})r-;}r.;(hTXUWe can create both files manually or we can use ``cabal init`` to create them for us.hUjË:h`hahbhhd}r/;(hf]hg]hh]hi]hl]uhnKhohhp]r0;(hyX0We can create both files manually or we can use r1;…r2;}r3;(hTX0We can create both files manually or we can use h`NhnNhohhUj-;ubhß)r4;}r5;(hTX``cabal init``hd}r6;(hf]hg]hh]hi]hl]uhUj-;hp]r7;hyX cabal initr8;…r9;}r:;(hTUhUj4;ubahbhçubhyX to create them for us.r;;…r<;}r=;(hTX to create them for us.h`NhnNhohhUj-;ubeubhV)r>;}r?;(hTUhUjË:h`hahbhchd}r@;(hf]hg]hh]hi]rA;jÆ:ahl]rB;h=auhnK"hohhp]rC;(hr)rD;}rE;(hTXUsing "cabal init"rF;hUj>;h`hahbhvhd}rG;(hf]hg]hh]hi]hl]uhnK"hohhp]rH;hyXUsing “cabal initâ€rI;…rJ;}rK;(hTjF;h`NhnNhohhUjD;ubaubh})rL;}rM;(hTXwThe ``cabal init`` command is interactive. It asks us a number of questions starting with the package name and version.hUj>;h`hahbhhd}rN;(hf]hg]hh]hi]hl]uhnK$hohhp]rO;(hyXThe rP;…rQ;}rR;(hTXThe h`NhnNhohhUjL;ubhß)rS;}rT;(hTX``cabal init``hd}rU;(hf]hg]hh]hi]hl]uhUjL;hp]rV;hyX cabal initrW;…rX;}rY;(hTUhUjS;ubahbhçubhyXe command is interactive. It asks us a number of questions starting with the package name and version.rZ;…r[;}r\;(hTXe command is interactive. It asks us a number of questions starting with the package name and version.h`NhnNhohhUjL;ubeubjÌ)r];}r^;(hTXS$ cabal init Package name [default "proglet"]? Package version [default "0.1"]? ...hUj>;h`hahbjÏhd}r_;(jÑjÒhi]hh]hf]hg]hl]uhnK)hohhp]r`;hyXS$ cabal init Package name [default "proglet"]? Package version [default "0.1"]? ...ra;…rb;}rc;(hTUhUj];ubaubh})rd;}re;(hTX¡It also asks questions about various other bits of package metadata. For a package that you never intend to distribute to others, these fields can be left blank.rf;hUj>;h`hahbhhd}rg;(hf]hg]hh]hi]hl]uhnK.hohhp]rh;hyX¡It also asks questions about various other bits of package metadata. For a package that you never intend to distribute to others, these fields can be left blank.ri;…rj;}rk;(hTjf;h`NhnNhohhUjd;ubaubh})rl;}rm;(hTXïOne of the important questions is whether the package contains a library or an executable. Libraries are collections of Haskell modules that can be re-used by other Haskell libraries and programs, while executables are standalone programs.rn;hUj>;h`hahbhhd}ro;(hf]hg]hh]hi]hl]uhnK2hohhp]rp;hyXïOne of the important questions is whether the package contains a library or an executable. Libraries are collections of Haskell modules that can be re-used by other Haskell libraries and programs, while executables are standalone programs.rq;…rr;}rs;(hTjn;h`NhnNhohhUjl;ubaubjÌ)rt;}ru;(hTXHWhat does the package build: 1) Library 2) Executable Your choice?hUj>;h`hahbjÏhd}rv;(jÑjÒhi]hh]hf]hg]hl]uhnK9hohhp]rw;hyXHWhat does the package build: 1) Library 2) Executable Your choice?rx;…ry;}rz;(hTUhUjt;ubaubh})r{;}r|;(hTX«For the moment these are the only choices. For more complex packages (e.g. a library and multiple executables or test suites) the ``.cabal`` file can be edited afterwards.hUj>;h`hahbhhd}r};(hf]hg]hh]hi]hl]uhnK>hohhp]r~;(hyX‚For the moment these are the only choices. For more complex packages (e.g. a library and multiple executables or test suites) the r;…r€;}r;(hTX‚For the moment these are the only choices. For more complex packages (e.g. a library and multiple executables or test suites) the h`NhnNhohhUj{;ubhß)r‚;}rƒ;(hTX ``.cabal``hd}r„;(hf]hg]hh]hi]hl]uhUj{;hp]r…;hyX.cabalr†;…r‡;}rˆ;(hTUhUj‚;ubahbhçubhyX file can be edited afterwards.r‰;…rŠ;}r‹;(hTX file can be edited afterwards.h`NhnNhohhUj{;ubeubh})rŒ;}r;(hTXšFinally, ``cabal init`` creates the initial ``proglet.cabal`` and ``Setup.hs`` files, and depending on your choice of license, a ``LICENSE`` file as well.hUj>;h`hahbhhd}rŽ;(hf]hg]hh]hi]hl]uhnKBhohhp]r;(hyX Finally, r;…r‘;}r’;(hTX Finally, h`NhnNhohhUjŒ;ubhß)r“;}r”;(hTX``cabal init``hd}r•;(hf]hg]hh]hi]hl]uhUjŒ;hp]r–;hyX cabal initr—;…r˜;}r™;(hTUhUj“;ubahbhçubhyX creates the initial rš;…r›;}rœ;(hTX creates the initial h`NhnNhohhUjŒ;ubhß)r;}rž;(hTX``proglet.cabal``hd}rŸ;(hf]hg]hh]hi]hl]uhUjŒ;hp]r ;hyX proglet.cabalr¡;…r¢;}r£;(hTUhUj;ubahbhçubhyX and r¤;…r¥;}r¦;(hTX and h`NhnNhohhUjŒ;ubhß)r§;}r¨;(hTX ``Setup.hs``hd}r©;(hf]hg]hh]hi]hl]uhUjŒ;hp]rª;hyXSetup.hsr«;…r¬;}r­;(hTUhUj§;ubahbhçubhyX3 files, and depending on your choice of license, a r®;…r¯;}r°;(hTX3 files, and depending on your choice of license, a h`NhnNhohhUjŒ;ubhß)r±;}r²;(hTX ``LICENSE``hd}r³;(hf]hg]hh]hi]hl]uhUjŒ;hp]r´;hyXLICENSErµ;…r¶;}r·;(hTUhUj±;ubahbhçubhyX file as well.r¸;…r¹;}rº;(hTX file as well.h`NhnNhohhUjŒ;ubeubjÌ)r»;}r¼;(hTX‹Generating LICENSE... Generating Setup.hs... Generating proglet.cabal... You may want to edit the .cabal file and add a Description field.hUj>;h`hahbjÏhd}r½;(jÑjÒhi]hh]hf]hg]hl]uhnKHhohhp]r¾;hyX‹Generating LICENSE... Generating Setup.hs... Generating proglet.cabal... You may want to edit the .cabal file and add a Description field.r¿;…rÀ;}rÁ;(hTUhUj»;ubaubh})rÂ;}rÃ;(hTXÅAs this stage the ``proglet.cabal`` is not quite complete and before you are able to build the package you will need to edit the file and add some build information about the library or executable.hUj>;h`hahbhhd}rÄ;(hf]hg]hh]hi]hl]uhnKNhohhp]rÅ;(hyXAs this stage the rÆ;…rÇ;}rÈ;(hTXAs this stage the h`NhnNhohhUjÂ;ubhß)rÉ;}rÊ;(hTX``proglet.cabal``hd}rË;(hf]hg]hh]hi]hl]uhUjÂ;hp]rÌ;hyX proglet.cabalrÍ;…rÎ;}rÏ;(hTUhUjÉ;ubahbhçubhyX¢ is not quite complete and before you are able to build the package you will need to edit the file and add some build information about the library or executable.rÐ;…rÑ;}rÒ;(hTX¢ is not quite complete and before you are able to build the package you will need to edit the file and add some build information about the library or executable.h`NhnNhohhUjÂ;ubeubeubhV)rÓ;}rÔ;(hTUhUjË:h`hahbhchd}rÕ;(hf]hg]hh]hi]rÖ;jÀ:ahl]r×;hauhnKShohhp]rØ;(hr)rÙ;}rÚ;(hTXEditing the .cabal filerÛ;hUjÓ;h`hahbhvhd}rÜ;(hf]hg]hh]hi]hl]uhnKShohhp]rÝ;hyXEditing the .cabal filerÞ;…rß;}rà;(hTjÛ;h`NhnNhohhUjÙ;ubaubjé:)rá;}râ;(hTUhUjÓ;h`hahbjì:hd}rã;(UlangXcabalUlinenothresholdI9223372036854775807 hi]hh]hf]hg]hl]uhnKVhohhp]ubh})rä;}rå;(hTXÛLoad up the ``.cabal`` file in a text editor. The first part of the ``.cabal`` file has the package metadata and towards the end of the file you will find the :pkg-section:`executable` or :pkg-section:`library` section.hUjÓ;h`hahbhhd}ræ;(hf]hg]hh]hi]hl]uhnKWhohhp]rç;(hyX Load up the rè;…ré;}rê;(hTX Load up the h`NhnNhohhUjä;ubhß)rë;}rì;(hTX ``.cabal``hd}rí;(hf]hg]hh]hi]hl]uhUjä;hp]rî;hyX.cabalrï;…rð;}rñ;(hTUhUjë;ubahbhçubhyX. file in a text editor. The first part of the rò;…ró;}rô;(hTX. file in a text editor. The first part of the h`NhnNhohhUjä;ubhß)rõ;}rö;(hTX ``.cabal``hd}r÷;(hf]hg]hh]hi]hl]uhUjä;hp]rø;hyX.cabalrù;…rú;}rû;(hTUhUjõ;ubahbhçubhyXQ file has the package metadata and towards the end of the file you will find the rü;…rý;}rþ;(hTXQ file has the package metadata and towards the end of the file you will find the h`NhnNhohhUjä;ubjk)rÿ;}r<(hTX:pkg-section:`executable`r<hUjä;h`hahbjohd}r<(UreftypeX pkg-sectionjqˆjrX executableU refdomainXcabalr<hi]hh]U refexplicit‰hf]hg]hl]jtjuuhnKWhp]r<hß)r<}r<(hTj<hd}r<(hf]hg]r<(j|j<Xcabal-pkg-sectionr <ehh]hi]hl]uhUjÿ;hp]r <hyX executabler <…r <}r <(hTUhUj<ubahbhçubaubhyX or r<…r<}r<(hTX or h`NhnNhohhUjä;ubjk)r<}r<(hTX:pkg-section:`library`r<hUjä;h`hahbjohd}r<(UreftypeX pkg-sectionjqˆjrXlibraryU refdomainXcabalr<hi]hh]U refexplicit‰hf]hg]hl]jtjuuhnKWhp]r<hß)r<}r<(hTj<hd}r<(hf]hg]r<(j|j<Xcabal-pkg-sectionr<ehh]hi]hl]uhUj<hp]r<hyXlibraryr<…r<}r<(hTUhUj<ubahbhçubaubhyX section.r <…r!<}r"<(hTX section.h`NhnNhohhUjä;ubeubh})r#<}r$<(hTX'You will see that the fields that have yet to be filled in are commented out. Cabal files use "``--``" Haskell-style comment syntax. (Note that comments are only allowed on lines on their own. Trailing comments on other lines are not allowed because they could be confused with program options.)hUjÓ;h`hahbhhd}r%<(hf]hg]hh]hi]hl]uhnK[hohhp]r&<(hyXaYou will see that the fields that have yet to be filled in are commented out. Cabal files use “r'<…r(<}r)<(hTX_You will see that the fields that have yet to be filled in are commented out. Cabal files use "h`NhnNhohhUj#<ubhß)r*<}r+<(hTX``--``hd}r,<(hf]hg]hh]hi]hl]uhUj#<hp]r-<hyX--r.<…r/<}r0<(hTUhUj*<ubahbhçubhyXĆHaskell-style comment syntax. (Note that comments are only allowed on lines on their own. Trailing comments on other lines are not allowed because they could be confused with program options.)r1<…r2<}r3<(hTXÂ" Haskell-style comment syntax. (Note that comments are only allowed on lines on their own. Trailing comments on other lines are not allowed because they could be confused with program options.)h`NhnNhohhUj#<ubeubh})r4<}r5<(hTXwIf you selected earlier to create a library package then your ``.cabal`` file will have a section that looks like this:hUjÓ;h`hahbhhd}r6<(hf]hg]hh]hi]hl]uhnKahohhp]r7<(hyX>If you selected earlier to create a library package then your r8<…r9<}r:<(hTX>If you selected earlier to create a library package then your h`NhnNhohhUj4<ubhß)r;<}r<<(hTX ``.cabal``hd}r=<(hf]hg]hh]hi]hl]uhUj4<hp]r><hyX.cabalr?<…r@<}rA<(hTUhUj;<ubahbhçubhyX/ file will have a section that looks like this:rB<…rC<}rD<(hTX/ file will have a section that looks like this:h`NhnNhohhUj4<ubeubjÌ)rE<}rF<(hTXNlibrary exposed-modules: Proglet -- other-modules: -- build-depends:hUjÓ;h`hahbjÏhd}rG<(jÑjÒhi]hh]hf]hg]hl]uhnKfhohhp]rH<hyXNlibrary exposed-modules: Proglet -- other-modules: -- build-depends:rI<…rJ<}rK<(hTUhUjE<ubaubh})rL<}rM<(hTXOAlternatively, if you selected an executable then there will be a section like:rN<hUjÓ;h`hahbhhd}rO<(hf]hg]hh]hi]hl]uhnKkhohhp]rP<hyXOAlternatively, if you selected an executable then there will be a section like:rQ<…rR<}rS<(hTjN<h`NhnNhohhUjL<ubaubjÌ)rT<}rU<(hTXHexecutable proglet -- main-is: -- other-modules: -- build-depends:hUjÓ;h`hahbjÏhd}rV<(jÑjÒhi]hh]hf]hg]hl]uhnKphohhp]rW<hyXHexecutable proglet -- main-is: -- other-modules: -- build-depends:rX<…rY<}rZ<(hTUhUjT<ubaubh})r[<}r\<(hTX¨The build information fields listed (but commented out) are just the few most important and common fields. There are many others that are covered later in this chapter.r]<hUjÓ;h`hahbhhd}r^<(hf]hg]hh]hi]hl]uhnKuhohhp]r_<hyX¨The build information fields listed (but commented out) are just the few most important and common fields. There are many others that are covered later in this chapter.r`<…ra<}rb<(hTj]<h`NhnNhohhUj[<ubaubh})rc<}rd<(hTXMost of the build information fields are the same between libraries and executables. The difference is that libraries have a number of "exposed" modules that make up the public interface of the library, while executables have a file containing a ``Main`` module.hUjÓ;h`hahbhhd}re<(hf]hg]hh]hi]hl]uhnKyhohhp]rf<(hyXúMost of the build information fields are the same between libraries and executables. The difference is that libraries have a number of “exposed†modules that make up the public interface of the library, while executables have a file containing a rg<…rh<}ri<(hTXöMost of the build information fields are the same between libraries and executables. The difference is that libraries have a number of "exposed" modules that make up the public interface of the library, while executables have a file containing a h`NhnNhohhUjc<ubhß)rj<}rk<(hTX``Main``hd}rl<(hf]hg]hh]hi]hl]uhUjc<hp]rm<hyXMainrn<…ro<}rp<(hTUhUjj<ubahbhçubhyX module.rq<…rr<}rs<(hTX module.h`NhnNhohhUjc<ubeubh})rt<}ru<(hTXÝThe name of a library always matches the name of the package, so it is not specified in the library section. Executables often follow the name of the package too, but this is not required and the name is given explicitly.rv<hUjÓ;h`hahbhhd}rw<(hf]hg]hh]hi]hl]uhnK~hohhp]rx<hyXÝThe name of a library always matches the name of the package, so it is not specified in the library section. Executables often follow the name of the package too, but this is not required and the name is given explicitly.ry<…rz<}r{<(hTjv<h`NhnNhohhUjt<ubaubeubhV)r|<}r}<(hTUhUjË:h`hahbhchd}r~<(hf]hg]hh]hi]r<j¿:ahl]r€<hauhnK„hohhp]r<(hr)r‚<}rƒ<(hTXModules included in the packager„<hUj|<h`hahbhvhd}r…<(hf]hg]hh]hi]hl]uhnK„hohhp]r†<hyXModules included in the packager‡<…rˆ<}r‰<(hTj„<h`NhnNhohhUj‚<ubaubh})rŠ<}r‹<(hTXuFor a library, ``cabal init`` looks in the project directory for files that look like Haskell modules and adds all the modules to the :pkg-field:`library:exposed-modules` field. For modules that do not form part of your package's public interface, you can move those modules to the :pkg-field:`other-modules` field. Either way, all modules in the library need to be listed.hUj|<h`hahbhhd}rŒ<(hf]hg]hh]hi]hl]uhnK†hohhp]r<(hyXFor a library, rŽ<…r<}r<(hTXFor a library, h`NhnNhohhUjŠ<ubhß)r‘<}r’<(hTX``cabal init``hd}r“<(hf]hg]hh]hi]hl]uhUjŠ<hp]r”<hyX cabal initr•<…r–<}r—<(hTUhUj‘<ubahbhçubhyXi looks in the project directory for files that look like Haskell modules and adds all the modules to the r˜<…r™<}rš<(hTXi looks in the project directory for files that look like Haskell modules and adds all the modules to the h`NhnNhohhUjŠ<ubjk)r›<}rœ<(hTX$:pkg-field:`library:exposed-modules`r<hUjŠ<h`hahbjohd}rž<(UreftypeX pkg-fieldjqˆjrXexposed-modulesU refdomainXcabalrŸ<hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹XlibraryuhnK†hp]r <hß)r¡<}r¢<(hTj<hd}r£<(hf]hg]r¤<(j|jŸ<Xcabal-pkg-fieldr¥<ehh]hi]hl]uhUj›<hp]r¦<hyXlibrary:exposed-modulesr§<…r¨<}r©<(hTUhUj¡<ubahbhçubaubhyXr field. For modules that do not form part of your package’s public interface, you can move those modules to the rª<…r«<}r¬<(hTXp field. For modules that do not form part of your package's public interface, you can move those modules to the h`NhnNhohhUjŠ<ubjk)r­<}r®<(hTX:pkg-field:`other-modules`r¯<hUjŠ<h`hahbjohd}r°<(UreftypeX pkg-fieldjqˆjrX other-modulesU refdomainXcabalr±<hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnK†hp]r²<hß)r³<}r´<(hTj¯<hd}rµ<(hf]hg]r¶<(j|j±<Xcabal-pkg-fieldr·<ehh]hi]hl]uhUj­<hp]r¸<hyX other-modulesr¹<…rº<}r»<(hTUhUj³<ubahbhçubaubhyXA field. Either way, all modules in the library need to be listed.r¼<…r½<}r¾<(hTXA field. Either way, all modules in the library need to be listed.h`NhnNhohhUjŠ<ubeubh})r¿<}rÀ<(hTXqFor an executable, ``cabal init`` does not try to guess which file contains your program's ``Main`` module. You will need to fill in the :pkg-field:`executable:main-is` field with the file name of your program's ``Main`` module (including ``.hs`` or ``.lhs`` extension). Other modules included in the executable should be listed in the :pkg-field:`other-modules` field.hUj|<h`hahbhhd}rÁ<(hf]hg]hh]hi]hl]uhnKhohhp]rÂ<(hyXFor an executable, rÃ<…rÄ<}rÅ<(hTXFor an executable, h`NhnNhohhUj¿<ubhß)rÆ<}rÇ<(hTX``cabal init``hd}rÈ<(hf]hg]hh]hi]hl]uhUj¿<hp]rÉ<hyX cabal initrÊ<…rË<}rÌ<(hTUhUjÆ<ubahbhçubhyX< does not try to guess which file contains your program’s rÍ<…rÎ<}rÏ<(hTX: does not try to guess which file contains your program's h`NhnNhohhUj¿<ubhß)rÐ<}rÑ<(hTX``Main``hd}rÒ<(hf]hg]hh]hi]hl]uhUj¿<hp]rÓ<hyXMainrÔ<…rÕ<}rÖ<(hTUhUjÐ<ubahbhçubhyX& module. You will need to fill in the r×<…rØ<}rÙ<(hTX& module. You will need to fill in the h`NhnNhohhUj¿<ubjk)rÚ<}rÛ<(hTX:pkg-field:`executable:main-is`rÜ<hUj¿<h`hahbjohd}rÝ<(UreftypeX pkg-fieldjqˆjrXmain-isU refdomainXcabalrÞ<hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹X executableuhnKhp]rß<hß)rà<}rá<(hTjÜ<hd}râ<(hf]hg]rã<(j|jÞ<Xcabal-pkg-fieldrä<ehh]hi]hl]uhUjÚ<hp]rå<hyXexecutable:main-isræ<…rç<}rè<(hTUhUjà<ubahbhçubaubhyX. field with the file name of your program’s ré<…rê<}rë<(hTX, field with the file name of your program's h`NhnNhohhUj¿<ubhß)rì<}rí<(hTX``Main``hd}rî<(hf]hg]hh]hi]hl]uhUj¿<hp]rï<hyXMainrð<…rñ<}rò<(hTUhUjì<ubahbhçubhyX module (including ró<…rô<}rõ<(hTX module (including h`NhnNhohhUj¿<ubhß)rö<}r÷<(hTX``.hs``hd}rø<(hf]hg]hh]hi]hl]uhUj¿<hp]rù<hyX.hsrú<…rû<}rü<(hTUhUjö<ubahbhçubhyX or rý<…rþ<}rÿ<(hTX or h`NhnNhohhUj¿<ubhß)r=}r=(hTX``.lhs``hd}r=(hf]hg]hh]hi]hl]uhUj¿<hp]r=hyX.lhsr=…r=}r=(hTUhUj=ubahbhçubhyXN extension). Other modules included in the executable should be listed in the r=…r=}r =(hTXN extension). Other modules included in the executable should be listed in the h`NhnNhohhUj¿<ubjk)r =}r =(hTX:pkg-field:`other-modules`r =hUj¿<h`hahbjohd}r =(UreftypeX pkg-fieldjqˆjrX other-modulesU refdomainXcabalr=hi]hh]U refexplicit‰hf]hg]hl]jtjuj‹NuhnKhp]r=hß)r=}r=(hTj =hd}r=(hf]hg]r=(j|j=Xcabal-pkg-fieldr=ehh]hi]hl]uhUj =hp]r=hyX other-modulesr=…r=}r=(hTUhUj=ubahbhçubaubhyX field.r=…r=}r=(hTX field.h`NhnNhohhUj¿<ubeubeubhV)r=}r=(hTUhUjË:h`hahbhchd}r=(hf]hg]hh]hi]r=jÅ:ahl]r =h8auhnK•hohhp]r!=(hr)r"=}r#=(hTX$Modules imported from other packagesr$=hUj=h`hahbhvhd}r%=(hf]hg]hh]hi]hl]uhnK•hohhp]r&=hyX$Modules imported from other packagesr'=…r(=}r)=(hTj$=h`NhnNhohhUj"=ubaubh})r*=}r+=(hTXWhile your library or executable may include a number of modules, it almost certainly also imports a number of external modules from the standard libraries or other pre-packaged libraries. (These other libraries are of course just Cabal packages that contain a library.)r,=hUj=h`hahbhhd}r-=(hf]hg]hh]hi]hl]uhnK—hohhp]r.=hyXWhile your library or executable may include a number of modules, it almost certainly also imports a number of external modules from the standard libraries or other pre-packaged libraries. (These other libraries are of course just Cabal packages that contain a library.)r/=…r0=}r1=(hTj,=h`NhnNhohhUj*=ubaubh})r2=}r3=(hTXÂYou have to list all of the library packages that your library or executable imports modules from. Or to put it another way: you have to list all the other packages that your package depends on.r4=hUj=h`hahbhhd}r5=(hf]hg]hh]hi]hl]uhnKœhohhp]r6=hyXÂYou have to list all of the library packages that your library or executable imports modules from. Or to put it another way: you have to list all the other packages that your package depends on.r7=…r8=}r9=(hTj4=h`NhnNhohhUj2=ubaubh})r:=}r;=(hTX§For example, suppose the example ``Proglet`` module imports the module ``Data.Map``. The ``Data.Map`` module comes from the ``containers`` package, so we must list it:hUj=h`hahbhhd}r<=(hf]hg]hh]hi]hl]uhnK hohhp]r==(hyX!For example, suppose the example r>=…r?=}r@=(hTX!For example, suppose the example h`NhnNhohhUj:=ubhß)rA=}rB=(hTX ``Proglet``hd}rC=(hf]hg]hh]hi]hl]uhUj:=hp]rD=hyXProgletrE=…rF=}rG=(hTUhUjA=ubahbhçubhyX module imports the module rH=…rI=}rJ=(hTX module imports the module h`NhnNhohhUj:=ubhß)rK=}rL=(hTX ``Data.Map``hd}rM=(hf]hg]hh]hi]hl]uhUj:=hp]rN=hyXData.MaprO=…rP=}rQ=(hTUhUjK=ubahbhçubhyX. The rR=…rS=}rT=(hTX. The h`NhnNhohhUj:=ubhß)rU=}rV=(hTX ``Data.Map``hd}rW=(hf]hg]hh]hi]hl]uhUj:=hp]rX=hyXData.MaprY=…rZ=}r[=(hTUhUjU=ubahbhçubhyX module comes from the r\=…r]=}r^=(hTX module comes from the h`NhnNhohhUj:=ubhß)r_=}r`=(hTX``containers``hd}ra=(hf]hg]hh]hi]hl]uhUj:=hp]rb=hyX containersrc=…rd=}re=(hTUhUj_=ubahbhçubhyX package, so we must list it:rf=…rg=}rh=(hTX package, so we must list it:h`NhnNhohhUj:=ubeubjÌ)ri=}rj=(hTXflibrary exposed-modules: Proglet other-modules: build-depends: containers, base == 4.*hUj=h`hahbjÏhd}rk=(jÑjÒhi]hh]hf]hg]hl]uhnK¦hohhp]rl=hyXflibrary exposed-modules: Proglet other-modules: build-depends: containers, base == 4.*rm=…rn=}ro=(hTUhUji=ubaubh})rp=}rq=(hTX®In addition, almost every package also depends on the ``base`` library package because it exports the standard ``Prelude`` module plus other basic modules like ``Data.List``.hUj=h`hahbhhd}rr=(hf]hg]hh]hi]hl]uhnK«hohhp]rs=(hyX6In addition, almost every package also depends on the rt=…ru=}rv=(hTX6In addition, almost every package also depends on the h`NhnNhohhUjp=ubhß)rw=}rx=(hTX``base``hd}ry=(hf]hg]hh]hi]hl]uhUjp=hp]rz=hyXbaser{=…r|=}r}=(hTUhUjw=ubahbhçubhyX1 library package because it exports the standard r~=…r=}r€=(hTX1 library package because it exports the standard h`NhnNhohhUjp=ubhß)r=}r‚=(hTX ``Prelude``hd}rƒ=(hf]hg]hh]hi]hl]uhUjp=hp]r„=hyXPreluder…=…r†=}r‡=(hTUhUj=ubahbhçubhyX& module plus other basic modules like rˆ=…r‰=}rŠ=(hTX& module plus other basic modules like h`NhnNhohhUjp=ubhß)r‹=}rŒ=(hTX ``Data.List``hd}r=(hf]hg]hh]hi]hl]uhUjp=hp]rŽ=hyX Data.Listr=…r=}r‘=(hTUhUj‹=ubahbhçubhyX.…r’=}r“=(hTX.h`NhnNhohhUjp=ubeubh})r”=}r•=(hTXºYou will notice that we have listed ``base == 4.*``. This gives a constraint on the version of the base package that our package will work with. The most common kinds of constraints are:hUj=h`hahbhhd}r–=(hf]hg]hh]hi]hl]uhnK¯hohhp]r—=(hyX$You will notice that we have listed r˜=…r™=}rš=(hTX$You will notice that we have listed h`NhnNhohhUj”=ubhß)r›=}rœ=(hTX``base == 4.*``hd}r=(hf]hg]hh]hi]hl]uhUj”=hp]rž=hyX base == 4.*rŸ=…r =}r¡=(hTUhUj›=ubahbhçubhyX‡. This gives a constraint on the version of the base package that our package will work with. The most common kinds of constraints are:r¢=…r£=}r¤=(hTX‡. This gives a constraint on the version of the base package that our package will work with. The most common kinds of constraints are:h`NhnNhohhUj”=ubeubh‡)r¥=}r¦=(hTUhUj=h`hahbhŠhd}r§=(hŒX-hi]hh]hf]hg]hl]uhnK³hohhp]r¨=(hŽ)r©=}rª=(hTX``pkgname >= n``r«=hUj¥=h`hahbh‘hd}r¬=(hf]hg]hh]hi]hl]uhnNhohhp]r­=h})r®=}r¯=(hTj«=hUj©=h`hahbhhd}r°=(hf]hg]hh]hi]hl]uhnK³hp]r±=hß)r²=}r³=(hTj«=hd}r´=(hf]hg]hh]hi]hl]uhUj®=hp]rµ=hyX pkgname >= nr¶=…r·=}r¸=(hTUhUj²=ubahbhçubaubaubhŽ)r¹=}rº=(hTX``pkgname >= n && < m``r»=hUj¥=h`hahbh‘hd}r¼=(hf]hg]hh]hi]hl]uhnNhohhp]r½=h})r¾=}r¿=(hTj»=hUj¹=h`hahbhhd}rÀ=(hf]hg]hh]hi]hl]uhnK´hp]rÁ=hß)rÂ=}rÃ=(hTj»=hd}rÄ=(hf]hg]hh]hi]hl]uhUj¾=hp]rÅ=hyXpkgname >= n && < mrÆ=…rÇ=}rÈ=(hTUhUjÂ=ubahbhçubaubaubhŽ)rÉ=}rÊ=(hTX``pkgname == n.*`` hUj¥=h`hahbh‘hd}rË=(hf]hg]hh]hi]hl]uhnNhohhp]rÌ=h})rÍ=}rÎ=(hTX``pkgname == n.*``rÏ=hUjÉ=h`hahbhhd}rÐ=(hf]hg]hh]hi]hl]uhnKµhp]rÑ=hß)rÒ=}rÓ=(hTjÏ=hd}rÔ=(hf]hg]hh]hi]hl]uhUjÍ=hp]rÕ=hyXpkgname == n.*rÖ=…r×=}rØ=(hTUhUjÒ=ubahbhçubaubaubeubh})rÙ=}rÚ=(hTXmThe last is just shorthand, for example ``base == 4.*`` means exactly the same thing as ``base >= 4 && < 5``.hUj=h`hahbhhd}rÛ=(hf]hg]hh]hi]hl]uhnK·hohhp]rÜ=(hyX(The last is just shorthand, for example rÝ=…rÞ=}rß=(hTX(The last is just shorthand, for example h`NhnNhohhUjÙ=ubhß)rà=}rá=(hTX``base == 4.*``hd}râ=(hf]hg]hh]hi]hl]uhUjÙ=hp]rã=hyX base == 4.*rä=…rå=}ræ=(hTUhUjà=ubahbhçubhyX! means exactly the same thing as rç=…rè=}ré=(hTX! means exactly the same thing as h`NhnNhohhUjÙ=ubhß)rê=}rë=(hTX``base >= 4 && < 5``hd}rì=(hf]hg]hh]hi]hl]uhUjÙ=hp]rí=hyXbase >= 4 && < 5rî=…rï=}rð=(hTUhUjê=ubahbhçubhyX.…rñ=}rò=(hTX.h`NhnNhohhUjÙ=ubeubeubhV)ró=}rô=(hTUhUjË:h`hahbhchd}rõ=(hf]hg]hh]hi]rö=jÁ:ahl]r÷=h auhnK»hohhp]rø=(hr)rù=}rú=(hTXBuilding the packagerû=hUjó=h`hahbhvhd}rü=(hf]hg]hh]hi]hl]uhnK»hohhp]rý=hyXBuilding the packagerþ=…rÿ=}r>(hTjû=h`NhnNhohhUjù=ubaubh})r>}r>(hTXSFor simple packages that's it! We can now try configuring and building the package:r>hUjó=h`hahbhhd}r>(hf]hg]hh]hi]hl]uhnK½hohhp]r>hyXUFor simple packages that’s it! We can now try configuring and building the package:r>…r>}r>(hTj>h`NhnNhohhUj>ubaubjÌ)r >}r >(hTX$ cabal configure $ cabal buildhUjó=h`hahbjÏhd}r >(j‰jXconsolejÑjÒhi]hh]hf]j}hg]hl]uhnKÀhohhp]r >hyX$ cabal configure $ cabal buildr >…r>}r>(hTUhUj >ubaubh})r>}r>(hTXFAssuming those two steps worked then you can also install the package:r>hUjó=h`hahbhhd}r>(hf]hg]hh]hi]hl]uhnKÅhohhp]r>hyXFAssuming those two steps worked then you can also install the package:r>…r>}r>(hTj>h`NhnNhohhUj>ubaubjÌ)r>}r>(hTX$ cabal installhUjó=h`hahbjÏhd}r>(j‰jXconsolejÑjÒhi]hh]hf]j}hg]hl]uhnKÇhohhp]r>hyX$ cabal installr>…r>}r>(hTUhUj>ubaubh})r>}r >(hTXÖFor libraries this makes them available for use in GHCi or to be used by other packages. For executables it installs the program so that you can run it (though you may first need to adjust your system's ``$PATH``).hUjó=h`hahbhhd}r!>(hf]hg]hh]hi]hl]uhnKËhohhp]r">(hyXÍFor libraries this makes them available for use in GHCi or to be used by other packages. For executables it installs the program so that you can run it (though you may first need to adjust your system’s r#>…r$>}r%>(hTXËFor libraries this makes them available for use in GHCi or to be used by other packages. For executables it installs the program so that you can run it (though you may first need to adjust your system's h`NhnNhohhUj>ubhß)r&>}r'>(hTX ``$PATH``hd}r(>(hf]hg]hh]hi]hl]uhUj>hp]r)>hyX$PATHr*>…r+>}r,>(hTUhUj&>ubahbhçubhyX).r->…r.>}r/>(hTX).h`NhnNhohhUj>ubeubeubhV)r0>}r1>(hTUhUjË:h`hahbhchd}r2>(hf]hg]hh]hi]r3>jÃ:ahl]r4>h6auhnKÐhohhp]r5>(hr)r6>}r7>(hTX Next stepsr8>hUj0>h`hahbhvhd}r9>(hf]hg]hh]hi]hl]uhnKÐhohhp]r:>hyX Next stepsr;>…r<>}r=>(hTj8>h`NhnNhohhUj6>ubaubh})r>>}r?>(hTXfWhat we have covered so far should be enough for very simple packages that you use on your own system.r@>hUj0>h`hahbhhd}rA>(hf]hg]hh]hi]hl]uhnKÒhohhp]rB>hyXfWhat we have covered so far should be enough for very simple packages that you use on your own system.rC>…rD>}rE>(hTj@>h`NhnNhohhUj>>ubaubh})rF>}rG>(hTX‡The next few sections cover more details needed for more complex packages and details needed for distributing packages to other people.rH>hUj0>h`hahbhhd}rI>(hf]hg]hh]hi]hl]uhnKÕhohhp]rJ>hyX‡The next few sections cover more details needed for more complex packages and details needed for distributing packages to other people.rK>…rL>}rM>(hTjH>h`NhnNhohhUjF>ubaubh})rN>}rO>(hTXtThe previous chapter covers building and installing packages -- your own packages or ones developed by other people.rP>hUj0>h`hahbhhd}rQ>(hf]hg]hh]hi]hl]uhnKØhohhp]rR>hyXuThe previous chapter covers building and installing packages – your own packages or ones developed by other people.rS>…rT>}rU>(hTjP>h`NhnNhohhUjN>ubaubeubeubhV)rV>}rW>(hTUhUhh`hahbhchd}rX>(hf]hg]hh]hi]rY>jÉ:ahl]rZ>hBauhnKÜhohhp]r[>(hr)r\>}r]>(hTXPackage conceptsr^>hUjV>h`hahbhvhd}r_>(hf]hg]hh]hi]hl]uhnKÜhohhp]r`>hyXPackage conceptsra>…rb>}rc>(hTj^>h`NhnNhohhUj\>ubaubh})rd>}re>(hTX¡Before diving into the details of writing packages it helps to understand a bit about packages in the Haskell world and the particular approach that Cabal takes.rf>hUjV>h`hahbhhd}rg>(hf]hg]hh]hi]hl]uhnKÞhohhp]rh>hyX¡Before diving into the details of writing packages it helps to understand a bit about packages in the Haskell world and the particular approach that Cabal takes.ri>…rj>}rk>(hTjf>h`NhnNhohhUjd>ubaubhV)rl>}rm>(hTUhUjV>h`hahbhchd}rn>(hf]hg]hh]hi]ro>j½:ahl]rp>h auhnKãhohhp]rq>(hr)rr>}rs>(hTXThe point of packagesrt>hUjl>h`hahbhvhd}ru>(hf]hg]hh]hi]hl]uhnKãhohhp]rv>hyXThe point of packagesrw>…rx>}ry>(hTjt>h`NhnNhohhUjr>ubaubh})rz>}r{>(hTXçPackages are a mechanism for organising and distributing code. Packages are particularly suited for "programming in the large", that is building big systems by using and re-using code written by different people at different times.r|>hUjl>h`hahbhhd}r}>(hf]hg]hh]hi]hl]uhnKåhohhp]r~>hyXëPackages are a mechanism for organising and distributing code. Packages are particularly suited for “programming in the largeâ€, that is building big systems by using and re-using code written by different people at different times.r>…r€>}r>(hTj|>h`NhnNhohhUjz>ubaubh})r‚>}rƒ>(hTX¹People organise code into packages based on functionality and dependencies. Social factors are also important: most packages have a single author, or a relatively small team of authors.r„>hUjl>h`hahbhhd}r…>(hf]hg]hh]hi]hl]uhnKêhohhp]r†>hyX¹People organise code into packages based on functionality and dependencies. Social factors are also important: most packages have a single author, or a relatively small team of authors.r‡>…rˆ>}r‰>(hTj„>h`NhnNhohhUj‚>ubaubh})rŠ>}r‹>(hTXSPackages are also used for distribution: the idea is that a package can be created in one place and be moved to a different computer and be usable in that different environment. There are a surprising number of details that have to be got right for this to work, and a good package system helps to simply this process and make it reliable.rŒ>hUjl>h`hahbhhd}r>(hf]hg]hh]hi]hl]uhnKîhohhp]rŽ>hyXSPackages are also used for distribution: the idea is that a package can be created in one place and be moved to a different computer and be usable in that different environment. There are a surprising number of details that have to be got right for this to work, and a good package system helps to simply this process and make it reliable.r>…r>}r‘>(hTjŒ>h`NhnNhohhUjŠ>ubaubh})r’>}r“>(hTXEPackages come in two main flavours: libraries of reusable code, and complete programs. Libraries present a code interface, an API, while programs can be run directly. In the Haskell world, library packages expose a set of Haskell modules as their public interface. Cabal packages can contain a library or executables or both.r”>hUjl>h`hahbhhd}r•>(hf]hg]hh]hi]hl]uhnKôhohhp]r–>hyXEPackages come in two main flavours: libraries of reusable code, and complete programs. Libraries present a code interface, an API, while programs can be run directly. In the Haskell world, library packages expose a set of Haskell modules as their public interface. Cabal packages can contain a library or executables or both.r—>…r˜>}r™>(hTj”>h`NhnNhohhUj’>ubaubh})rš>}r›>(hTXÏSome programming languages have packages as a builtin language concept. For example in Java, a package provides a local namespace for types and other definitions. In the Haskell world, packages are not a part of the language itself. Haskell programs consist of a number of modules, and packages just provide a way to partition the modules into sets of related functionality. Thus the choice of module names in Haskell is still important, even when using packages.rœ>hUjl>h`hahbhhd}r>(hf]hg]hh]hi]hl]uhnKúhohhp]rž>hyXÏSome programming languages have packages as a builtin language concept. For example in Java, a package provides a local namespace for types and other definitions. In the Haskell world, packages are not a part of the language itself. Haskell programs consist of a number of modules, and packages just provide a way to partition the modules into sets of related functionality. Thus the choice of module names in Haskell is still important, even when using packages.rŸ>…r >}r¡>(hTjœ>h`NhnNhohhUjš>ubaubeubhV)r¢>}r£>(hTUhUjV>h`hahbhchd}r¤>(hf]hg]hh]hi]r¥>jÂ:ahl]r¦>h1auhnMhohhp]r§>(hr)r¨>}r©>(hTXPackage names and versionsrª>hUj¢>h`hahbhvhd}r«>(hf]hg]hh]hi]hl]uhnMhohhp]r¬>hyXPackage names and versionsr­>…r®>}r¯>(hTjª>h`NhnNhohhUj¨>ubaubh})r°>}r±>(hTX All packages have a name, e.g. "HUnit". Package names are assumed to be unique. Cabal package names may contain letters, numbers and hyphens, but not spaces and may also not contain a hyphened section consisting of only numbers. The namespace for Cabal packages is flat, not hierarchical.r²>hUj¢>h`hahbhhd}r³>(hf]hg]hh]hi]hl]uhnMhohhp]r´>hyX$All packages have a name, e.g. “HUnitâ€. Package names are assumed to be unique. Cabal package names may contain letters, numbers and hyphens, but not spaces and may also not contain a hyphened section consisting of only numbers. The namespace for Cabal packages is flat, not hierarchical.rµ>…r¶>}r·>(hTj²>h`NhnNhohhUj°>ubaubh})r¸>}r¹>(hTXPackages also have a version, e.g "1.1". This matches the typical way in which packages are developed. Strictly speaking, each version of a package is independent, but usually they are very similar. Cabal package versions follow the conventional numeric style, consisting of a sequence of digits such as "1.0.1" or "2.0". There are a range of common conventions for "versioning" packages, that is giving some meaning to the version number in terms of changes in the package. Section [TODO] has some tips on package versioning.rº>hUj¢>h`hahbhhd}r»>(hf]hg]hh]hi]hl]uhnM hohhp]r¼>hyXPackages also have a version, e.g “1.1â€. This matches the typical way in which packages are developed. Strictly speaking, each version of a package is independent, but usually they are very similar. Cabal package versions follow the conventional numeric style, consisting of a sequence of digits such as “1.0.1†or “2.0â€. There are a range of common conventions for “versioning†packages, that is giving some meaning to the version number in terms of changes in the package. Section [TODO] has some tips on package versioning.r½>…r¾>}r¿>(hTjº>h`NhnNhohhUj¸>ubaubh})rÀ>}rÁ>(hTX—The combination of package name and version is called the *package ID* and is written with a hyphen to separate the name and version, e.g. "HUnit-1.1".hUj¢>h`hahbhhd}rÂ>(hf]hg]hh]hi]hl]uhnMhohhp]rÃ>(hyX:The combination of package name and version is called the rÄ>…rÅ>}rÆ>(hTX:The combination of package name and version is called the h`NhnNhohhUjÀ>ubh¿)rÇ>}rÈ>(hTX *package ID*hd}rÉ>(hf]hg]hh]hi]hl]uhUjÀ>hp]rÊ>hyX package IDrË>…rÌ>}rÍ>(hTUhUjÇ>ubahbhÇubhyXU and is written with a hyphen to separate the name and version, e.g. “HUnit-1.1â€.rÎ>…rÏ>}rÐ>(hTXQ and is written with a hyphen to separate the name and version, e.g. "HUnit-1.1".h`NhnNhohhUjÀ>ubeubh})rÑ>}rÒ>(hTXÎFor Cabal packages, the combination of the package name and version *uniquely* identifies each package. Or to put it another way: two packages with the same name and version are considered to *be* the same.hUj¢>h`hahbhhd}rÓ>(hf]hg]hh]hi]hl]uhnMhohhp]rÔ>(hyXDFor Cabal packages, the combination of the package name and version rÕ>…rÖ>}r×>(hTXDFor Cabal packages, the combination of the package name and version h`NhnNhohhUjÑ>ubh¿)rØ>}rÙ>(hTX *uniquely*hd}rÚ>(hf]hg]hh]hi]hl]uhUjÑ>hp]rÛ>hyXuniquelyrÜ>…rÝ>}rÞ>(hTUhUjØ>ubahbhÇubhyXr identifies each package. Or to put it another way: two packages with the same name and version are considered to rß>…rà>}rá>(hTXr identifies each package. Or to put it another way: two packages with the same name and version are considered to h`NhnNhohhUjÑ>ubh¿)râ>}rã>(hTX*be*hd}rä>(hf]hg]hh]hi]hl]uhUjÑ>hp]rå>hyXberæ>…rç>}rè>(hTUhUjâ>ubahbhÇubhyX the same.ré>…rê>}rë>(hTX the same.h`NhnNhohhUjÑ>ubeubh})rì>}rí>(hTX@Strictly speaking, the package ID only identifies each Cabal *source* package; the same Cabal source package can be configured and built in different ways. There is a separate installed package ID that uniquely identifies each installed package instance. Most of the time however, users need not be aware of this detail.hUj¢>h`hahbhhd}rî>(hf]hg]hh]hi]hl]uhnMhohhp]rï>(hyX=Strictly speaking, the package ID only identifies each Cabal rð>…rñ>}rò>(hTX=Strictly speaking, the package ID only identifies each Cabal h`NhnNhohhUjì>ubh¿)ró>}rô>(hTX*source*hd}rõ>(hf]hg]hh]hi]hl]uhUjì>hp]rö>hyXsourcer÷>…rø>}rù>(hTUhUjó>ubahbhÇubhyXû package; the same Cabal source package can be configured and built in different ways. There is a separate installed package ID that uniquely identifies each installed package instance. Most of the time however, users need not be aware of this detail.rú>…rû>}rü>(hTXû package; the same Cabal source package can be configured and built in different ways. There is a separate installed package ID that uniquely identifies each installed package instance. Most of the time however, users need not be aware of this detail.h`NhnNhohhUjì>ubeubeubhV)rý>}rþ>(hTUhUjV>h`hahbhchd}rÿ>(hf]hg]hh]hi]r?jÈ:ahl]r?hAauhnM#hohhp]r?(hr)r?}r?(hTX(Kinds of package: Cabal vs GHC vs systemr?hUjý>h`hahbhvhd}r?(hf]hg]hh]hi]hl]uhnM#hohhp]r?hyX(Kinds of package: Cabal vs GHC vs systemr?…r ?}r ?(hTj?h`NhnNhohhUj?ubaubh})r ?}r ?(hTXŸIt can be slightly confusing at first because there are various different notions of package floating around. Fortunately the details are not very complicated.r ?hUjý>h`hahbhhd}r?(hf]hg]hh]hi]hl]uhnM%hohhp]r?hyXŸIt can be slightly confusing at first because there are various different notions of package floating around. Fortunately the details are not very complicated.r?…r?}r?(hTj ?h`NhnNhohhUj ?ubaubj)r?}r?(hTUhUjý>h`hahbjhd}r?(hf]hg]hh]hi]hl]uhnNhohhp]r?(j)r?}r?(hTXëCabal packages Cabal packages are really source packages. That is they contain Haskell (and sometimes C) source code. Cabal packages can be compiled to produce GHC packages. They can also be translated into operating system packages. hUj?h`hahbjhd}r?(hf]hg]hh]hi]hl]uhnM.hp]r?(j)r?}r?(hTXCabal packagesr?hUj?h`hahbj hd}r?(hf]hg]hh]hi]hl]uhnM.hp]r?hyXCabal packagesr ?…r!?}r"?(hTj?hUj?ubaubj3)r#?}r$?(hTUhd}r%?(hf]hg]hh]hi]hl]uhUj?hp]r&?(h})r'?}r(?(hTXfCabal packages are really source packages. That is they contain Haskell (and sometimes C) source code.r)?hUj#?h`hahbhhd}r*?(hf]hg]hh]hi]hl]uhnM*hp]r+?hyXfCabal packages are really source packages. That is they contain Haskell (and sometimes C) source code.r,?…r-?}r.?(hTj)?hUj'?ubaubh})r/?}r0?(hTXsCabal packages can be compiled to produce GHC packages. They can also be translated into operating system packages.r1?hUj#?h`hahbhhd}r2?(hf]hg]hh]hi]hl]uhnM-hp]r3?hyXsCabal packages can be compiled to produce GHC packages. They can also be translated into operating system packages.r4?…r5?}r6?(hTj1?hUj/?ubaubehbjMubeubj)r7?}r8?(hTXªGHC packages This is GHC's view on packages. GHC only cares about library packages, not executables. Library packages have to be registered with GHC for them to be available in GHCi or to be used when compiling other programs or packages. The low-level tool ``ghc-pkg`` is used to register GHC packages and to get information on what packages are currently registered. You never need to make GHC packages manually. When you build and install a Cabal package containing a library then it gets registered with GHC automatically. Haskell implementations other than GHC have essentially the same concept of registered packages. For the most part, Cabal hides the slight differences. hUj?h`hahbjhd}r9?(hf]hg]hh]hi]hl]uhnM?hohhp]r:?(j)r;?}r?(hf]hg]hh]hi]hl]uhnM?hp]r??hyX GHC packagesr@?…rA?}rB?(hTj=?hUj;?ubaubj3)rC?}rD?(hTUhd}rE?(hf]hg]hh]hi]hl]uhUj7?hp]rF?(h})rG?}rH?(hTXáThis is GHC's view on packages. GHC only cares about library packages, not executables. Library packages have to be registered with GHC for them to be available in GHCi or to be used when compiling other programs or packages.rI?hUjC?h`hahbhhd}rJ?(hf]hg]hh]hi]hl]uhnM1hp]rK?hyXãThis is GHC’s view on packages. GHC only cares about library packages, not executables. Library packages have to be registered with GHC for them to be available in GHCi or to be used when compiling other programs or packages.rL?…rM?}rN?(hTjI?hUjG?ubaubh})rO?}rP?(hTXThe low-level tool ``ghc-pkg`` is used to register GHC packages and to get information on what packages are currently registered.hUjC?h`hahbhhd}rQ?(hf]hg]hh]hi]hl]uhnM6hp]rR?(hyXThe low-level tool rS?…rT?}rU?(hTXThe low-level tool hUjO?ubhß)rV?}rW?(hTX ``ghc-pkg``hd}rX?(hf]hg]hh]hi]hl]uhUjO?hp]rY?hyXghc-pkgrZ?…r[?}r\?(hTUhUjV?ubahbhçubhyXc is used to register GHC packages and to get information on what packages are currently registered.r]?…r^?}r_?(hTXc is used to register GHC packages and to get information on what packages are currently registered.hUjO?ubeubh})r`?}ra?(hTXYou never need to make GHC packages manually. When you build and install a Cabal package containing a library then it gets registered with GHC automatically.rb?hUjC?h`hahbhhd}rc?(hf]hg]hh]hi]hl]uhnM9hp]rd?hyXYou never need to make GHC packages manually. When you build and install a Cabal package containing a library then it gets registered with GHC automatically.re?…rf?}rg?(hTjb?hUj`?ubaubh})rh?}ri?(hTX—Haskell implementations other than GHC have essentially the same concept of registered packages. For the most part, Cabal hides the slight differences.rj?hUjC?h`hahbhhd}rk?(hf]hg]hh]hi]hl]uhnM=hp]rl?hyX—Haskell implementations other than GHC have essentially the same concept of registered packages. For the most part, Cabal hides the slight differences.rm?…rn?}ro?(hTjj?hUjh?ubaubehbjMubeubj)rp?}rq?(hTXfOperating system packages On operating systems like Linux and Mac OS X, the system has a specific notion of a package and there are tools for installing and managing packages. The Cabal package format is designed to allow Cabal packages to be translated, mostly-automatically, into operating system packages. They are usually translated 1:1, that is a single Cabal package becomes a single system package. It is also possible to make Windows installers from Cabal packages, though this is typically done for a program together with all of its library dependencies, rather than packaging each library separately. hUj?h`hahbjhd}rr?(hf]hg]hh]hi]hl]uhnMMhohhp]rs?(j)rt?}ru?(hTXOperating system packagesrv?hUjp?h`hahbj hd}rw?(hf]hg]hh]hi]hl]uhnMMhp]rx?hyXOperating system packagesry?…rz?}r{?(hTjv?hUjt?ubaubj3)r|?}r}?(hTUhd}r~?(hf]hg]hh]hi]hl]uhUjp?hp]r?(h})r€?}r?(hTX•On operating systems like Linux and Mac OS X, the system has a specific notion of a package and there are tools for installing and managing packages.r‚?hUj|?h`hahbhhd}rƒ?(hf]hg]hh]hi]hl]uhnMBhp]r„?hyX•On operating systems like Linux and Mac OS X, the system has a specific notion of a package and there are tools for installing and managing packages.r…?…r†?}r‡?(hTj‚?hUj€?ubaubh})rˆ?}r‰?(hTXåThe Cabal package format is designed to allow Cabal packages to be translated, mostly-automatically, into operating system packages. They are usually translated 1:1, that is a single Cabal package becomes a single system package.rŠ?hUj|?h`hahbhhd}r‹?(hf]hg]hh]hi]hl]uhnMFhp]rŒ?hyXåThe Cabal package format is designed to allow Cabal packages to be translated, mostly-automatically, into operating system packages. They are usually translated 1:1, that is a single Cabal package becomes a single system package.r?…rŽ?}r?(hTjŠ?hUjˆ?ubaubh})r?}r‘?(hTXÍIt is also possible to make Windows installers from Cabal packages, though this is typically done for a program together with all of its library dependencies, rather than packaging each library separately.r’?hUj|?h`hahbhhd}r“?(hf]hg]hh]hi]hl]uhnMKhp]r”?hyXÍIt is also possible to make Windows installers from Cabal packages, though this is typically done for a program together with all of its library dependencies, rather than packaging each library separately.r•?…r–?}r—?(hTj’?hUj?ubaubehbjMubeubeubeubhV)r˜?}r™?(hTUhUjV>h`hahbhchd}rš?(hf]hg]hh]hi]r›?jÄ:ahl]rœ?h7auhnMPhohhp]r?(hr)rž?}rŸ?(hTXUnit of distributionr ?hUj˜?h`hahbhvhd}r¡?(hf]hg]hh]hi]hl]uhnMPhohhp]r¢?hyXUnit of distributionr£?…r¤?}r¥?(hTj ?h`NhnNhohhUjž?ubaubh})r¦?}r§?(hTXQThe Cabal package is the unit of distribution. What this means is that each Cabal package can be distributed on its own in source or binary form. Of course there may dependencies between packages, but there is usually a degree of flexibility in which versions of packages can work together so distributing them independently makes sense.r¨?hUj˜?h`hahbhhd}r©?(hf]hg]hh]hi]hl]uhnMRhohhp]rª?hyXQThe Cabal package is the unit of distribution. What this means is that each Cabal package can be distributed on its own in source or binary form. Of course there may dependencies between packages, but there is usually a degree of flexibility in which versions of packages can work together so distributing them independently makes sense.r«?…r¬?}r­?(hTj¨?h`NhnNhohhUj¦?ubaubh})r®?}r¯?(hTX×It is perhaps easiest to see what being "the unit of distribution" means by contrast to an alternative approach. Many projects are made up of several interdependent packages and during development these might all be kept under one common directory tree and be built and tested together. When it comes to distribution however, rather than distributing them all together in a single tarball, it is required that they each be distributed independently in their own tarballs.r°?hUj˜?h`hahbhhd}r±?(hf]hg]hh]hi]hl]uhnMXhohhp]r²?hyXÛIt is perhaps easiest to see what being “the unit of distribution†means by contrast to an alternative approach. Many projects are made up of several interdependent packages and during development these might all be kept under one common directory tree and be built and tested together. When it comes to distribution however, rather than distributing them all together in a single tarball, it is required that they each be distributed independently in their own tarballs.r³?…r´?}rµ?(hTj°?h`NhnNhohhUj®?ubaubh})r¶?}r·?(hTXCabal's approach is to say that if you can specify a dependency on a package then that package should be able to be distributed independently. Or to put it the other way round, if you want to distribute it as a single unit, then it should be a single package.r¸?hUj˜?h`hahbhhd}r¹?(hf]hg]hh]hi]hl]uhnM`hohhp]rº?hyXCabal’s approach is to say that if you can specify a dependency on a package then that package should be able to be distributed independently. Or to put it the other way round, if you want to distribute it as a single unit, then it should be a single package.r»?…r¼?}r½?(hTj¸?h`NhnNhohhUj¶?ubaubeubhV)r¾?}r¿?(hTUhUjV>h`hahbhchd}rÀ?(hf]hg]hh]hi]rÁ?j¾:ahl]rÂ?h auhnMfhohhp]rÃ?(hr)rÄ?}rÅ?(hTX6Explicit dependencies and automatic package managementrÆ?hUj¾?h`hahbhvhd}rÇ?(hf]hg]hh]hi]hl]uhnMfhohhp]rÈ?hyX6Explicit dependencies and automatic package managementrÉ?…rÊ?}rË?(hTjÆ?h`NhnNhohhUjÄ?ubaubh})rÌ?}rÍ?(hTXàCabal takes the approach that all packages dependencies are specified explicitly and specified in a declarative way. The point is to enable automatic package management. This means tools like ``cabal`` can resolve dependencies and install a package plus all of its dependencies automatically. Alternatively, it is possible to mechanically (or mostly mechanically) translate Cabal packages into system packages and let the system package manager install dependencies automatically.hUj¾?h`hahbhhd}rÎ?(hf]hg]hh]hi]hl]uhnMhhohhp]rÏ?(hyXÀCabal takes the approach that all packages dependencies are specified explicitly and specified in a declarative way. The point is to enable automatic package management. This means tools like rÐ?…rÑ?}rÒ?(hTXÀCabal takes the approach that all packages dependencies are specified explicitly and specified in a declarative way. The point is to enable automatic package management. This means tools like h`NhnNhohhUjÌ?ubhß)rÓ?}rÔ?(hTX ``cabal``hd}rÕ?(hf]hg]hh]hi]hl]uhUjÌ?hp]rÖ?hyXcabalr×?…rØ?}rÙ?(hTUhUjÓ?ubahbhçubhyX can resolve dependencies and install a package plus all of its dependencies automatically. Alternatively, it is possible to mechanically (or mostly mechanically) translate Cabal packages into system packages and let the system package manager install dependencies automatically.rÚ?…rÛ?}rÜ?(hTX can resolve dependencies and install a package plus all of its dependencies automatically. Alternatively, it is possible to mechanically (or mostly mechanically) translate Cabal packages into system packages and let the system package manager install dependencies automatically.h`NhnNhohhUjÌ?ubeubh})rÝ?}rÞ?(hTX-It is important to track dependencies accurately so that packages can reliably be moved from one system to another system and still be able to build it there. Cabal is therefore relatively strict about specifying dependencies. For example Cabal's default build system will not even let code build if it tries to import a module from a package that isn't listed in the ``.cabal`` file, even if that package is actually installed. This helps to ensure that there are no "untracked dependencies" that could cause the code to fail to build on some other system.hUj¾?h`hahbhhd}rß?(hf]hg]hh]hi]hl]uhnMphohhp]rà?(hyXtIt is important to track dependencies accurately so that packages can reliably be moved from one system to another system and still be able to build it there. Cabal is therefore relatively strict about specifying dependencies. For example Cabal’s default build system will not even let code build if it tries to import a module from a package that isn’t listed in the rá?…râ?}rã?(hTXpIt is important to track dependencies accurately so that packages can reliably be moved from one system to another system and still be able to build it there. Cabal is therefore relatively strict about specifying dependencies. For example Cabal's default build system will not even let code build if it tries to import a module from a package that isn't listed in the h`NhnNhohhUjÝ?ubhß)rä?}rå?(hTX ``.cabal``hd}ræ?(hf]hg]hh]hi]hl]uhUjÝ?hp]rç?hyX.cabalrè?…ré?}rê?(hTUhUjä?ubahbhçubhyX· file, even if that package is actually installed. This helps to ensure that there are no “untracked dependencies†that could cause the code to fail to build on some other system.rë?…rì?}rí?(hTX³ file, even if that package is actually installed. This helps to ensure that there are no "untracked dependencies" that could cause the code to fail to build on some other system.h`NhnNhohhUjÝ?ubeubh})rî?}rï?(hTX¾The explicit dependency approach is in contrast to the traditional "./configure" approach where instead of specifying dependencies declaratively, the ``./configure`` script checks if the dependencies are present on the system. Some manual work is required to transform a ``./configure`` based package into a Linux distribution package (or similar). This conversion work is usually done by people other than the package author(s). The practical effect of this is that only the most popular packages will benefit from automatic package management. Instead, Cabal forces the original author to specify the dependencies but the advantage is that every package can benefit from automatic package management.hUj¾?h`hahbhhd}rð?(hf]hg]hh]hi]hl]uhnMzhohhp]rñ?(hyXšThe explicit dependency approach is in contrast to the traditional “./configure†approach where instead of specifying dependencies declaratively, the rò?…ró?}rô?(hTX–The explicit dependency approach is in contrast to the traditional "./configure" approach where instead of specifying dependencies declaratively, the h`NhnNhohhUjî?ubhß)rõ?}rö?(hTX``./configure``hd}r÷?(hf]hg]hh]hi]hl]uhUjî?hp]rø?hyX ./configurerù?…rú?}rû?(hTUhUjõ?ubahbhçubhyXj script checks if the dependencies are present on the system. Some manual work is required to transform a rü?…rý?}rþ?(hTXj script checks if the dependencies are present on the system. Some manual work is required to transform a h`NhnNhohhUjî?ubhß)rÿ?}r@(hTX``./configure``hd}r@(hf]hg]hh]hi]hl]uhUjî?hp]r@hyX ./configurer@…r@}r@(hTUhUjÿ?ubahbhçubhyX  based package into a Linux distribution package (or similar). This conversion work is usually done by people other than the package author(s). The practical effect of this is that only the most popular packages will benefit from automatic package management. Instead, Cabal forces the original author to specify the dependencies but the advantage is that every package can benefit from automatic package management.r@…r@}r@(hTX  based package into a Linux distribution package (or similar). This conversion work is usually done by people other than the package author(s). The practical effect of this is that only the most popular packages will benefit from automatic package management. Instead, Cabal forces the original author to specify the dependencies but the advantage is that every package can benefit from automatic package management.h`NhnNhohhUjî?ubeubh})r @}r @(hTXMThe "./configure" approach tends to encourage packages that adapt themselves to the environment in which they are built, for example by disabling optional features so that they can continue to work when a particular dependency is not available. This approach makes sense in a world where installing additional dependencies is a tiresome manual process and so minimising dependencies is important. The automatic package management view is that packages should just declare what they need and the package manager will take responsibility for ensuring that all the dependencies are installed.r @hUj¾?h`hahbhhd}r @(hf]hg]hh]hi]hl]uhnM†hohhp]r @hyXQThe “./configure†approach tends to encourage packages that adapt themselves to the environment in which they are built, for example by disabling optional features so that they can continue to work when a particular dependency is not available. This approach makes sense in a world where installing additional dependencies is a tiresome manual process and so minimising dependencies is important. The automatic package management view is that packages should just declare what they need and the package manager will take responsibility for ensuring that all the dependencies are installed.r@…r@}r@(hTj @h`NhnNhohhUj @ubaubh})r@}r@(hTXËSometimes of course optional features and optional dependencies do make sense. Cabal packages can have optional features and varying dependencies. These conditional dependencies are still specified in a declarative way however and remain compatible with automatic package management. The need to remain compatible with automatic package management means that Cabal's conditional dependencies system is a bit less flexible than with the "./configure" approach.r@hUj¾?h`hahbhhd}r@(hf]hg]hh]hi]hl]uhnMhohhp]r@hyXÑSometimes of course optional features and optional dependencies do make sense. Cabal packages can have optional features and varying dependencies. These conditional dependencies are still specified in a declarative way however and remain compatible with automatic package management. The need to remain compatible with automatic package management means that Cabal’s conditional dependencies system is a bit less flexible than with the “./configure†approach.r@…r@}r@(hTj@h`NhnNhohhUj@ubaubeubhV)r@}r@(hTUhUjV>h`hahbhchd}r@(hf]hg]hh]hi]r@jÇ:ahl]r@h>auhnM™hohhp]r@(hr)r@}r @(hTX Portabilityr!@hUj@h`hahbhvhd}r"@(hf]hg]hh]hi]hl]uhnM™hohhp]r#@hyX Portabilityr$@…r%@}r&@(hTj!@h`NhnNhohhUj@ubaubh})r'@}r(@(hTXOne of the purposes of Cabal is to make it easier to build packages on different platforms (operating systems and CPU architectures), with different compiler versions and indeed even with different Haskell implementations. (Yes, there are Haskell implementations other than GHC!)r)@hUj@h`hahbhhd}r*@(hf]hg]hh]hi]hl]uhnM›hohhp]r+@hyXOne of the purposes of Cabal is to make it easier to build packages on different platforms (operating systems and CPU architectures), with different compiler versions and indeed even with different Haskell implementations. (Yes, there are Haskell implementations other than GHC!)r,@…r-@}r.@(hTj)@h`NhnNhohhUj'@ubaubh})r/@}r0@(hTXCabal provides abstractions of features present in different Haskell implementations and wherever possible it is best to take advantage of these to increase portability. Where necessary however it is possible to use specific features of specific implementations.r1@hUj@h`hahbhhd}r2@(hf]hg]hh]hi]hl]uhnM¡hohhp]r3@hyXCabal provides abstractions of features present in different Haskell implementations and wherever possible it is best to take advantage of these to increase portability. Where necessary however it is possible to use specific features of specific implementations.r4@…r5@}r6@(hTj1@h`NhnNhohhUj/@ubaubh})r7@}r8@(hTX¾For example a package author can list in the package's ``.cabal`` what language extensions the code uses. This allows Cabal to figure out if the language extension is supported by the Haskell implementation that the user picks. Additionally, certain language extensions such as Template Haskell require special handling from the build system and by listing the extension it provides the build system with enough information to do the right thing.hUj@h`hahbhhd}r9@(hf]hg]hh]hi]hl]uhnM¦hohhp]r:@(hyX9For example a package author can list in the package’s r;@…r<@}r=@(hTX7For example a package author can list in the package's h`NhnNhohhUj7@ubhß)r>@}r?@(hTX ``.cabal``hd}r@@(hf]hg]hh]hi]hl]uhUj7@hp]rA@hyX.cabalrB@…rC@}rD@(hTUhUj>@ubahbhçubhyX} what language extensions the code uses. This allows Cabal to figure out if the language extension is supported by the Haskell implementation that the user picks. Additionally, certain language extensions such as Template Haskell require special handling from the build system and by listing the extension it provides the build system with enough information to do the right thing.rE@…rF@}rG@(hTX} what language extensions the code uses. This allows Cabal to figure out if the language extension is supported by the Haskell implementation that the user picks. Additionally, certain language extensions such as Template Haskell require special handling from the build system and by listing the extension it provides the build system with enough information to do the right thing.h`NhnNhohhUj7@ubeubh})rH@}rI@(hTXÇAnother similar example is linking with foreign libraries. Rather than specifying GHC flags directly, the package author can list the libraries that are needed and the build system will take care of using the right flags for the compiler. Additionally this makes it easier for tools to discover what system C libraries a package needs, which is useful for tracking dependencies on system libraries (e.g. when translating into Linux distribution packages).rJ@hUj@h`hahbhhd}rK@(hf]hg]hh]hi]hl]uhnM®hohhp]rL@hyXÇAnother similar example is linking with foreign libraries. Rather than specifying GHC flags directly, the package author can list the libraries that are needed and the build system will take care of using the right flags for the compiler. Additionally this makes it easier for tools to discover what system C libraries a package needs, which is useful for tracking dependencies on system libraries (e.g. when translating into Linux distribution packages).rM@…rN@}rO@(hTjJ@h`NhnNhohhUjH@ubaubh})rP@}rQ@(hTX]In fact both of these examples fall into the category of explicitly specifying dependencies. Not all dependencies are other Cabal packages. Foreign libraries are clearly another kind of dependency. It's also possible to think of language extensions as dependencies: the package depends on a Haskell implementation that supports all those extensions.rR@hUj@h`hahbhhd}rS@(hf]hg]hh]hi]hl]uhnM¶hohhp]rT@hyX_In fact both of these examples fall into the category of explicitly specifying dependencies. Not all dependencies are other Cabal packages. Foreign libraries are clearly another kind of dependency. It’s also possible to think of language extensions as dependencies: the package depends on a Haskell implementation that supports all those extensions.rU@…rV@}rW@(hTjR@h`NhnNhohhUjP@ubaubh})rX@}rY@(hTXzWhere compiler-specific options are needed however, there is an "escape hatch" available. The developer can specify implementation-specific options and more generally there is a configuration mechanism to customise many aspects of how a package is built depending on the Haskell implementation, the operating system, computer architecture and user-specified configuration flags.rZ@hUj@h`hahbhhd}r[@(hf]hg]hh]hi]hl]uhnM¼hohhp]r\@hyX~Where compiler-specific options are needed however, there is an “escape hatch†available. The developer can specify implementation-specific options and more generally there is a configuration mechanism to customise many aspects of how a package is built depending on the Haskell implementation, the operating system, computer architecture and user-specified configuration flags.r]@…r^@}r_@(hTjZ@h`NhnNhohhUjX@ubaubeubeubh^ehTUU transformerr`@NU footnote_refsra@}rb@Urefnamesrc@}rd@(Xpvp]re@(j%j2%ejÙ]rf@jÖaXpackage properties]rg@jU aXconditional blocks]rh@j‡0aXbuild information]ri@(j— j« jýj'j‘j9j%j¬eXpackage descriptions]rj@j@ajŽ ]rk@j‹ aXhackage]rl@jIaXsystem-dependent parameters]rm@(jj+jej|$j(*j‰.jû.eXhaddock]rn@(j j eXpackage versioning policy]ro@jáaXfilerp@]rq@j?)rr@}rs@(hTj#hd}rt@(Unamejp@hi]hh]hf]Urefnameru@jp@hg]hl]uhUjß"hp]rv@hyXfilerw@…rx@}ry@(hTUhUjr@ubahbjCubaXmore complex packages]rz@jWaj¼]r{@j¹ajõ]r|@jòajx ]r}@(ju j†$j™euUsymbol_footnotesr~@]r@Uautofootnote_refsr€@]r@Usymbol_footnote_refsr‚@]rƒ@U citationsr„@]r…@hohU current_liner†@NUtransform_messagesr‡@]rˆ@(hQ)r‰@}rŠ@(hTUhd}r‹@(hf]UlevelKhi]hh]rŒ@jj:aUsourcehahg]hl]UlineM¹Utypej–:uhp]r@h})rŽ@}r@(hTUhd}r@(hf]hg]hh]hi]hl]uhUj‰@hp]r‘@hyX2Duplicate implicit target name: "foo-bench.cabal".r’@…r“@}r”@(hTUhUjŽ@ubahbhubahbj“:ubhQ)r•@}r–@(hTUhd}r—@(hf]UlevelKhi]r˜@j #ahh]r™@j #aUsourcehahg]hl]UlineM UtypeUERRORrš@uhp]r›@h})rœ@}r@(hTUhd}rž@(hf]hg]hh]hi]hl]uhUj•@hp]rŸ@hyXUnknown target name: "file".r @…r¡@}r¢@(hTUhUjœ@ubahbhubahbj“:ubhQ)r£@}r¤@(hTUhd}r¥@(hf]UlevelKhi]hh]Usourcehahg]hl]UlineM*Utypej–:uhp]r¦@h})r§@}r¨@(hTUhd}r©@(hf]hg]hh]hi]hl]uhUj£@hp]rª@hyX2Hyperlink target "buildtoolsbc" is not referenced.r«@…r¬@}r­@(hTUhUj§@ubahbhubahbj“:ubhQ)r®@}r¯@(hTUhd}r°@(hf]UlevelKhi]hh]UsourcejÆ hg]hl]UlineM= Utypej–:uhp]r±@h})r²@}r³@(hTUhd}r´@(hf]hg]hh]hi]hl]uhUj®@hp]rµ@hyX-Hyperlink target "haskell" is not referenced.r¶@…r·@}r¸@(hTUhUj²@ubahbhubahbj“:ubhQ)r¹@}rº@(hTUhd}r»@(hf]UlevelKhi]hh]UsourcejÆ hg]hl]UlineME Utypej–:uhp]r¼@h})r½@}r¾@(hTUhd}r¿@(hf]hg]hh]hi]hl]uhUj¹@hp]rÀ@hyX,Hyperlink target "hoogle" is not referenced.rÁ@…rÂ@}rÃ@(hTUhUj½@ubahbhubahbj“:ubhQ)rÄ@}rÅ@(hTUhd}rÆ@(hf]UlevelKhi]hh]UsourcejÆ hg]hl]UlineMG Utypej–:uhp]rÇ@h})rÈ@}rÉ@(hTUhd}rÊ@(hf]hg]hh]hi]hl]uhUjÄ@hp]rË@hyX.Hyperlink target "hscolour" is not referenced.rÌ@…rÍ@}rÎ@(hTUhUjÈ@ubahbhubahbj“:ubeUreporterrÏ@NUid_startrÐ@K U autofootnotesrÑ@]rÒ@U citation_refsrÓ@}rÔ@Uindirect_targetsrÕ@]rÖ@Usettingsr×@(cdocutils.frontend Values rØ@orÙ@}rÚ@(Ufootnote_backlinksrÛ@KUrecord_dependenciesrÜ@NU language_coderÝ@UenrÞ@U tracebackrß@ˆUpep_referencesrà@NUstrip_commentsrá@NU toc_backlinksrâ@Uentryrã@U rfc_base_urlrä@Uhttps://tools.ietf.org/html/rå@U datestampræ@NU report_levelrç@KUsmartquotes_localesrè@NU _destinationré@NU halt_levelrê@KU strip_classesrë@NhvNUerror_encoding_error_handlerrì@Ubackslashreplacerí@Udebugrî@NUembed_stylesheetrï@‰Uoutput_encoding_error_handlerrð@Ustrictrñ@U sectnum_xformrò@KUdump_transformsró@NU docinfo_xformrô@KUwarning_streamrõ@NUpep_file_url_templaterö@Upep-%04dr÷@Uexit_status_levelrø@KUconfigrù@NUstrict_visitorrú@NUcloak_email_addressesrû@ˆUtrim_footnote_reference_spacerü@‰Uenvrý@NUdump_pseudo_xmlrþ@NUexpose_internalsrÿ@NUsectsubtitle_xformrA‰U source_linkrANUrfc_referencesrANUoutput_encodingrAUutf-8rAU source_urlrANUinput_encodingrAU utf-8-sigrAU_disable_configrANU id_prefixr AUUcharacter_level_inline_markupr A‰U tab_widthr AKUerror_encodingr AUUTF-8r AU_sourcerAhaUgettext_compactrAˆU generatorrANUdump_internalsrANU smart_quotesrAˆU pep_base_urlrAU https://www.python.org/dev/peps/rAUsyntax_highlightrAUlongrAUinput_encoding_error_handlerrAjñ@Uauto_id_prefixrAUidrAUdoctitle_xformrA‰Ustrip_elements_with_classesrANU _config_filesrA]Ufile_insertion_enabledrAˆU raw_enabledrAKU dump_settingsrANubUsymbol_footnote_startr AKUidsr!A}r"A(ja1j]1j(jg$j`0j\0j¾"jº"j_j[j%7j!7j¤+j +j# j j€j|j+j'jI0jE0hýhùj 0j0j1#j-#jX jVj• j j­j©j5j1jŽjŠj7&j3&j j jÌjÈjô jï jÄ:j˜?jÂ:j¢>jI jE jy)jz)jž.jš.j/j+j,jþ+j j j)9jð!jÉ:jV>j®%jª%j}/jy/j§j£jÉ8jÅ8jFh\jœjÛ/jØ jÑ j¾:j¾?j jljÔ3jÐ3jÐjÊjâ,jÞ,jöjòj-j‰-jX-jT-j¦j¡jÆ:j>;j #j•@j #j#j?!j;!j:j}:jÜ jØ j)!j%!jö/jñ/jà j¾ j>:hWjãjßjj:jf:jøjôj{jwjÉ#jÅ#jê1jæ1j^+jZ+jÖ'jÒ'jÈ:jý>jX5jT5jÐ jÑ jÄ0jÀ0j®jªjDj@j30j/0j—j“jKjGjjOjÁ:jó=jÓ.jÏ.jÑ(jÍ(jœj˜j!jjxjtjœ$j˜$jQjMj”jj½:jl>jw9js9j÷-jó-jájÝj×jÓjÏjËjç jã j jý j=j9jè6jä6j<j8jRjNjJjFjp(jl(jÈjÄjÜjØjÛj×j‡j‚jù0jõ0jû jö j²/j®/jt7jp7j!j‰!jÉjÅja.j].j16j-6j¿:j|<jHjBjbj^jÇ:j@j›&j—&jí jé jã&jß&j²8hZjŠ0j¨1jjj/j /j¼:jË:j«j§jE"jA"jÊjÆjz'jv'jújöj”jjjjFjBj·4j³4j j j²7j®7jÅ:j=hkh^jU!jQ!j=*j9*jjj°j¬jD4j@4jÀ:jÓ;jâjÞjÏ4jÊ4j´j°j_j[jjj¤*j *j:j:j# j j«6j§6jò jî jâ)jÞ)jj jÃ:j0>j®jªjÂ-j¾-j #j#já jÜ j,.j(.uUsubstitution_namesr#A}r$Ahbhohd}r%A(hf]hi]hh]Usourcehahg]hl]uU footnotesr&A]r'AUrefidsr(A}r)A(jÐ ]r*AjÍ ajy)]r+Ajv)auub.