!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~" Safe-Inferred None<Print all withTiming information and clear the information.   Safe-Inferred   Safe-Inferred1Generates an HTML report given some build system " profiling data in JSON format. ETemplate 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  Safe-Inferred  NoneUTF8 ByteString ASCII ByteString .Starts out empty, then is filled exactly once &Like an MVar, but must always be full Like an MVar, but has no value DCall once at the start, then call repeatedly to get Time values out Like nub', but the results may be in any order. 3   (.   None 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. %Combine two file paths, an alias for . ;Remove the current extension and add another, an alias for . $Combine two file paths. Any leading ./ or ../ components in the right file  are eliminated. * combine "aaa/bbb" "ccc" == "aaa/bbb/ccc" , combine "aaa/bbb" "./ccc" == "aaa/bbb/ccc" ) combine "aaa/bbb" "../ccc" == "aaa/ccc" The extension of executables, "exe" on Windows and "" otherwise. 6  !"#$%&'()*+,-./012345678 9 None:!This is a hot-spot, so optimised ;<:=>?@<:=;<:=>?@ NoneAHGiven a pool, and a function that breaks the S invariants, restore them 2 They are only allowed to touch working or todo BAdd a new task to the pool CEA blocking action is being run while on the pool, yield your thread. 5 Should only be called by an action under addPool. MIf the first part of the result is True then the result is sufficiently high K priority that you may exceed the pool limit to get it done immediately. M Always the result of a child thread raising an error, which will probably ! raise an error in the parent. D<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. EFGHIJKLMNOPQRSTUVWXYZ[\ABCDMBCDEFGHIJKLMNOQPRSTUVWXYZ[\ABCDNone ]^_`abcdefg]_abcdef ]^_`abcdefgNone hijklmnopqrstjmno hijklmnopqrstNone-A type synonym for file patterns, containing // and *. For the syntax  and semantics of  see . u$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 that match:    "//*.c"  "foo/bar/baz.c"  "*.c"  "baz.c"  "//*.c"  "baz.c"  "test.c"  "test.c" Examples that don't match:    "*.c"  "foo/bar.c"  "*/*.c"  "foo/bar/baz.c" )An example that only matches on Windows:   "foo/bar"  "foo\\bar" v?Given a pattern, return the directory that requires searching,  with w: 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) xNGiven a set of patterns, produce a set of directories that require searching,  with wD 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)] yDo they have the same * and  counts in the same order zEExtract the items that match the wildcards. The pair must match with . {Given the result of z, substitute it back in to a y pattern. / p '?==' x ==> substitute (extract p x) p == x |}~uvxyz{vxyz{|} ~uvxyz{NoneA stream of values 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). &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.  Version of & that omits the sleep '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 (. ! !"#$%&'() !"#$%&'()  !"#$%&'() Safe-Inferred*<Error representing all expected exceptions thrown by Shake. L Problems when executing rules will be raising using this exception type. ,<The target that was being built when the exception occured. - The stack of targets, where the , is last. .*The underlying exception that was raised. *+,-. *+,-.*+,-.Noneq(number available, queue of people with how much they want and a barrier to signal 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. Key used for Eq/EOrd operations. To make withResources work, we require newResourceIO < newThrottleIO String used for Show jTry to acquire a resource. Returns Nothing to indicate you have acquired with no blocking, or Just act to O say after act completes (which will block) then you will have the resource. MYou should only ever releaseResource that you obtained with acquireResource. 0 A version of 3 that runs in IO, and can be called before calling .  Most people should use  instead. 1 A version of 3 that runs in IO, and can be called before calling .  Most people should use  instead. /01/01 /01None NoneNone2!The verbosity data type, used by >. 3@Print messages for virtually everything (mostly for debugging). 4JPrint errors, full command line and status messages when starting a rule. 53Print errors and full command lines when running a  or  command. 6Print errors and #  command-name  file-name when running a   command. 71Only print essential messages, typically errors. 8Don't print any messages. ,Internal type, copied from Hide in Uniplate 9UOptions to control the execution of Shake, usually specified by overriding fields in  O:   O{<=4, @=Just " report.html"}The $ instance for this type reports the I and J$ 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. < 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. = 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. > Defaults to 60. What level of messages should be printed out. ? Defaults to G. Operate in staunch mode, where building continues even after errors,  similar to make --keep-going. @ Defaults to :. Write an HTML profiling report to a file, showing which j rules rebuilt, why, and how much time they took. Useful for improving the speed of your build systems. A Defaults to N. Perform basic sanity checks during building, checking the current directory M is not modified and that output files are not modified by multiple rules. K These sanity checks do not check for missing or redundant dependencies. B 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  B seconds will be lost. C Defaults to $. Assume all build objects are clean/ dirty, see K for details.  Can be used to implement  make --touch. D 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). E 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. F Defaults to w . Change stdout and stderr( to line buffering while running Shake. G Defaults to 6. Print timing information for each stage at the end. H Default to w.. 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. IbDefaults 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. JDefaults to writing using B. A function called to output messages from Shake, along with the 2 at ` which that message should be printed. This function will be called atomically from all other J functions.  The 2, will always be greater than or higher than >. K:The current assumptions made by the build system, used by C. 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 ! commands. Any 3 other files in the database are left unchanged. LNThis 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 " operations. MbThis 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 "G 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. NNAssume that all rules reached are dirty and require rebuilding, equivalent to " always  returning  . Useful to undo the results of M%, for benchmarking rebuild speed and a for rebuilding if untracked dependencies have changed. This assumption is safe, but may cause # more rebuilding than necessary. OThe default set of 9. *23456789:;<=>?@ABCDEFGHIJKLMNO) !"#$%23456789:;<=>?@ABCDEFGHIJKLMNO28765439:;<=>?@ABCDEFGHIJKNMLO#None$Is the exception asyncronous, not a  coding error that should be ignored Storage options Logging function Witness Execute $None[Given a Key and a Value from the database, check it still matches the value stored on disk mGiven a chunk of stack (bottom element first), and a key, either raise an exception or successfully build it NInvariant: The database does not have any cycles when 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 G      !"#$%&'()*+,-./0123456789:;<=$&(2459*      !"#$%&'()*+,-./0123456789:;<=%NoneQThe Q monad, use P to raise > actions into it, and  to execute files.  Action values are used by W and X. The Q$ monad tracks the dependencies of a S. R:Define a set of rules. Rules can be created with calls to W, V or X. Rules are combined  with either the ?" instance, or (more commonly) the @ instance and do notation. S8Define a pair of types that can be used by Shake rules. / To import all the type classes required see Development.Shake.Classes. T 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, T should return . UODefine an alias for the six type classes required for things involved in Shake &s. 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) VLike W, but lower priority, if no W exists then V is checked. ' All default rules must be disjoint. W4Add a rule to build a key, returning an appropriate Q. All rules must be disjoint. & To define lower priority rules use V. ATAdd a rule at a given priority, higher numbers correspond to higher-priority rules.  The function V is priority 0 and W& is priority 1. All rules of the same  priority must be disjoint. XCRun an action, usually used for specifying top-level requirements.    main =  O $ do  X $ do  b <- ' "file.src"  when b $  ["file.out"] This X builds file.out, but only if file.src exists. The X 0 will be run in every build execution (unless Y is used), so only cheap 4 operations should be performed. All arguments to X' may be run in parallel, in any order. %For the standard requirement of only !ing a fixed list of files in the X,  see (. YNRemove all actions specified in a set of rules, usually used for implementing 0 command line specification of what to build. Z!If an exception is raised by the Q, perform some >. [ After an Q, perform some >!, even if there is an exception. B/Internal main function (not exported publicly) \aExecute 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 W or V.  All key values passed to \ become dependencies of the Q. ]+Apply a single rule, equivalent to calling \( with a singleton list. Where possible,  use \ to allow parallelism. ^Get the initial 92, these will not change during the build process. _7Write an action to the trace list, along with the start/#end time of running the IO action.  The  and  functions automatically call _. 3 The trace list is used for profile reports (see @). `2Write a message to the output when the verbosity (>) is appropriate. D The output will not be interleaved with any other Shake messages 4 (other than those generated by system commands). a2Write a message to the output when the verbosity (>) is appropriate. D The output will not be interleaved with any other Shake messages 4 (other than those generated by system commands). b2Write a message to the output when the verbosity (>) is appropriate. D The output will not be interleaved with any other Shake messages 4 (other than those generated by system commands). c3Get the current verbosity level, originally set by > . If you I want to output information to the console, you are recommended to use  ` / a / b&, which ensures multiple messages are = not interleaved. The verbosity can be modified locally by d. d1Run an action with a particular verbosity level.  Will not update the > returned by ^ and will  not have any impact on 3 tracing. eRun an action with 7/ verbosity, in particular messages produced by _  (including from  or %) will not be printed to the screen.  Will not update the > returned by ^ and will  not turn off any 3 tracing. fhCreate 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:     ){* =2} $ do  ( ["a.xls","b.xls"]  excel <-  "Excel" 1  "*.xls" + \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  ( [show i , "exe" | i < - [1..100]]  "*.exe" + \out ->   disk 1 $   "ld -o" [out] ...  "*.o" + \out ->   "cl -o" [out] ... g^Create a throttled resource, given a name (for error messages) and a number of resources (the C) that can be  used per time period (the DO 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" + \ 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" + \ 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. hIRun an action which uses part of a finite resource. For more details see /.  You cannot call \ / need! while the resource is acquired. i^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 i, resources will not deadlock. j\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 < limit to be exceeded.  You cannot call \ / & while the extra thread is executing. OQEFGHIJKLMNOPQRSTUVWXYZ[\]^_R`abSTUcdefghVWAXYZ[Bijklmnopqr\s]^_t`abcdefguhijvw /01QRSTUeVWXYZ[Br\]^_`abcdefghij4QEFGHIJKLMNOPQRSTUVWXYZ[\]^_R`abSTUcdefghVWAXYZ[Bijklmnopqr\s]^_t`abcdefguhijvwNonekHA class for specifying what results you want to collect from a process.  Values are formed of r, o, l and tuples of those. l Collect the x of the process. , If you do not collect the exit code, any y will cause an exception. o Collect the stderr of the process.  If you are collecting the stderr<, it will not be echoed to the terminal, unless you include v. r Collect the stdout of the process.  If you are collecting the stdout<, it will not be echoed to the terminal, unless you include w. uOptions passed to  or ( to control how processes are executed. vShould I echo the stderr? Defaults to w unless a o result is required. wShould I echo the stdout? Defaults to w unless a r result is required. xShould I include the stderr4 in the exception if the command fails? Defaults to w. yName to use with _, or ""E for no tracing. By default traces using the name of the executable. z 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 no stdin is given. }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 u 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 u 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 . )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 u 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 r,  o and l. Some examples:     [] "gcc" ["-c","myfile.c"]N -- compile a file, throwing an exception on failure  l c <-  [] "gcc" ["-c",myfile]? -- run a command, recording the exit code  (l c, o err) <-  [] "gcc" ["-c","myfile.c"]> -- run a command, recording the exit code and error output  r 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 x using l, any y will throw an error, including  the o. in the exception message. If you capture the r or o1, that stream will not be echoed to the console,  unless you use the option w or v.  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 k. 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 k. )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.  u arguments are used as options. To take the examples from :    () <-  "gcc -c myfile.c"V -- compile a file, throwing an exception on failure  l c <-  "gcc -c" [myfile]H -- run a command, recording the exit code  (l c, o err) <-  "gcc -c myfile.c"K -- run a command, recording the exit code and error output  r out <-  "gcc -MM myfile.c"@ -- run a command, recording the output   (~ " generated") "gcc -c" [myfile] :: Q, () -- 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 k*. To avoid this error, bind the result to (), or include a type signature. The  command can also be run in the > monad, but then y. is ignored and command lines are not echoed. 6z{|}~klmnopqrstuvwxyz{|}~klmnopqrstuvwxyz{|}~rstopqlmnku~}|{zyxwv!z{|}~klmnopqrstu ~}|{zyxwv.None MThis function is not actually exported, but Haddock is buggy. Please ignore. Returns w? 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 wI 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. 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"] [Remove all empty directories and files that match any of the patterns beneath a directory.  Some examples:     "output" ["//*"]   "." ["//*.hi","//*.o"] -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. 1 %/None MThis 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 = 0 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 A/ is set, check that the file does not rebuild. S Used for adding dependencies on files that have already been used in this rule. TRequire that the argument files are built by the rules, used to specify the target.    main =  O $ 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 X and , use X 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 w 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 w. N This function will create the directory for the result file, if necessary.   (all isUpper . -)  \ out -> do  let src = 1& out $ map toLower $ takeBaseName out  2 out . map toUpper =<< 3 src QDefine a set of patterns, and if any of them match, run the associated rule. See . Define a rule that matches a ). No file required by the system must be @ matched by more than one pattern. For the pattern rules, see . N This function will create the directory for the result file, if necessary.    "*.asm.o"  \ out -> do  let src = 0 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.  A version of 3 that runs in IO, and can be called before calling .  Most people should use  instead. pGiven a way of loading information from a file, produce a cached version that will load each file at most once. U Using the cached function will still result in a dependency on the original file. ` The argument function should not access any files other than the one passed as its argument.  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"  \x -> do  v1 < - digits ( dropExtension x)  v2 < - digits ( dropExtension x)  2 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.  4None1Add 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 5 $  "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 6.  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. 7NoneHDefine 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. 8NoneIAlways rerun the associated action. Useful for defining rules that query ! the environment. For example:   "ghcVersion.txt" + \ out -> do    9 stdout <-  "ghc --numeric-version"  : out stdout  ;None[Main entry point for running Shake build systems. For an example see the top of the module Development.Shake.  Use 9% to specify how the system runs, and R3 to specify what to build. The function will throw $ an exception if the build fails. $To use command line flags to modify 9 see <. =NoneCRun 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 9 , such as --print-directory. + If there are no file arguments then the R1 are used directly, otherwise the file arguments  are ed (after calling Y). As an example:    main =  O{; = "_make/", I = )} $ do   "clean" $ > "_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 9D value, which may have some fields overriden by command line flags.  This argument is usually O', perhaps with a few fields overriden.  flags8 is a list of flag descriptions, which either produce a  containing an error > message (typically for flags with invalid arguments, .e.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 =  O 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 9. Each option returns a either an error message (invalid argument to the flag) or a function that changes some fields  in 9. 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<Define a rule for building multiple files at the same time. ; As an example, a single invokation 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. LDefine a rule for building multiple files at the same time, a more powerful ! and more dangerous version 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 | A x `elem` [".hi",".o"]  = Just [0 x , "hi", 0 x , "o"] test _ = Nothing Regardless of whether Foo.hi or Foo.o( is passed, the function always returns [Foo.hi, Foo.o]. 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. Read a file, after calling 5. The argument file will be tracked as a dependency. Write a file, lifted to the Q 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.   NoneA variable arity version of . A variable arity version of . A variable arity version of . =A variable arity function to accumulate a list of arguments.           None !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~OUSTRVWXYQ\]_PZ[*+,-.9:;<=>?@ABCDEFGHIJKNML^ !"#$%)&'(2876543c`abderstopqlmnku~}|{zyxwv/f0hig1jNoneVGiven 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) CDECDFGHIGJKGHLGHMGHNGJOCDPQRSQRTQRUVWXVWYZ[\Z[]Z[^_`abc@defghhijklmnopqrstuvvwxyz{|}~*)%%%&%"%%%%!%%%%%%% %%%%%%%%%%%995.'.......>///(/////+//444786;=<==??BBBBB3B2BBB:CGGGGQRQRQRQRQQQQ                                       ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9G:;<=><=?<=@<=A<=B<=C<=D<=E<=F<=G<=H<=I<=J<=K<=L<=M<=1<=-<=N<=O<=P<=Q<=R<=S<=T<=U<=V<=W<=X<=Y<=Z<=[<=\<=0<=,<=A<=]<=^<=_<=`<=a<=b<=c<=d<=e f g a h i j k l m n o o p q r s t u v v w x y z z { | } ~     CGGzGCG     ########$$$$$$$$$$$$$ $!$"$"$#$#$$$%$&$'$($)$*$+$!$,$-$.$$/$0$1$k$2$3$4$5$6$6$7$7$$8$9$:$;$<$=$>$?$@$A$B$C$D$E$F$G$H$I$J$K$L$M$N$O$P$Q$RCSGTUGVW%X%YCZC[%%\%\%]%^%_%`%a%b%3%c%d%e%f%'%g%)%h%i%i%%%j%k%k%l%m%%n%n%o%p%q%r%s%t%u%v%w%x%y%z%{%|%}%~%%%%%GG#........................................./////////////44444777777777888888888GVG=================????????B    shake-0.10.9Development.Shake.ClassesDevelopment.Shake.FilePathDevelopment.ShakeDevelopment.Shake.CommandDevelopment.Shake.SysDevelopment.Shake.UtilGeneral.BinaryGeneral.Timing Paths_shakeDevelopment.Shake.Report General.BaseDevelopment.Shake.ByteStringDevelopment.Shake.PoolGeneral.InternDevelopment.Shake.FileTimeDevelopment.Shake.FilePatternDevelopment.Shake.Progress shakeProgressDevelopment.Shake.ErrorsDevelopment.Shake.Resource newResource newThrottle withResourcecmdneed withResourcesshakeDevelopment.Shake.ValueDevelopment.Shake.SpecialDevelopment.Shake.Typescommandtracedaction storedValueDevelopment.Shake.StorageDevelopment.Shake.DatabaseDevelopment.Shake.CoreRule doesFileExistwant shakeOptions shakeThreads*><.> takeBaseName!Development.Shake.Rules.DirectoryDevelopment.Shake.Rules.File dropExtensionreplaceBaseName writeFile' readFile'Development.Shake.Rules.Oracle fromStdout alwaysRerun!Development.Shake.Rules.OrderOnlyDevelopment.Shake.Rules.RerunStdoutwriteFileChangedDevelopment.Shake.Shake shakeArgsDevelopment.Shake.ArgsremoveFilesAfterDevelopment.Shake.Rules.Files-<.> takeExtensionDevelopment.Shake.Derivedghc-prim GHC.Classes==EqbaseGHC.ShowShowData.Typeable.InternalTypeableshowListshow showsPrectypeOf/=binary-0.5.1.1 Data.BinarygetputBinarydeepseq-1.3.0.1Control.DeepSeqrnfNFDatahashable-1.2.1.0Data.Hashable.Classhash hashWithSaltHashabledropDirectory1takeDirectory1 normalisetoNativecombineexe FilePattern?==Progress isFailure countSkipped countBuilt countUnknown countTodo timeSkipped timeBuilt timeUnknowntimeTodoprogressDisplayprogressTitlebarprogressProgramprogressSimpleShakeExceptionshakeExceptionTargetshakeExceptionStackshakeExceptionInnerResource newResourceIO newThrottleIO Verbosity DiagnosticChattyLoudNormalQuietSilent ShakeOptions shakeFiles shakeVersionshakeVerbosity shakeStaunch shakeReport shakeLint shakeFlush shakeAssumeshakeAbbreviationsshakeStorageLogshakeLineBuffering shakeTimingsshakeRunCommands shakeOutputAssume AssumeSkip AssumeClean AssumeDirtytransformers-0.3.0.0Control.Monad.IO.ClassliftIOActionRules ShakeValue defaultRulerulewithoutActionsactionOnException actionFinallyapplyapply1getShakeOptionsputLoud putNormalputQuiet getVerbosity withVerbosityquietlyunsafeExtraThread CmdResultExitfromExitStderr fromStderr CmdOption EchoStderr EchoStdout WithStderrTraced BinaryPipesShellStdinEnvCwdaddPathaddEnvcommand_doesDirectoryExistgetEnvgetDirectoryContentsgetDirectoryFilesgetDirectoryDirs removeFilesneededphony~>?>**> newCacheIOnewCache addOracle askOracle askOracleWith orderOnly shakeArgsWithshakeOptDescrs*>>?>>system' systemCwd systemOutput copyFile' readFileLineswriteFileLinessyssysCwd sysOutputargs parseMakefileneedMakefileDependenciesneededMakefileDependencies BinaryWithputWithgetWith$fBinaryWithctxMaybe$fBinaryWithctx[]$fBinaryWithctx(,) GHC.TypesWordGHC.WordWord8Word16Word32Word64 decodeFile encodeFiledecodeencodeData.Binary.PutputWord8PutData.Binary.GetgetWord8Get printTimingstimings resetTimings addTiming showTimingsshowGapshowDPcatchIOversionbindirlibdirdatadir libexecdir getBinDir getLibDir getDataDir getLibexecDirgetDataFileName buildReport runTemplatelbs_stripPrefixBSUBSBarrierVarLock offsetTimefastNubDurationTimenewLockwithLock withLockTrynewVarreadVar modifyVar modifyVar_withVar newBarrier signalBarrier waitBarrierdurationsleep modifyIORef'' writeIORef'' showQuotewhenJustloopwhileM concatMapM partitionM isWindowspackunpackpack_unpack_packUunpackUunpackU_packU_requireU $fNFDataBSU $fNFDataBS$fShowBS $fShowBarrier $fShowVar $fShowLockGHC.IOFilePathfilepath-1.3.0.1System.FilePath.PosixpathSeparatorsreplaceExtension makeRelative isAbsolute isRelative makeValidisValid equalFilePathjoinPathsplitDirectories splitPathreplaceDirectory takeDirectorydropTrailingPathSeparatoraddTrailingPathSeparatorhasTrailingPathSeparator takeFileName dropFileNamereplaceFileName splitFileNameisDrivehasDrive dropDrive takeDrive joinDrive splitDrivetakeExtensionsdropExtensionssplitExtensions hasExtension addExtensionsplitExtension getSearchPathsplitSearchPathisExtSeparator extSeparatorisSearchPathSeparatorsearchPathSeparatorisPathSeparator pathSeparatorlinesCR endsSlashdotDotdotslashstepaddPool blockPoolrunPoolSthreads threadsMax threadsSumworkingblockedtodoPoolTreeBranchLeafQueueNonDetnonDetnewQueueenqueuePriorityenqueuedequeue insertTree removeTreeemptySIdInternemptyinsertaddlookuptoListfromList$fBinaryWithwIdExtractFileTimeextractFileTimeFileTimefileTime fileTimeNonegetModTimeErrorgetModTimeMaybegetModTimeMaybePortablegetModTimeMaybeUnix$fExtractFileTimeUTCTime$fExtractFileTimeClockTime$fShowFileTimematch directories1True directories compatibleextract substituteSStringRegexEmptyRepeatConcatOrBracketEndStartAnyNotLitLexemeChar SlashSlashStarisCharisDullfromCharlexerpatternStream Data.MaybeNothingJustprogressDisplayTester runStreamidStream oldStreamiff foldStream posStreamfromIntdecaylatchmessageprogressDisplayerxterm$fApplicativeStream$fFunctorStream$fMonoidProgresserr alternativeserrorStructured structurederrorNoRuleToBuildTypeerrorRuleTypeMismatcherrorIncompatibleRuleserrorMultipleRulesMatcherrorRuleRecursionerrorDuplicateOracle errorNoApplyspecialIsOracleKey$fShowShakeException$fExceptionShakeExceptionFinite resourceOrd resourceShowacquireResourcereleaseResourceThrottle throttleLock throttleVal throttleTime resourceIds resourceId $fOrdResource $fEqResource$fShowResourceWitness typeNames witnessIn witnessOutValueKeynewKeynewValuetypeKey typeValuefromKey fromValuewitnessregisterWitness toStableListcurrentWitness$fBinaryWithWitnessValue$fBinaryWitness $fEqWitness $fEqValue$fHashableValue $fNFDataValue $fShowValue $fShowKeyspecialAlwaysRebuildsspecialIsFileKeyFunction Data.DataDataFalse System.IOputStrLn fromFunctionfieldsShakeOptionstyShakeOptionsconShakeOptionsunhide tyFunction$fDataFunction$fShowFunction$fShowShakeOptions$fDataShakeOptionsasyncExceptionMapdatabaseVersion withStorage flushThread readChunkstoChunk showExceptionstoredexecuteDatabasebuilddependencyOrder resultsOnlyStepKeyOpsDepends fromDependsWaitingPendingResultresultbuiltchangeddepends executiontracesStatusMissingLoadedErrorReadylockinternstatusjournal diagnosticassumeTraceStackStepincStep showStackaddStacktopStack checkStack emptyStack statusTypeisError isWaitingisReady afterWaiting newWaiting runWaitingwaitFor getResultprogress removeStepshowJSON checkValidstepKey toStepResultfromStepResult withDatabase$fBinaryWithWitnessStatus$fBinaryWithWitnessResult$fBinaryWithWitnessStep $fShowPendingIO Data.MonoidMonoidGHC.BaseMonad rulePriorityrunIntDoubleSActiondatabasepool timestampruleinfooutputoptslintafterstack verbositydiscount blockapplyRuleInfo resultTypeSRulesactionsrulesARuleruleKey ruleValuerulesIOnewRules modifyRulesgetRuleswithCapabilities lineBuffering abbreviate wrapStackregisterWitnessescreateRuleinfo runStored runExecute runActionrunAfter applyKeyValueputWhen blockApply $fMonoidRules$fMonoidSRulesGHC.IO.ExceptionExitCode ExitFailureArgarg CmdArguments cmdArguments:-> cmdResult ResultCode ResultStderr ResultStdoutcommandExplicitcommandExplicitIOforkWaitsaneCommandForUser cmdResultWith$fArg[]$fArgCmdOption$fArg[]0$fArg[]1$fCmdArgumentsIO$fCmdArgumentsAction$fCmdArguments(->)$fCmdResult(,,)$fCmdResult(,) $fCmdResult()$fCmdResultStderr$fCmdResultStdout$fCmdResultExitCode$fCmdResultExitdefaultRuleDirectory GetDirectoryA GetDirectoryQ GetDirDirs GetDirFilespatGetDirdirGetEnvAGetEnvQDoesDirectoryExistADoesDirectoryExistQDoesFileExistADoesFileExistQgetEnvIO getDirActioncontentsanswergetDir $fRuleGetDirectoryQGetDirectoryA$fRuleGetEnvQGetEnvA,$fRuleDoesDirectoryExistQDoesDirectoryExistA"$fRuleDoesFileExistQDoesFileExistA$fBinaryGetDirectoryQ$fHashableGetDirectoryQ$fNFDataGetDirectoryQ$fShowGetDirectoryA$fShowGetDirectoryQ $fShowGetEnvA $fShowGetEnvQ$fShowDoesDirectoryExistA$fShowDoesDirectoryExistQ$fShowDoesFileExistA$fShowDoesFileExistQdefaultRuleFileFileAFileQneedBSneededBS neededCheckroot$fRuleFileQFileA $fShowFileA $fEqFileA $fShowFileQOracleAOracleQ$fRuleOracleQOracleA OrderOnlyA OrderOnlyQdefaultRuleOrderOnly orderOnlyBS$fRuleOrderOnlyQOrderOnlyA$fShowOrderOnlyA$fShowOrderOnlyQ AlwaysRerunA AlwaysRerunQdefaultRuleRerun$fRuleAlwaysRerunQAlwaysRerunA$fEqAlwaysRerunA$fShowAlwaysRerunA$fShowAlwaysRerunQString Data.EitherLeft shakeOptsExExtraNoBuild ExceptionNoTimeSleepHelpColorPrintDirectory AssumeOld AssumeNewVersionChangeDirectory showOptDescr fmapOptDescrunescapeescapeFilesAFilesQ getFileTimes$fRuleFilesQFilesA $fShowFilesQ $fShowFilesA checkExitCode ArgsArgumentsargs_SysOutputArguments sysOutput_SysCwdArgumentssysCwd_ SysArgumentssys_$fArgsArguments[]$fArgsArguments(->)$fSysOutputArgumentsAction$fSysOutputArguments(->)$fSysCwdArgumentsAction$fSysCwdArguments(->)$fSysArgumentsAction$fSysArguments(->)