s      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~/ Safe-InferredETemplate Engine. Perform the following replacements on a line basis:   script src="foo" /script ==>  script[[foo]] /script   link-href="foo" rel="stylesheet" type="text/css" / ==>  styletype="text/css"[[foo]] /style  None    Safe-Inferred5Run with some cleanup scope. Regardless of exceptions/ threads, all  actions ) will be run by the time it exits. The ' actions will be run in reverse order. Add a cleanup action to a 4 scope. If the return action is not run by the time  3 terminates then it will be run then. The argument  is  to say  run the action, . to say ignore the action (and never run it).   Safe-Inferred 'Like a barrier, but based on callbacks                 Safe-Inferred !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ None"Run and then call a continuation. Strict version BApply a modification, run an action, then undo the changes after. HCapture a continuation. The continuation should be called at most once. _ Calling the same continuation, multiple times, in parallel, results in incorrect behaviour.                Safe-Inferred None<Print all withTiming information and clear the information.   None!HGiven a pool, and a function that breaks the S invariants, restore them 7 They are only allowed to touch threadsLimit or todo "HAdd a new task to the pool, may be cancelled by sending it an exception #IAdd a new task to the pool, may be cancelled by sending it an exception. ( Takes priority over everything else. $YTemporarily increase the pool by 1 thread. Call the cleanup action to restore the value. ? After calling cleanup you should requeue onto a new thread. %<Run all the tasks in the pool on the given number of works. F If any thread throws an exception, the exception will be reraised. &'()*+,-./0123456789:;<!"#$%-"#$%&'()*+,-./1023456789:;<!"#$%None =XSome users are blocked (non-empty), plus an action to call once we go back to Available >'Some number of resources are available ?(number of currently available resources @Tqueue of people with how much they want and the action when it is allocated to them VA type representing an external resource which the build system should respect. There  are two ways to create  s in Shake:  > creates a finite resource, stopping too many actions running  simultaneously.  A creates a throttled resource, stopping too many actions running  over a short time period. These resources are used with % when defining rules. Typically only  system commands (such as ) should be run inside ,  not commands such as . 'Be careful that the actions run within # do not themselves require further  resources, or you may get a "0thread blocked indefinitely in an MVar operation" exception. 1 If an action requires multiple resources, use  to avoid deadlock. AKey used for Eq/EOrd operations. To make withResources work, we require newResourceIO < newThrottleIO BString used for Show C3Acquire the resource and call the function. Passes 1 to indicate you have acquired with no blocking,  or V to say there was waiting and you must not do significant computation on that thread. DMYou should only ever releaseResource that you obtained with acquireResource.  A version of 3 that runs in IO, and can be called before calling .  Most people should use  instead.  A version of 3 that runs in IO, and can be called before calling .  Most people should use  instead. E=>FG?@HABCDIJKLMNOCD E>=FG?@HABCDIJKLMNO Safe-Inferred PQRSTUVWXYZ[\QWXYZ[\ PQRSTUVWXYZ[\None]<Generates an report given some build system profiling data. ^_`abcdefghijk]lmnopqr^_`abcdefghij] ^_`abcdefghijk]lmnopqr Safe-Inferreds!This is a hot-spot, so optimised tuvswxyzvswtuvswxyz Safe-Inferred{|}~{}~{|}~ Safe-Inferred!{} None- $None Safe-Inferred Drop the first directory from a . Should only be used on  relative paths. # dropDirectory1 "aaa/bbb" == "bbb"  dropDirectory1 "aaa/" == ""  dropDirectory1 "aaa" == ""  dropDirectory1 "" == "" Take the first component of a . Should only be used on  relative paths. # takeDirectory1 "aaa/bbb" == "aaa"  takeDirectory1 "aaa/" == "aaa"  takeDirectory1 "aaa" == "aaa"  Normalise a , trying to do:  All  become /  foo/bar/../baz becomes foo/baz  foo/./bar becomes foo/bar  foo//bar becomes foo/bar aThis function is not based on the normalise function from the filepath library, as that function  is quite broken. *Convert to native path separators, namely \ on Windows. Convert all path separators to /, even on Windows. ;Remove the current extension and add another, an alias for . The extension of executables, "exe" on Windows and "" otherwise. 8 Safe-Inferred  NoneLike ', but the results may be in any order.    !None UTF8 ByteString  ASCII ByteString            "None  !"#$ !"#  !"#$#None%&'()*+,-./0123456789: &(*,01245%&'()*+,-./0123456789:$None -A type synonym for file patterns, containing // and *. For the syntax  and semantics of  see . Most  normaliseExd  values are suitable as  values which match ' only that specific file. On Windows \ is treated as equivalent to /. You can write + values as a literal string, or build them  up using the operators %, &  and '. However, beware that:  On Windows, use % from Development.Shake.FilePath instead of from  System.FilePath - otherwise "//*" <.> exe results in "//*\\.exe".  If the second argument of && has a leading path separator (namely /) . then the second argument will be returned. ;$Return is (brackets, matched, rest) Match a  against a $, There are only two special forms:  *= matches an entire path component, excluding any separators.  //1 matches an arbitrary number of path components. Some examples:  test.c matches test.c and nothing else.  *.c matches all .c$ files in the current directory, so file.c matches,  but file.h and dir/file.c don't.  //*.c matches all .c7 files in the current directory or its subdirectories,  so file.c, dir/file.c and dir1/dir2/file.c all match, but file.h and  dir/file.h don't.  dir/*/*# matches all files one level below dir, so dir/one/file.c and  dir/two/file.h match, but file.c, one/dir/file.c, dir/file.h  and dir/one/two/file.c don't. !Patterns with constructs such as foo/../bar will never match  normalised ( values, so are unlikely to be correct.  Join two  values by inserting two / characters between them. Y Will first remove any trailing path separators on the first argument, and any leading  separators on the second.  "dir" <//> "*" == "dir//*" <?Given a pattern, return the directory that requires searching,  with : if it requires a recursive search. Must be conservative.  Examples: $ directories1 "*.xml" == ("",False) % directories1 "//*.xml" == ("",True) + directories1 "foo//*.xml" == ("foo",True) 3 directories1 "foo/bar/*.xml" == ("foo/bar",False) ) directories1 "*/bar/*.xml" == ("",True) =NGiven a set of patterns, produce a set of directories that require searching,  with D if it requires a recursive search. Must be conservative. Examples: . directories ["*.xml","//*.c"] == [("",True)] F directories ["bar/*.xml","baz//*.c"] == [("bar",False),("baz",True)] F directories ["bar/*.xml","baz//*.c"] == [("bar",False),("baz",True)] >#Is the pattern free from any * and . ?Do they have the same * and  counts in the same order @EExtract the items that match the wildcards. The pair must match with . AGiven the result of @, substitute it back in to a ? pattern. / p '?==' x ==> substitute (extract p x) p == x BCDEFGHIJKLMNOPQRSTUV;<=>?@A <=>?@ABC MLKJIHGFEDNQPORSTUV;<=>?@A(NoneW1A machine that takes inputs and produces outputs ZInformation about the current state of the build, obtained by passing a callback function  to ). Typically a program will use * to poll this value and produce ? status messages, which is implemented using this data type. ! Starts out  , becomes  a target name if a rule fails. "HNumber of rules which were required, but were already in a valid state. #8Number of rules which were have been built in this run. $XNumber of rules which have been built previously, but are not yet known to be required. %hNumber of rules which are currently required (ignoring dependencies that do not change), but not built. &Time spent building " rules in previous runs. 'Time spent building # rules. (Time spent building $ rules in previous runs. )Time spent building %b rules in previous runs, plus the number which have no known time (have never been built before). X4return (number of seconds, percentage, explanation) *PGiven a sampling interval (in seconds) and a way to display the status message, , produce a function suitable for using as ). 6 This function polls the progress information every n seconds, produces a status 7 message and displays it using the display function. .Typical status messages will take the form of  1m25s (15%), indicating that the build x is predicted to complete in 1 minute 25 seconds (85 seconds total), and 15% of the necessary build time has elapsed. Z This function uses past observations to predict future behaviour, and as such, is only [ guessing. The time is likely to go up as well as down, and will be less accurate from a < clean build (as the system has fewer past observations). FThe current implementation is to predict the time remaining (based on ) ) and the  work already done ('(). The percentage is then calculated as  remaining / (done + remaining), , while time left is calculated by scaling  remaining* by the observed work rate in this build,  roughly done / time_elapsed. YUGiven a list of progress inputs, what would you have suggested (seconds, percentage) Z9Given a trace, display information about how well we did +FSet the title of the current console window to the given text. If the  environment variable $TERM is set to xterm# this uses xterm escape sequences. C On Windows, if not detected as an xterm, this function uses the SetConsoleTitle API. ,Call the program shake-progress if it is on the $PATH. The program is called with  the following arguments:  --title=string - the string passed to progressProgram.  --state=Normal , or one of  NoProgress, Normal, or Error to indicate - what state the progress bar should be in.   --value=25: - the percent of the build that has completed, if not in  NoProgress state. ;The program will not be called consecutively with the same --state and --value options. ZWindows 7 or higher users can get taskbar progress notifications by placing the following  program in their $PATH:  ,https://github.com/ndmitchell/shake/releases. -HA simple method for displaying progress messages, suitable for using as ). V This function writes the current progress to the titlebar every five seconds using +,  and calls any shake-progress program on the $PATH using ,. 0[\]^_`Wab !"#$%&'()cdefghijklmX*YZnopqrst+,-uvw[\]^_` !"#$%&'()*YZ+,-[\]^_`Wab !"#$%&'()cdefghijklmX*YZnopqrst+,-uvw* Safe-Inferred.<Error representing all expected exceptions thrown by Shake. L Problems when executing rules will be raising using this exception type. 0<The target that was being built when the exception occured. 1 The stack of targets, where the 0 is last. 2*The underlying exception that was raised. ./012xyz{|}~ ./012xz|}~./012xyz{|}~+None ,None-None.3An equality check and a cost. 4The values are not equal. 5JThe equality check was expensive, as the results are not trivially equal. 6The equality check was cheap. 7!The verbosity data type, used by C. 8@Print messages for virtually everything (mostly for debugging). 9JPrint errors, full command line and status messages when starting a rule. :3Print errors and full command lines when running a . or  command. ;Print errors and #  command-name (for  file-name) when running a / command. <1Only print essential messages, typically errors. =Don't print any messages. ,Internal type, copied from Hide in Uniplate >UOptions to control the execution of Shake, usually specified by overriding fields in  `:   `{A=4, E=[" report.html"]}The $ instance for this type reports the Q and R$ fields as having the abstract type ,  because " cannot be defined for functions. @ Defaults to .shakeD. The prefix of the filename used for storing Shake metadata files. $ All metadata files will be named @. extension , for some  extension.  If the @. directory does not exist it will be created. A Defaults to 19. Maximum number of rules to run in parallel, similar to  make --jobs=N. e For many build systems, a number equal to or slightly less than the number of physical processors  works well. B Defaults to 1*. The version number of your build rules. N Change the version number to force a complete rebuild, such as when making V significant changes to the rules that require a wipe. The version number should be ? set in the source code, and not passed on the command line. C Defaults to ;0. What level of messages should be printed out. D Defaults to G. Operate in staunch mode, where building continues even after errors,  similar to make --keep-going. E Defaults to []C. Write a profiling report to a file, showing which rules rebuilt, [ why, and how much time they took. Useful for improving the speed of your build systems.  If the file extension is .json it will write JSON data; if .js it will write Javascript;  if .trace' it will write trace events (load into about://tracing in Chrome); ! otherwise it will write HTML. F Defaults to -. Perform sanity checks during building, see Y for details. G Defaults to  109. How often to flush Shake metadata files in seconds, or  to never flush explicitly. m It is possible that on abnormal termination (not Haskell exceptions) any rules that completed in the last  G seconds will be lost. H Defaults to $. Assume all build objects are clean/ dirty, see \ for details.  Can be used to implement  make --touch. I Defaults to []l. A list of substrings that should be abbreviated in status messages, and their corresponding abbreviation. 1 Commonly used to replace the long paths (e.g. .make/i586-linux-gcc/output) with an abbreviation (e.g. $OUT). J Defaults to . Write a message to @.storage3 whenever a storage event happens which may impact { on the current stored progress. Examples include database version number changes, database compaction or corrupt files. K Defaults to  . Change stdout and stderr( to line buffering while running Shake. L Defaults to 6. Print timing information for each stage at the end. M Default to .. Should you run command line actions, set to 4 to skip actions whose output streams and exit code S are not used. Useful for profiling the non-command portion of the build system. N Default to X*. How to check if a file has changed, see S for details. O Default to T. After running a rule to create a file, is it an error if the file does not exist. # Provided for compatibility with make and ninja, (which have ugly file creation semantics). P Default to '[]'I. After the build system completes, write a list of all files which were live in that run, d i.e. those which Shake checked were valid or rebuilt. Produces best answers if nothing rebuilds. QbDefaults to no action. A function called when the build starts, allowing progress to be reported. d The function is called on a separate thread, and that thread is killed when the build completes. < For applications that want to display progress messages, -( is often sufficient, but more advanced  users should look at the  data type. RDefaults to writing using ZB. A function called to output messages from Shake, along with the 7 at ` which that message should be printed. This function will be called atomically from all other R functions.  The 7, will always be greater than or higher than C. S8How should you determine if a file has changed, used by N. The most common values are  X (very fast, touch causes files to rebuild) and U  (a bit slower, touch) does not cause input files to rebuild). TOA file is rebuilt if either its modification time or its digest has changed. A touch will force a rebuild, a but even if a files modification time is reset afterwards, changes will also cause a rebuild. UUse V for input/source files and X for output files. VrA file is rebuilt if both its modification time and digest have changed. For efficiency reasons, the modification J time is checked first, and if that has changed, the digest is checked. WUCompare equality of file contents digests, a file has changed if its digest changes.  A touchc will not force a rebuild. Use this mode if modification times on your file system are unreliable. XcCompare equality of modification timestamps, a file has changed if its last modified time changes.  A touch_ will force a rebuild. This mode is fast and usually sufficiently accurate, so is the default. Y&Which lint checks to perform, used by F. Z?Track which files are accessed by command line programs run by command or cmd, using  tracker.exe as supplied Q with the Microsoft .NET 4.5 SDK (Windows only). Also performs all checks from [". Note that some programs are not > tracked properly, particularly cygwin programs (it seems). [|The most basic form of linting. Checks that the current directory does not change and that results do not change after they # are first written. Any calls to needed: will assert that they do not cause a rule to be rebuilt. \:The current assumptions made by the build system, used by H. These options ] allow the end user to specify that any rules run are either to be treated as clean, or as 6 dirty, regardless of what the build system thinks. ?These assumptions only operate on files reached by the current 0 commands. Any 3 other files in the database are left unchanged. ]NThis assumption is unsafe, and may lead to incorrect build results in this run. m Assume that all rules reached are clean in this run. Only useful for benchmarking, to remove any overhead  from running 1 operations. ^bThis assumption is unsafe, and may lead to incorrect build results in this run, and in future runs. g Assume and record that all rules reached are clean and do not require rebuilding, provided the rule  has a 1G and has been built before. Useful if you have modified a file in some ^ inconsequential way, such as only the comments or whitespace, and wish to avoid a rebuild. _NAssume that all rules reached are dirty and require rebuilding, equivalent to 1 always  returning  . Useful to undo the results of ^%, for benchmarking rebuild speed and a for rebuilding if untracked dependencies have changed. This assumption is safe, but may cause # more rebuilding than necessary. `The default set of >. :3456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`9 !"#$%&'()3456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`36547=<;:98>?@ABCDEFGHIJKLMNOPQRSXWVUTY[Z\_^]`2None$Is the exception asyncronous, not a  coding error that should be ignored Storage options Logging function Witness Execute 3None+Given a Key, find the value stored on disk JGiven both Values, see if they are equal and how expensive that check was LGiven a stack and a key, either raise an exception or successfully build it OInvariant: The database does not have any cycles where a Key depends on itself TReturn either an exception (crash), or (how much time you spent waiting, the value) uGiven a map of representing a dependency order (with a show for error messages), find an ordering for the items such 1 that no item points to an item before itself. . Raise an error if you end up with a cycle. ;Eliminate all errors from the database, pretending they don't exist N/4None"aThe a monad, use   to raise D actions into it, and  to execute files.  Action values are used by g and j. The a$ monad tracks the dependencies of a c. bLDefine a set of rules. Rules can be created with calls to functions such as 5 or j. Rules are combined  with either the a" instance, or (more commonly) the 4 instance and do notation. To define your own  custom types of rule, see Development.Shake.Rule. c8Define a pair of types that can be used by Shake rules. / To import all the type classes required see Development.Shake.Classes. d [Required] Retrieve the value associated with a key, if available. As an example for filenames/1timestamps, if the file exists you should return  ' the timestamp, but otherwise return !. For rules whose values are not  stored externally, d should return . e [Optional]? Equality check, with a notion of how expensive the check was. fODefine an alias for the six type classes required for things involved in Shake 6s. G This alias is only available in GHC 7.4 and above, and requires the ConstraintKinds extension. cTo define your own values meeting the necessary constraints it is convenient to use the extensions  GeneralizedNewtypeDeriving and DeriveDataTypeable to write: [ newtype MyType = MyType (String, Bool) deriving (Show,Typeable,Eq,Hashable,Binary,NFData) g4Add a rule to build a key, returning an appropriate a . All rules at a given priority P must be disjoint. Rules have priority 1 by default, but can be modified with h. hVChange the priority of a given set of rules, where higher priorities take precedence. S All matching rules at a given priority must be disjoint, or an error is raised. : All builtin Shake rules have priority between 0 and 1.  Excessive use of h is discouraged. As an example:    h 4 $ "hello.*" %> \out ->  writeFile' out "hello.*"  h 8 $ "*.txt" %> \out ->  writeFile' out "*.txt" In this example  hello.txtJ will match the second rule, instead of raising an error about ambiguity. idChange the matching behaviour of rules so rules do not have to be disjoint, but are instead matched N in order. Only recommended for small blocks containing a handful of rules.    i $ do  "hello.*" %> \out ->  writeFile' out "hello.*"  "*.txt" %> \out ->  writeFile' out "*.txt" In this example  hello.txtI will match the first rule, instead of raising an error about ambiguity. jCRun an action, usually used for specifying top-level requirements.    main =  ` $ do  j $ do  b <- 7 "file.src"  when b $  ["file.out"] This j builds file.out, but only if file.src exists. The j 0 will be run in every build execution (unless k is used), so only cheap 4 operations should be performed. All arguments to j' may be run in parallel, in any order. %For the standard requirement of only !ing a fixed list of files in the j,  see 8. kNRemove all actions specified in a set of rules, usually used for implementing 0 command line specification of what to build. l!If an exception is raised by the a, perform some D. m After an a, perform some D!, even if there is an exception. /Internal main function (not exported publicly) naExecute a rule, returning the associated values. If possible, the rules will be run in parallel. F This function requires that appropriate rules have been added with g.  All key values passed to n become dependencies of the a. o+Apply a single rule, equivalent to calling n( with a singleton list. Where possible,  use n to allow parallelism. pGet the initial >2, these will not change during the build process. q7Write an action to the trace list, along with the start/#end time of running the IO action.  The  and . functions automatically call q. 3 The trace list is used for profile reports (see E). r2Write a message to the output when the verbosity (C) is appropriate. D The output will not be interleaved with any other Shake messages 4 (other than those generated by system commands). s2Write a message to the output when the verbosity (C) is appropriate. D The output will not be interleaved with any other Shake messages 4 (other than those generated by system commands). t2Write a message to the output when the verbosity (C) is appropriate. D The output will not be interleaved with any other Shake messages 4 (other than those generated by system commands). u3Get the current verbosity level, originally set by C . If you I want to output information to the console, you are recommended to use  r / s / t&, which ensures multiple messages are = not interleaved. The verbosity can be modified locally by v. v1Run an action with a particular verbosity level.  Will not update the C returned by p and will  not have any impact on 8 tracing. wRun an action with </ verbosity, in particular messages produced by q  (including from  or .%) will not be printed to the screen.  Will not update the C returned by p and will  not turn off any 8 tracing. x<Track that a key has been used by the action preceeding it. y?Track that a key has been changed by the action preceeding it. z6Allow any matching key to violate the tracking rules. {hCreate a finite resource, given a name (for error messages) and a quantity of the resource that exists. ] Shake will ensure that actions using the same finite resource do not execute in parallel. Z As an example, only one set of calls to the Excel API can occur at one time, therefore < Excel is a finite resource of quantity 1. You can write:     9{: =2} $ do  8 ["a.xls","b.xls"]  excel <-  "Excel" 1  "*.xls" 5 \out ->   excel 1 $   "excel" out ... Now the two calls to excel will not happen in parallel. ^As another example, calls to compilers are usually CPU bound but calls to linkers are usually b disk bound. Running 8 linkers will often cause an 8 CPU system to grid to a halt. We can limit  ourselves to 4 linkers with:   disk <-  "Disk" 4  8 [show i % "exe" | i < - [1..100]]  "*.exe" 5 \out ->   disk 1 $   "ld -o" [out] ...  "*.o" 5 \out ->   "cl -o" [out] ... |^Create a throttled resource, given a name (for error messages) and a number of resources (the @) that can be  used per time period (the >O in seconds). Shake will ensure that actions using the same throttled resource m do not exceed the limits. As an example, let us assume that making more than 1 request every 5 seconds to A Google results in our client being blacklisted, we can write:    google <-  "Google" 1 5  "*.url" 5 \ out -> do   google 1 $   "wget" ["http:// google.com?q=" ++ ; out] "-O" [out] yNow we will wait at least 5 seconds after querying Google before performing another query. If Google change the rules to 3 allow 12 requests per minute we can instead use  "Google" 12 60, which would allow l greater parallelisation, and avoid throttling entirely if only a small number of requests are necessary. eIn the original example we never make a fresh request until 5 seconds after the previous request has  completed. If we instead 8 want to throttle requests since the previous request started we can write:    google <-  "Google" 1 5  "*.url" 5 \ out -> do   google 1 $ return ()   "wget" ["http:// google.com?q=" ++ ; out] "-O" [out] =However, the rule may not continue running immediately after  completes, so while n we will never exceed an average of 1 request every 5 seconds, we may end up running an unbounded number of ] requests simultaneously. If this limitation causes a problem in practice it can be fixed. }IRun an action which uses part of a finite resource. For more details see . % You cannot depend on a rule (e.g. need) while a resource is held. ~^Run an action which uses part of several finite resources. Acquires the resources in a stable [ order, to prevent deadlock. If all rules requiring more than one resource acquire those # resources with a single call to ~, resources will not deadlock.  A version of 3 that runs in IO, and can be called before calling .  Most people should use  instead. fGiven an action on a key, produce a cached version that will execute the action at most once per key. ` Using the cached result will still result include any dependencies that the action requires.  Each call to D creates a separate cache that is independent of all other calls to . LThis function is useful when creating files that store intermediate values, o to avoid the overhead of repeatedly reading from disk, particularly if the file requires expensive parsing.  As an example:    digits <-  $ \ file -> do  src < - readFile' file * return $ length $ filter isDigit src  "*.digits" 5 \x -> do  v1 < - digits ( dropExtension x)  v2 < - digits ( dropExtension x)  < x $ show (v1,v2) To create the result MyFile.txt.digits the file  MyFile.txt, will be read and counted, but only at most  once per execution. \Run an action without counting to the thread limit, typically used for actions that execute T on remote machines using barely any local CPU resources. Unsafe as it allows the A limit to be exceeded. % You cannot depend on a rule (e.g. need') while the extra thread is executing. " If the rule blocks (e.g. calls }:) then the extra thread may be used by some other action. $ Only really suitable for calling 'cmd'/'command'. _a      !"#$%&'(b)*+cdef,-./01ghijk234567lm89:;<n=opq>rstuvwx?yz{|@}~AB'abcdef.ghijklm<nopqrstuvwxyz{|}~<a        !"#$%&'(b)*+cdef,-./01ghijk234567lm89:;<n=opq>rstuvwx?yz{|@}~AB=None CMThis function is not actually exported, but Haddock is buggy. Please ignore. Returns ? if the file exists. The existence of the file is tracked as a _ dependency, and if the file is created or deleted the rule will rerun in subsequent builds. You should not call 4 on files which can be created by the build system. Returns I if the directory exists. The existence of the directory is tracked as a c dependency, and if the directory is created or delete the rule will rerun in subsequent builds. You should not call : on directories which can be created by the build system. Return + the value of the environment variable, or  H if the variable is not set. The environment variable is tracked as a K dependency, and if it changes the rule will rerun in subsequent builds. IReturn the value of the environment variable, or the default value if it  not set. Similar to . QGet the contents of a directory. The result will be sorted, and will not contain  the entries . or ..M (unlike the standard Haskell version). The resulting paths will be relative 5 to the first argument. The result is tracked as a K dependency, and if it changes the rule will rerun in subsequent builds. %It is usually simpler to call either  or . NGet the files anywhere under a directory that match any of a set of patterns. . For the interpretation of the patterns see . All results will be  relative to the & argument. The result is tracked as a K dependency, and if it changes the rule will rerun in subsequent builds.  Some examples:  ( getDirectoryFiles "Config" ["//*.xml"] ; -- All .xml files anywhere under the Config directory D -- If Config/foo/bar.xml exists it will return ["foo/bar.xml"] . getDirectoryFiles "Modules" ["*.hs","*.lhs"] 1 -- All .hs or .lhs in the Modules directory Y -- If Modules/foo.hs and Modules/foo.lhs exist, it will return ["foo.hs","foo.lhs"] ?If you require a qualified file name it is often easier to use "" as  argument, = for example the following two expressions are equivalent: D fmap (map ("Config" </>)) (getDirectoryFiles "Config" ["//*.xml"]) ( getDirectoryFiles "" ["Config//*.xml"] 2Get the directories in a directory, not including . or ... V All directories are relative to the argument directory. The result is tracked as a K dependency, and if it changes the rule will rerun in subsequent builds.  getDirectoryDirs "/Users" 6 -- Return all directories in the /Users directory % -- e.g. ["Emily","Henry","Neil"] TRemove all files and directories that match any of the patterns within a directory.  Some examples:     "output" ["//*"]   "." ["//*.hi","//*.o"] dAny directories that become empty after deleting items from within them will themselves be deleted, 3 up to (and including) the containing directory. 0 This function is often useful when writing a clean action for your build system,  often as a phony rule. Remove files, like 7, but executed after the build completes successfully.  Useful for implementing clean= actions that delete files Shake may have open for building. 1DEFGHIJKLMNOPQRSTUVWCXYZ[\]^_`abcdefghij C%DEFJHGKKIKLMNOPQRSTUVWCXYZ[\]^_`abcdefghij>None kMThis function is not actually exported, but Haddock is buggy. Please ignore. SAdd a dependency on the file arguments, ensuring they are built before continuing. \ The file arguments may be built in parallel, in any order. This function is particularly  necessary when calling  or .. As an example:    "//*.rot13"  \ out -> do  let src = ? out   [src]   "rot13" [src] "-o" [out] Usually  need [foo,bar] is preferable to  need [foo] >> need [bar] as the former allows greater * parallelism, while the latter requires foo- to finish building before starting to build bar. Like  , but if F/ is set, check that the file does not rebuild. S Used for adding dependencies on files that have already been used in this rule. ;Track that a file was read by the action preceeding it. If F is activated @ then these files must be dependencies of this rule. Calls to  are  automatically inserted in Z mode. >Track that a file was written by the action preceeding it. If F is activated f then these files must either be the target of this rule, or never referred to by the build system.  Calls to  are automatically inserted in Z mode. 2Allow accessing a file in this rule, ignoring any 'trackRead'\/'trackWrite' calls matching  the pattern. TRequire that the argument files are built by the rules, used to specify the target.    main =  ` $ do   ["Main.exe"]  ... This program will build Main.exe/, given sufficient rules. All arguments to all  calls + may be built in parallel, in any order. %This function is defined in terms of j and , use j if you need more complex  targets than  allows. TDeclare a phony action -- an action that does not produce a file, and will be rerun 7 in every execution that requires it. You can demand  rules using  / . J Phony actions are never executed more than once in a single build run. HPhony actions are intended to define command-line abbreviations. If you  a phony action e in a rule then every execution where that rule is required will rerun both the rule and the phony  action. Infix operator alias for &, for sake of consistency with normal  rules. <Define a rule to build files. If the first argument returns  for a given file, 9 the second argument will be used to build it. Usually  is sufficient, but  gives X additional power. For any file used by the build system, only one rule should return . N This function will create the directory for the result file, if necessary.   (all isUpper . ;)  \ out -> do  let src = @& out $ map toLower $ takeBaseName out  < out . map toUpper =<< A src aDefine a set of patterns, and if any of them match, run the associated rule. Defined in terms of .  Think of it as the OR (||) equivalent of . Define a rule that matches a , see  for the pattern rules. Z Patterns with no wildcards have higher priority than those with wildcards, and no file W required by the system may be matched by more than one pattern at the same priority  (see h and i to modify this behaviour). N This function will create the directory for the result file, if necessary.    "*.asm.o"  \ out -> do  let src = ? out   [src]   "as" [src] "-o" [out] MTo define a build system for multiple compiled languages, we recommend using .asm.o,  .cpp.o, .hs.o6, to indicate which language produces an object file.  I.e., the file foo.cpp produces object file  foo.cpp.o. 7Note that matching is case-sensitive, even on Windows. lmnopqkrstuvwxyz{lnopkrslmnopqkrstuvwxyz{BNone  Deprecated: Please use command or cmd instead. 6 This function will be removed in a future version. ZExecute a system command. This function will raise an error if the exit code is non-zero.  Before running  make sure you  any required files.  Deprecated: Please use command or cmd instead, with Cwd. 6 This function will be removed in a future version. VExecute a system command with a specified current working directory (first argument). C This function will raise an error if the exit code is non-zero.  Before running  make sure you  any required files.    "/usr/ MyDirectory" "pwd" []  Deprecated: Please use command or cmd instead, with Stdout or Stderr. 6 This function will be removed in a future version. $Execute a system command, returning (stdout,stderr). C This function will raise an error if the exit code is non-zero.  Before running  make sure you  any required files. copyFile' old new copies the existing file from old to new.  The old' file will be tracked as a dependency. copyFile' old new copies the existing file from old to new , if the contents have changed.  The old' file will be tracked as a dependency. Read a file, after calling 5. The argument file will be tracked as a dependency. Write a file, lifted to the a monad.  A version of * which also splits the result into lines. 6 The argument file will be tracked as a dependency.  A version of # which writes out a list of lines. 5Write a file, but only if the contents would change. MCreate a temporary file in the temporary directory. The file will be deleted E after the action completes (provided the file is not still open).  The L will not have any file extension, will exist, and will be zero bytes long. 3 If you require a file with a specific name, use . DCreate a temporary directory inside the system temporary directory. = The directory will be deleted after the action completes. |  |NoneHA class for specifying what results you want to collect from a process.  Values are formed of , ,  and tuples of those.  Collect the } of the process. , If you do not collect the exit code, any ~ will cause an exception.  Collect the stderr of the process.  If you are collecting the stderr<, it will not be echoed to the terminal, unless you include .  Collect the stdout of the process.  If you are collecting the stdout<, it will not be echoed to the terminal, unless you include . Options passed to  or ( to control how processes are executed. Should I echo the stderr? Defaults to  unless a  result is required. Should I echo the stdout? Defaults to  unless a  result is required. Should I include the stderr4 in the exception if the command fails? Defaults to . Name to use with q, or ""E for no tracing. By default traces using the name of the executable.  Treat the stdin/stdout/stderr; messages as binary. By default streams use text encoding. Pass the command to the shell without escaping - any arguments will be joined with spaces. By default arguments are escaped properly.  Given as the stdin( of the spawned process. By default the stdin is inherited. eChange the environment variables in the spawned process. By default uses this processes environment.  Use  to modify the $PATH variable, or  to modify other variables. gChange the current directory in the spawned process. By default uses this processes current directory.  Produce a  of value ) that is the current environment, plus a  prefix and suffix to the $PATH$ environment variable. For example:    opt <-  ["/usr/special"] []   opt "userbinary --version" Would prepend /usr/special to the current $PATH, and the command would pick  /usr/special/ userbinary+, if it exists. To add other variables see .  Produce a  of value 4 that is the current environment, plus the argument ' environment variables. For example:    opt <-  [("CFLAGS","-O2")]   opt " gcc -c main.c" #Would add the environment variable $CFLAGS with value -O2. If the variable $CFLAGS F was already defined it would be overwritten. If you wish to modify $PATH see . (Given a directory (as passed to tracker /if) report on which files were used for readingwriting _If the user specifies a custom $PATH, and not Shell, then try and resolve their exe ourselves. & Tricky, because on Windows it doesn't look in the $PATH first. )Execute a system command. Before running  make sure you  any files ! that are used by the command. 2This function takes a list of options (often just [], see  for the available Q options), the name of the executable (either a full name, or a program on the $PATH) and , a list of arguments. The result is often ()%, but can be a tuple containg any of ,   and . Some examples:     [] "gcc" ["-c","myfile.c"]N -- compile a file, throwing an exception on failure   c <-  [] "gcc" ["-c",myfile]? -- run a command, recording the exit code  ( c,  err) <-  [] "gcc" ["-c","myfile.c"]> -- run a command, recording the exit code and error output   out <-  [] "gcc" ["-MM","myfile.c"]3 -- run a command, recording the output   [ " generated"] "gcc" ["-c",myfile]/ -- run a command in a directory Unless you retrieve the } using , any ~ will throw an error, including  the . in the exception message. If you capture the  or 1, that stream will not be echoed to the console,  unless you use the option  or .  If you use  inside a doO block and do not use the result, you may get a compile-time error about being  unable to deduce . To avoid this error, use .  A version of O where you do not require any results, used to avoid errors about being unable  to deduce . )Execute a system command. Before running  make sure you  any files ! that are used by the command.  String: arguments are treated as whitespace separated arguments.  [String]- arguments are treated as literal arguments.   arguments are used as options. To take the examples from :    () <-  "gcc -c myfile.c"V -- compile a file, throwing an exception on failure   c <-  "gcc -c" [myfile]H -- run a command, recording the exit code  ( c,  err) <-  "gcc -c myfile.c"K -- run a command, recording the exit code and error output   out <-  "gcc -MM myfile.c"@ -- run a command, recording the output   ( " generated") "gcc -c" [myfile] :: a, () -- run a command in a directory #When passing file arguments we use [myfile] so that if the myfile5 variable contains spaces they are properly escaped.  If you use  inside a doO block and do not use the result, you may get a compile-time error about being  unable to deduce *. To avoid this error, bind the result to (), or include a type signature. The  command can also be run in the D monad, but then . is ignored and command lines are not echoed. <' CNoneRequire the user to press y before continuing. Replace exceptions with . 8Require a condition to be true, or exit with a message. DNone<Define a rule for building multiple files at the same time.  Think of it as the AND (&&) equivalent of . ; As an example, a single invocation of GHC produces both .hi and .o files:    ["*.o","*.hi"]  \[o,hi] -> do  let hs = o  "hs"  ! ... -- all files the .hs import   "ghc -c" [hs] However, in practice, it'&s usually easier to define rules with  and make the .hi depend  on the .o9. When defining rules that build multiple files, all the  values must  have the same sequence of // and * wildcards in the same order. M This function will create directories for the result files, if necessary.  Think of it as the OR (||) equivalent of . LDefine a rule for building multiple files at the same time, a more powerful ! and more dangerous version of . Think of it as the AND (&&) equivalent of . Given an application test &?> ..., test should return Just! if the rule applies, and should = return the list of files that will be produced. This list must3 include the file passed as an argument and should  obey the invariant:  U forAll $ \x ys -> test x == Just ys ==> x `elem` ys && all ((== Just ys) . test) ys 7As an example of a function satisfying the invariaint:    test x |  x `elem` [".hi",".o"]  = Just [ x  "hi",  x  "o"] test _ = Nothing Regardless of whether Foo.hi or Foo.o( is passed, the function always returns [Foo.hi, Foo.o]. ENone1Add extra information which rules can depend on. 0 An oracle is a function from a question type q, to an answer type a. ` As an example, we can define an oracle allowing you to depend on the current version of GHC:   W newtype GhcVersion = GhcVersion () deriving (Show,Typeable,Eq,Hashable,Binary,NFData)  rules = do   $ \(GhcVersion _) -> fmap F $  "ghc --numeric-version"  ... rules ... If a rule calls  (GhcVersion ())<, that rule will be rerun whenever the GHC version changes.  Some notes:  We define  GhcVersion with a newtype around (), allowing the use of GeneralizedNewtypeDeriving. 4 All the necessary type classes are exported from Development.Shake.Classes.  Each call to ( must use a different type of question.  Actions passed to / will be run in every build they are required, \ but if their value does not change they will not invalidate any rules depending on them. > To get a similar behaviour using data stored in files, see G.  If the value returned by  is ignored then ) may help avoid ambiguous type messages. $ Alternatively, use the result of  , which is ! restricted to the correct type. GAs a more complex example, consider tracking Haskell package versions:   Vnewtype GhcPkgList = GhcPkgList () deriving (Show,Typeable,Eq,Hashable,Binary,NFData) `newtype GhcPkgVersion = GhcPkgVersion String deriving (Show,Typeable,Eq,Hashable,Binary,NFData)   rules = do  getPkgList <-  $ \GhcPkgList{} -> do  Stdout out <-  "ghc-pkg list --simple-output" + return [(reverse b, reverse a) | x <%- words out, let (a,_:b) = break (== '-' ) $ reverse x]  --  getPkgVersion <-  $ \(GhcPkgVersion pkg) -> do  pkgs <- getPkgList $ GhcPkgList () ! return $ lookup pkg pkgs  --  "myrule" %> \_ -> do & getPkgVersion $ GhcPkgVersion "shake" - ... rule using the shake version ... >Using these definitions, any rule depending on the version of shake  should call getPkgVersion $ GhcPkgVersion "shake" to rebuild when shake is upgraded. &Get information previously added with . The question/'answer types must match those provided  to . &Get information previously added with +. The second argument is not used, but can M be useful to fix the answer type, avoiding ambiguous type error messages. HNoneHDefine order-only dependencies, these are dependencies that will always - be built before continuing, but which aren't dependencies of this action. [ Mostly useful for defining generated dependencies you think might be real dependencies. _ If they turn out to be real dependencies, you should add an explicit dependency afterwards.    "source.o" %> \ out -> do   ["header.h"]  () <- cmd "-gcc -c source.c -o source.o -MMD -MF source.m"  neededMakefileDependencies "source.m" If header.h is included by source.c then the call to needMakefileDependencies will cause 1 it to be added as a real dependency. If it isn't, then the rule won't rebuild if it changes, < and you will have lost some opportunity for parallelism. INoneIAlways rerun the associated action. Useful for defining rules that query ! the environment. For example:   "ghcVersion.txt" 5 \ out -> do    J stdout <-  "ghc --numeric-version"  K out stdout  LNone[Main entry point for running Shake build systems. For an example see the top of the module Development.Shake.  Use >% to specify how the system runs, and b3 to specify what to build. The function will throw $ an exception if the build fails. $To use command line flags to modify > see M. NNoneCRun a build system using command line arguments for configuration. & The available flags are those from , along with a few additional  make. compatible flags that are not represented in > , such as --print-directory. + If there are no file arguments then the b1 are used directly, otherwise the file arguments  are ed (after calling k). As an example:    main =  `{@ = "_make/", Q = -} $ do   "clean" $ O "_make" ["//*"]   ["_make/neil.txt","_make/ emily.txt"]  "_make/*.txt"  \out -> # ... build action here ... +This build system will default to building neil.txt and  emily.txt#, while showing progress messages, 4 and putting the Shake files in locations such as _make/ .database#. Some example command line flags:  main --no-progress" will turn off progress messages.  main -j6 will build on 6 threads.   main --help) will display a list of supported flags.   main clean. will not build anything, but will remove the _make directory, including the  any @.   main _make/ henry.txt will not build neil.txt or  emily.txt, but will instead build  henry.txt.  A version of 8 with more flexible handling of command line arguments.  The caller of I can add additional flags (the second argument) and chose how to convert  the flags/2arguments into rules (the third argument). Given:     opts flags (\ flagValues argValues -> result)  opts is the initial >D value, which may have some fields overriden by command line flags.  This argument is usually `', perhaps with a few fields overriden.  flags8 is a list of flag descriptions, which either produce a F containing an error > message (typically for flags with invalid arguments, .e.g. G "could not parse as int"), or a value  that is passed as  flagValues$. If you have no custom flags, pass [].   flagValues6 is a list of custom flags that the user supplied. If  flags == [] then this list will  be [].   argValuesQ is a list of non-flag arguments, which are often treated as files and passed to .  result should produce a 8 to indicate that no building needs to take place, or a  , providing the rules that should be used. 4As an example of a build system that can use either gcc or distcc for compiling:   import System.Console.GetOpt   data Flags = DistCC deriving Eq flags = [Option "" ["distcc"] (NoArg $ Right DistCC) "Run distributed."]  main =  ` flags $ \$flags targets -> return $ Just $ do  if null targets then  [" result.exe"] else  targets  let compiler = if DistCC `elem` flags then "distcc" else "gcc"  "*.o"  \ out -> do   ...  cmd compiler ...  ... Now you can pass --distcc to use the distcc compiler. :A list of command line options that can be used to modify >. Each option returns a either an error message (invalid argument to the flag) or a function that changes some fields  in >. The command line flags are make+ compatible where possbile, but additional ? flags have been added for the extra options Shake supports. 2True if it has a potential effect on ShakeOptions  None>A deprecated way of defining a low priority rule. Defined as:   defaultRule = h 0 . g 3456cdefgnoxyzfcde3654gnoxyzNone Deprecated: Alias for .  Deprecated: Alias for .  Deprecated: Alias for .  Deprecated: Alias for  . Note that *>. clashes with a Prelude operator in GHC 7.10.  Deprecated: Alias for .  Deprecated: Alias for .   !"#$%&'()*+,-./012789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abhijklmpqrstuvw{|}~ͦ`bjkihaq lm./012>?@ABCDEFGHIJKLMNOPQR\_^]Y[ZSXWVUTp !"#$%&'()-*+,7=<;:98urstvw{}~|NoneJRead a config file, returning a list of the variables and their bindings. . Config files use the Ninja lexical syntax:   :http://martine.github.io/ninja/manual.html#_lexical_syntax fRead a config file with an initial environment, returning a list of the variables and their bindings. . Config files use the Ninja lexical syntax:   :http://martine.github.io/ninja/manual.html#_lexical_syntax Specify the file to use with . Specify the values to use with , generally prefer  + unless you also need access to the values  of variables outside a. 6Obtain the value of a configuration variable, returns  to indicate the variable * has no binding. Any build system using  must call either   or . The ; function will introduce a dependency on the configuration w variable (but not the whole configuration file), and if the configuration variable changes, the rule will be rerun.  As an example:    "myconfiguration.cfg"  "*.o"  \ out -> do  cflags <-  "CFLAGS"   "gcc" [out -<.> "c"] (fromMaybe "" cflags) Obtain the configuration keys.  Any build system using  must call either  or .  The @ function will introduce a dependency on the configuration keys i (but not the whole configuration file), and if the configuration keys change, the rule will be rerun. % Usually use as part of an action.  As an example:    "myconfiguration.cfg"  j $ need =<< getConfigKeys  NoneVGiven the text of a Makefile, extract the list of targets and dependencies. Assumes a = small subset of Makefile syntax, mostly that generated by gcc -MM. @ parseMakefile "a: b c\nd : e" == [("a",["b","c"]),("d",["e"])] YDepend on the dependencies listed in a Makefile. Does not depend on the Makefile itself. a needMakefileDependencies file = need . concatMap snd . parseMakefile =<< liftIO (readFile file) YDepend on the dependencies listed in a Makefile. Does not depend on the Makefile itself. / Use this function to indicate that you have already used the files in question. e neededMakefileDependencies file = needed . concatMap snd . parseMakefile =<< liftIO (readFile file) Like S, but instead of accumulating a list of flags, apply functions to a default value. d Usually used to populate a record structure. As an example of a build system that can use either gcc or distcc for compiling:   import System.Console.GetOpt  0data Flags = Flags {distCC :: Bool} deriving Eq flags = [Option "" ["distcc"] (NoArg $ Right $ \x -> x{distCC=True}) "Run distributed."]  main =  ` flags (Flags False) $ \$flags targets -> return $ Just $ do  if null targets then  [" result.exe"] else  targets ) let compiler = if distCC flags then "distcc" else "gcc"  "*.o"  \ out -> do   ...   compiler ...  ... Now you can pass --distcc to use the distcc compiler. PQRPQSTUVTWXTUYTUZTU[TW\PQ]^_`^_abcdefgefhefijkljkmjknopqrstuvwx$y$z$'({({(|(}(~((((((((((*****---------------:----------------)---------------944464144444404444444/4444444444444444=7========O>>>>>>8>>>>>5BBBBBBAB<BBBKBBJJF.DDEEEHIGLNMNN                   ! " # $P%&T'(T')T'*T'+e,-e./ef0ef1ef2e,3e45e67e68e69e6:e6;e6< = > ?P%@P%AP%B ? C C D E F F G H I J KTLMTNOTLPPQRTSTTSUTSVTWXTYZTY[TL\TL]TL^T_`T_aTbcTdeTdfTdgTdhPQiT_jTLkTLlTLmTLnTLoTbpTbqTbrTbsTdtTduTvwTbxTbyTLzTL{T_|PQ}T~TbTvTbTP%P%P%P%P%TbP%TTLTTP%P%P%TWTTTTTTWTWTWTWTWTWTWTWTWTWTWTTTTTTTTTTTTTTTTTT~T~T~T~TTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTvTTTTbTbTbTbTbTbTbTbTbTbTbTbTbTbTbTbTbTbTbTNTdTdTdTdTdTdTTTTTTUTUTU TU TU TS TS TSTSTSTSTSTSTSTSTSTSTSTSTSTSTSTSTSTSTS TS!TS"TS#TS$TS%TS&TS'TS(TS)TS*TS+TS,TS-TS.TS/TS0TS1T23T24T25T26TY7TY8T_9T_:T_;T_<T_=TL>TL?TL@TLATLBTLCPQDPQEPQFPQGPQHPQIPQJPQKPQL M N O P Q R R S C C T U V W X Y Z [ \ ] ^ _ ` abbcdefghijklmnopqrstCCuvwxyzz{|}~~o66C     & !"#$%@;&'()*+,-./0123456789:;<?%=> ?T@ A B C D!E!F!E!F!G!H!I!J!K!L!M!N!O!P!Q!R"S"S"T"T"U"V"W""c"X"Y#Z#[#\#]#^#_#`#a#a#b#c#d#e#f#g#h#i#j#k#l#m#n$o$p$q$r$s$t$u$v$w$x$y$z${$|$}$~$$$$$$$$$$$$(((((((((((((((((((((((((((((((((**************+++++++++++++++++++++++++++,,-T-----------2222222333333333333333333333333333333333333p3333333333333333333333 3 3 3 3 33333333333333334444 4 4!4"4#4$4%4&4'4(4)4)4*4+4,4-4.4/40414243444545444464747484449494:4;4<4=4>4?4@4A4B4C4D4E4F4G4H4I4J4K4L4M4N4O4P=Q=R=R=S=T=U=V=W=X=Y=Y=Z=Z=[=[=\=\=]=]=^=^=_=`=a=b=c=d=e=f=g=h=i=j=k=l=m=n=o=p=q>r>s>s>t>t>u>v>w>x>y>z>{>|>}>~>>BTTCCCCCDDDDDDDDEEEEEHHHHHHHHHIIIIIIIIINNNNNNNNNNNNNNNNNNNNN shake-0.14.2Development.Shake.ClassesDevelopment.ShakeDevelopment.Shake.FilePathDevelopment.Shake.RuleDevelopment.Shake.CommandDevelopment.Shake.ConfigDevelopment.Shake.UtilGeneral.TemplateGeneral.BinaryGeneral.CleanupGeneral.ConcurrentGeneral.PreludeDevelopment.Shake.MonadGeneral.BilistGeneral.TimingDevelopment.Shake.PoolDevelopment.Shake.Resource newResource newThrottle withResourcecmdneed withResourcesshake Paths_shakeDevelopment.Shake.ProfileDevelopment.Shake.ByteStringDevelopment.Ninja.EnvDevelopment.Ninja.TypeDevelopment.Ninja.LexerDevelopment.Ninja.Parse General.ExtraGeneral.StringGeneral.InternDevelopment.Shake.FileInfoDevelopment.Shake.FilePattern<.>Development.Shake.Progress shakeProgressDevelopment.Shake.ErrorsDevelopment.Shake.ValueDevelopment.Shake.SpecialDevelopment.Shake.Typescommandtracedaction storedValueDevelopment.Shake.StorageDevelopment.Shake.DatabaseDevelopment.Shake.Core%>Rule doesFileExistwant shakeOptions shakeThreads takeBaseName writeFile'!Development.Shake.Rules.DirectoryDevelopment.Shake.Rules.File dropExtensionreplaceBaseName readFile'Development.Shake.DerivedDevelopment.Shake.DemoDevelopment.Shake.Rules.FilesDevelopment.Shake.Rules.Oracle fromStdout alwaysRerun!Development.Shake.Rules.OrderOnlyDevelopment.Shake.Rules.RerunStdoutwriteFileChangedDevelopment.Shake.Shake shakeArgsDevelopment.Shake.ArgsremoveFilesAfterghc-prim GHC.Classes==EqbaseGHC.ShowShowData.Typeable.InternalTypeableshowListshow showsPrectypeOf/=deepseq-1.3.0.1Control.DeepSeqrnfNFDatatransformers-0.4.1.0Control.Monad.IO.ClassliftIObinary-0.7.1.0Data.Binary.ClassputgetBinaryhashable-1.2.1.0Data.Hashable.ClasshashHashable hashWithSaltResource newResourceIO newThrottleIOdropDirectory1takeDirectory1 normaliseExtoNative toStandard-<.>exe FilePattern?==Progress isFailure countSkipped countBuilt countUnknown countTodo timeSkipped timeBuilt timeUnknowntimeTodoprogressDisplayprogressTitlebarprogressProgramprogressSimpleShakeExceptionshakeExceptionTargetshakeExceptionStackshakeExceptionInner EqualCostNotEqualEqualExpensive EqualCheap Verbosity DiagnosticChattyLoudNormalQuietSilent ShakeOptions shakeFiles shakeVersionshakeVerbosity shakeStaunch shakeReport shakeLint shakeFlush shakeAssumeshakeAbbreviationsshakeStorageLogshakeLineBuffering shakeTimingsshakeRunCommands shakeChangeshakeCreationCheckshakeLiveFiles shakeOutputChangeChangeModtimeOrDigestChangeModtimeAndDigestInputChangeModtimeAndDigest ChangeDigest ChangeModtimeLint LintTracker LintBasicAssume AssumeSkip AssumeClean AssumeDirtyActionRules equalValue ShakeValuerulepriority alternativeswithoutActionsactionOnException actionFinallyapplyapply1getShakeOptionsputLoud putNormalputQuiet getVerbosity withVerbosityquietlytrackUse trackChange trackAllow newCacheIOnewCacheunsafeExtraThreaddoesDirectoryExistgetEnvgetEnvWithDefaultgetDirectoryContentsgetDirectoryFilesgetDirectoryDirs removeFilesneeded trackRead trackWritephony~>?>|%>system' systemCwd systemOutput copyFile'copyFileChanged readFileLineswriteFileLines withTempFile withTempDir CmdArguments CmdResultExitfromExitStderr fromStderr CmdOption EchoStderr EchoStdout WithStderrTraced BinaryPipesShellStdinEnvCwdaddPathaddEnvcommand_&%>&?> addOracle askOracle askOracleWith orderOnly shakeArgsWithshakeOptDescrs defaultRule**>?>>*>>*>|*>&*>readConfigFilereadConfigFileWithEnvusingConfigFile usingConfig getConfig getConfigKeys parseMakefileneedMakefileDependenciesneededMakefileDependenciesshakeArgsAccumulate runTemplate librarieslbs_stripPrefixBinFloat fromBinFloatBinList fromBinList BinaryWithputWithgetWithconvert$fBinaryBinFloat$fShowBinFloat$fBinaryBinList $fShowBinList$fBinaryWithctxMaybe$fBinaryWithctx[]$fBinaryWithctx(,) GHC.TypesWordGHC.WordWord8Word16Word32Word64Data.Binary.PutPutData.Binary.Get.InternalGetgputggetGBinaryputWord8Data.Binary.GetgetWord8 Data.Binary encodeFileencode decodeOrFaildecodeFileOrFail decodeFiledecode withCleanup addCleanupCleanupBoolTrueFalseSuniqueitemsFencenewFence signalFence waitFence testFence $fShowFenceGHC.Base++GHC.ErrerrorfoldrGHC.PrimseqGHC.Listconcatfilterzip System.IOprint Data.Tuplefstsnd otherwisemap$GHC.Num fromInteger-GHC.Real fromRationalGHC.EnumenumFrom enumFromThen enumFromToenumFromThenTo>=negatefail>>=>>fmapreturn fromIntegral realToFrac toInteger toRationalBoundedEnum GHC.FloatFloating FractionalIntegralMonadFunctorNumOrdGHC.ReadReadReal RealFloatRealFracControl.Applicative ApplicativeCharDoubleFloatInt integer-gmpGHC.Integer.TypeIntegerOrderingRationalIO Data.EitherEitherStringLeftRightLTEQGTgetLine<*<*>purePrelude$!readIOreadLn appendFile writeFilereadFileinteract getContentsgetCharputStrLnputStrputCharGHC.IO.ExceptionioError Data.MonoidmconcatmappendmemptyMonoid Text.Readreadreadseither Data.Listunwordswordsunlineslinesproductsumfoldl1minimummaximumlex readParenreadList readsPrecText.ParserCombinators.ReadPReadSacoshatanhasinhcoshtanhsinhacosatanasincostansinlogBase**logsqrtexppiatan2isIEEEisNegativeZeroisDenormalized isInfiniteisNaN scaleFloat significandexponent encodeFloat decodeFloat floatRange floatDigits floatRadixGHC.IOFilePath userErrorIOErrorlcmgcd^^^oddevendivModquotRemmoddivremquotrecip/floorceilingroundtruncateproperFraction undefinedmaxBoundminBoundfromEnumtoEnumpredsucc Control.MonadmapM_mapM sequence_sequence=<< showParen showStringshowCharshowsShowSunzip3unzipzipWith3zipWithzip3!! concatMaplookupnotElemelemallanyorandreversebreakspansplitAtdroptake dropWhile takeWhilecycle replicaterepeatiteratescanr1scanrfoldr1scanl1scanlfoldllengthnullinitlasttailhead Data.MaybemaybeNothingJustMaybeuncurrycurrysubtractsignumabs*+asTypeOfuntilflip.constidcompare<=&&||not<>maxminrunRAWputRW unmodifyRW captureRAWCaptureRAWfromRAWhandlerrorwwgetROgetRWgetsROgetsRWwithRAWmodifyRWwithROwithRWcatchRAWtryRAWthrowRAWBilisttoListisEmptyconssnocuncons$fMonoidBilist $fEqBilist printTimingstimings resetTimings addTiming showTimingsshowGapstepaddPooladdPoolPriority increasePoolrunPoolthreads threadsLimit threadsMax threadsSumtodoPoolTreeBranchLeafQueueNonDetnonDetnewQueueenqueuePriorityenqueuedequeue insertTree removeTreeemptySThrottleWaitingThrottleAvailablefiniteAvailable finiteWaiting resourceOrd resourceShowacquireResourcereleaseResourceThrottleFinite resourceIds resourceIdwaiter blockPool $fOrdResource $fEqResource$fShowResourcecatchIOversionbindirlibdirdatadir libexecdir sysconfdir getBinDir getLibDir getDataDir getLibexecDir getSysconfDirgetDataFileName writeProfile ProfileTrace prfCommandprfStartprfStop ProfileEntryprfNameprfBuilt prfChanged prfDepends prfExecution prfTracesprfTimegenerateSummary generateHTML generateTrace generateJSON jsonListLinesjsonList jsonObjectlinesCR endsSlash wordsMakefilefilepathNormalisedotDotdotslashnewEnvscopeEnvaskEnvfromEnv $fShowEnvruleBindBuildruleNameenv depsNormal depsImplicit depsOrderOnly buildBindNinjarulessingles multiplesphonysdefaultspoolsExprVarLitExprsFileStrStraskExpraskVaraddBindaddBindsnewNinjaLexeme LexDefine LexDefaultLexPoolLexRule LexSubninja LexIncludeLexBuildLexBindStr0chrinc dropWhile0span0break0break00head0tail0list0take0isVarisVarDot endsDollardropN dropSpace lexerFilelexer lexerLooplexBindlexBuild lexDefaultlexRulelexPool lexInclude lexSubninja lexDefinelexxBindlexxFilelexxName lexxExprslexxExpr splitLineCont splitLineCRparse parseFile withBinds applyStmt splitDepsgetDepthfilepath-1.3.0.1System.FilePath.WindowspathSeparatorsSystem.FilePath.PosixreplaceExtension makeRelative isAbsolute isRelative makeValidisValid normalise equalFilePathjoinPathsplitDirectories splitPathcombinereplaceDirectory takeDirectorydropTrailingPathSeparatoraddTrailingPathSeparatorhasTrailingPathSeparator takeFileName dropFileNamereplaceFileName splitFileNameisDrivehasDrive dropDrive takeDrive joinDrive splitDrive getSearchPathsplitSearchPathisExtSeparator extSeparatorisSearchPathSeparatorsearchPathSeparatorisPathSeparator pathSeparatortakeExtensionsdropExtensionssplitExtensions hasExtension addExtension takeExtensionsplitExtensionfastNubnubgetNumberOfProcessors showQuotegetProcessorCount randomElemBSUBSpackunpackpack_unpack_packUunpackUunpackU_packU_requireU $fNFDataBSU $fNFDataBS$fShowBSIdInternemptyinsertaddfromList$fBinaryWithwIdWIN32_FILE_ATTRIBUTE_DATAFileSize FileInfoSizeModTime FileInfoModFileHash FileInfoHashFileInfoc_getFileAttributesExWc_getFileAttributesExA fileInfoEq fileInfoNeq fileInfoValfileInfo getFileHash getFileInfo alloca_WIN32_FILE_ATTRIBUTE_DATApeekLastWriteTimeLowpeekFileSizeLow $fEqFileInfo$fShowFileInfomatch directories1 directoriessimple compatibleextract substituteSStringRegexEmptyRepeatConcatOrBracketEndStartAnyNot SlashSlashStarisCharisDullfromCharpatternMealymessageprogressReplaywriteProgressReport ProgressEntry idealSecs idealPerc actualSecs actualPercrunMealyLPCSTRc_setConsoleTitle echoMealy scanMealyoldMealylatchiffdecay formatMessage showMinSecliftA2'indentxterm$fApplicativeMealy$fFunctorMealy$fMonoidProgresserrerrorStructured structurederrorNoRuleToBuildTypeerrorRuleTypeMismatcherrorIncompatibleRuleserrorMultipleRulesMatcherrorRuleRecursionerrorDuplicateOracle errorNoApplyspecialIsOracleKey$fShowShakeException$fExceptionShakeExceptionWitness typeNames witnessIn witnessOutValueKeynewKeynewValuetypeKey typeValuefromKey fromValuewitnessregisterWitness toStableListcurrentWitness$fBinaryWithWitnessValue$fBinaryWitness $fEqWitness $fEqValue$fHashableValue $fNFDataValue $fShowValue $fShowKeyspecialAlwaysRebuildsspecialIsFileKeyFunction Data.DataData fromFunctionfieldsShakeOptionstyShakeOptionsconShakeOptionsunhide tyFunction$fDataFunction$fShowFunction$fShowShakeOptions$fDataShakeOptionsasyncExceptionMapdatabaseVersion withStorage flushThread readChunkstoChunkstoredequalexecuteDatabasebuilddependencyOrder resultsOnlyStepKeyOpsDepends fromDependsWaitingPendingResultresultbuiltchangeddepends executiontracesStatusMissingLoadedErrorReadylockinternstatusjournal diagnosticassumeTraceStackStepincStep showStackaddStack showTopStacktopStack checkStack emptyStack statusTypeisError isWaitingisReady afterWaiting newWaiting runWaitingwaitFor getResultprogress removeSteptoReport checkValidlistLive listDependslookupDependenciesstepKey toStepResultfromStepResult withDatabase$fBinaryWithWitnessStatus $fBinaryTrace$fBinaryWithWitnessResult $fShowPending $fNFDataTracerun fromActionLocal localStacklocalVerbositylocalBlockApply localDepends localDiscount localTraceslocalTrackAllowslocalTrackUsedGlobalglobalDatabase globalPool globalCleanupglobalTimestamp globalRules globalOutput globalOptionsglobalDiagnostic globalLint globalAfterglobalTrackAbsentRuleInfo resultTypeSRulesactionsARuleruleKey ruleValuerulesIOnewRules modifyRulesgetRulesregisterWitnessescreateRuleinfo runStoredrunEqual runExecute actionBoom lineBuffering abbreviate wrapStack runActionrunAfter applyKeyValueputWhentrackCheckUsed blockApply $fMonoidRules$fMonoidSRulesdefaultRuleDirectory GetDirectoryA GetDirectoryQ GetDirDirs GetDirFilespatGetDirdirGetEnvAGetEnvQDoesDirectoryExistADoesDirectoryExistQDoesFileExistADoesFileExistQ getDirActioncontentsanswergetDir $fRuleGetDirectoryQGetDirectoryA$fRuleGetEnvQGetEnvA,$fRuleDoesDirectoryExistQDoesDirectoryExistA"$fRuleDoesFileExistQDoesFileExistA$fBinaryGetDirectoryQ$fHashableGetDirectoryQ$fNFDataGetDirectoryQ$fShowGetDirectoryA$fShowGetDirectoryQ $fShowGetEnvA $fShowGetEnvQ$fShowDoesDirectoryExistA$fShowDoesDirectoryExistQ$fShowDoesFileExistA$fShowDoesFileExistQdefaultRuleFileFileAFileQ fromFileQstoredValueErrorneedBSneededBS neededCheckroot$fRuleFileQFileA $fShowFileA $fBinaryFileA $fNFDataFileA$fHashableFileA $fShowFileQ checkExitCodeExitCode ExitFailure trackerFiles resolvePathArgarg cmdArguments:-> cmdResult ResultCode ResultStderr ResultStdoutcommandExplicit correctCasecommandExplicitIOfindExecutableWithforkWaitsaneCommandForUser cmdResultWith $fArgMaybe$fArg[]$fArgCmdOption $fArgMaybe0$fArg[]0$fArg[]1$fCmdArgumentsIO$fCmdArgumentsAction$fCmdArguments(->)$fCmdResult(,,)$fCmdResult(,) $fCmdResult()$fCmdResultStderr$fCmdResultStdout$fCmdResultExitCode$fCmdResultExityesNowraprequiredemoputLineFilesAFilesQ getFileTimes$fRuleFilesQFilesA $fShowFilesQ $fShowFilesAOracleAOracleQ$fRuleOracleQOracleA OrderOnlyA OrderOnlyQdefaultRuleOrderOnly orderOnlyBS$fRuleOrderOnlyQOrderOnlyA$fShowOrderOnlyA$fShowOrderOnlyQ AlwaysRerunA AlwaysRerunQdefaultRuleRerun$fRuleAlwaysRerunQAlwaysRerunA$fEqAlwaysRerunA$fShowAlwaysRerunA$fShowAlwaysRerunQ shakeOptsExExtraDemoProgressReplayProgressRecordNoBuild ExceptionNoTimeSleepHelpColorPrintDirectory AssumeOld AssumeNewNumericVersionVersionChangeDirectory showOptDescr fmapOptDescrunescapeescape ConfigKeysConfig