1RAKE(1) Ruby Programmers Reference Guide RAKE(1)
2
4 rake — Ruby Make
5
7 rake [--f Rakefile] [--version] [-CGNPgnqstv] [-D [PATTERN]] [-E CODE]
8 [-I LIBDIR] [-R RAKELIBDIR] [-T [PATTERN]] [-e CODE] [-p CODE]
9 [-r MODULE] [--rules] [variable=value] target ...
10
12 Rake is a simple ruby(1) build program with capabilities similar to the
13 regular make(1) command.
14
15 Rake has the following features:
16
17 · Rakefiles (Rake's version of Makefiles) are completely defined in
18 standard Ruby syntax. No XML files to edit. No quirky Makefile syn‐
19 tax to worry about (is that a tab or a space?).
20
21 · Users can specify tasks with prerequisites.
22
23 · Rake supports rule patterns to synthesize implicit tasks.
24
25 · Flexible FileLists that act like arrays but know about manipulating
26 file names and paths.
27
28 · A library of prepackaged tasks to make building rakefiles easier.
29
31 --version Display the program version.
32
33 -C
34 --classic-namespace
35 Put Task and FileTask in the top level namespace
36
37 -D [PATTERN]
38 --describe [PATTERN]
39 Describe the tasks (matching optional PATTERN), then
40 exit.
41
42 -E CODE
43 --execute-continue CODE
44 Execute some Ruby code, then continue with normal
45 task processing.
46
47 -G
48 --no-system
49 --nosystem Use standard project Rakefile search paths, ignore
50 system wide rakefiles.
51
52 -I LIBDIR
53 --libdir LIBDIR Include LIBDIR in the search path for required mod‐
54 ules.
55
56 -N
57 --no-search
58 --nosearch Do not search parent directories for the Rakefile.
59
60 -P
61 --prereqs Display the tasks and dependencies, then exit.
62
63 -R RAKELIBDIR
64 --rakelib RAKELIBDIR
65 --rakelibdir RAKELIBDIR
66 Auto-import any .rake files in RAKELIBDIR. (default
67 is rakelib )
68
69 -T [PATTERN]
70 --tasks [PATTERN] Display the tasks (matching optional PATTERN) with
71 descriptions, then exit.
72
73 -e CODE
74 --execute CODE Execute some Ruby code and exit.
75
76 -f FILE
77 --rakefile FILE Use FILE as the rakefile.
78
79 -h
80 --help Prints a summary of options.
81
82 -g
83 --system Using system wide (global) rakefiles (usually
84 ~/.rake/*.rake ).
85
86 -n
87 --dry-run Do a dry run without executing actions.
88
89 -p CODE
90 --execute-print CODE
91 Execute some Ruby code, print the result, then exit.
92
93 -q
94 --quiet Do not log messages to standard output.
95
96 -r MODULE
97 --require MODULE Require MODULE before executing rakefile.
98
99 -s
100 --silent Like --quiet, but also suppresses the 'in directory'
101 announcement.
102
103 -t
104 --trace Turn on invoke/execute tracing, enable full back‐
105 trace.
106
107 -v
108 --verbose Log message to standard output (default).
109
110 --rules Trace the rules resolution.
111
113 ruby(1) make(1)
114
115 http://rake.rubyforge.org/
116
118 Bugs, features requests and other issues can be logged at
119 <http://onestepback.org/redmine/projects/show/rake>.
120
121 You will need an account to before you can post issues. Register at
122 <http://onestepback.org/redmine/account/register>. Or you can send an
123 email to the author.
124
126 Rake is written by Jim Weirich <jim@weirichhouse.org>
127
128UNIX November 7, 2012 UNIX