Scroll to navigation

RAKE(1)() (ruby programmers reference guide) RAKE(1)()

NAME

rakeRuby Make

SYNOPSIS

rake [--f Rakefile] [--version] [-CGNPgnqstv] [-D [PATTERN]] [-E CODE] [-I LIBDIR] [-R RAKELIBDIR] [-T [PATTERN]] [-e CODE] [-p CODE] [-r MODULE] [--rules] [variable=value] target ...

DESCRIPTION

Rake is a simple ruby(1) build program with capabilities similar to the regular make(1) command.

Rake has the following features:

  • Rakefiles (Rake's version of Makefiles) are completely defined in standard Ruby syntax. No XML files to edit. No quirky Makefile syntax to worry about (is that a tab or a space?).
  • Users can specify tasks with prerequisites.
  • Rake supports rule patterns to synthesize implicit tasks.
  • Flexible FileLists that act like arrays but know about manipulating file names and paths.
  • A library of prepackaged tasks to make building rakefiles easier.

OPTIONS

Display the program version.

 
Put Task and FileTask in the top level namespace

[PATTERN]
 
[PATTERN]
Describe the tasks (matching optional PATTERN), then exit.

CODE
 
CODE
Execute some Ruby code, then continue with normal task processing.

 
 
Use standard project Rakefile search paths, ignore system wide rakefiles.

LIBDIR
 
LIBDIR
Include LIBDIR in the search path for required modules.

 
 
Do not search parent directories for the Rakefile.

 
Display the tasks and dependencies, then exit.

RAKELIBDIR
 
RAKELIBDIR
 
RAKELIBDIR
Auto-import any .rake files in RAKELIBDIR. (default is rakelib )

[PATTERN]
 
[PATTERN]
Display the tasks (matching optional PATTERN) with descriptions, then exit.

CODE
 
CODE
Execute some Ruby code and exit.

FILE
 
FILE
Use FILE as the rakefile.

 
Prints a summary of options.

 
Using system wide (global) rakefiles (usually ~/.rake/*.rake ).

 
Do a dry run without executing actions.

CODE
 
CODE
Execute some Ruby code, print the result, then exit.

 
Do not log messages to standard output.

MODULE
 
MODULE
Require MODULE before executing rakefile.

 
Like --quiet, but also suppresses the 'in directory' announcement.

 
Turn on invoke/execute tracing, enable full backtrace.

 
Log message to standard output (default).

Trace the rules resolution.

SEE ALSO

ruby(1) make(1)

http://rake.rubyforge.org/

REPORTING BUGS

Bugs, features requests and other issues can be logged at <http://onestepback.org/redmine/projects/show/rake>.

You will need an account to before you can post issues. Register at <http://onestepback.org/redmine/account/register>. Or you can send an email to the author.

AUTHOR

Rake is written by Jim Weirich ⟨jim@weirichhouse.org⟩

November 7, 2012 UNIX