使用者:DukeAnt/Rake
開發者 | Jim Weirich |
---|---|
程式語言 | Ruby |
作業系統 | Cross-platform |
類型 | Software development tools |
許可協議 | MIT License |
網站 | https://github.com/jimweirich/rake |
Rake is a software task management tool. It allows you to specify tasks and describe dependencies as well as to group tasks in a namespace.
It is similar to SCons and Make, but it has a number of differences. The tool is written in the Ruby programming language and the Rakefiles (equivalent of Makefiles in Make) use Ruby syntax. It was originated by Jim Weirich.
Rake uses Ruby's anonymous function blocks to define various tasks, allowing the use of Ruby syntax. It has a library of common tasks: for example, functions to do common file-manipulation tasks and a library to remove compiled files (the "clean" task). Like Make, Rake can also synthesize tasks based on patterns: for example, automatically building a file compilation task based on filename patterns. Rake is now part of the standard library from Ruby version 1.9 onward.
Example
編輯Below is an example of a simple Rake script to build a C Hello World program.
file 'hello.o' => 'hello.c' do
sh 'cc -c -o hello.o hello.c'
end
file 'hello' => 'hello.o' do
sh 'cc -o hello hello.o'
end
For further examples, see the Rakefile format documentation.
Rules
編輯When a file is named as a prerequisite but it does not have a file task defined for it, Rake will attempt to synthesize a task by looking at a list of rules supplied in the Rakefile. For example, suppose we were trying to invoke task "mycode.o" with no tasks defined for it. If the Rakefile has a rule that looks like this:
rule '.o' => '.c' do |t|
sh "cc #{t.source} -c -o #{t.name}"
end
This rule will synthesize any task that ends in ".o". It has as a prerequisite that a source file with an extension of ".c" must exist. If Rake is able to find a file named "mycode.c", it will automatically create a task that builds "mycode.o" from "mycode.c". If the file "mycode.c" does not exist, Rake will attempt to recursively synthesize a rule for it.
When a task is synthesized from a rule, the source attribute of the task is set to the matching source file. This allows us to write rules with actions that reference the source file.
Advanced rules
編輯Any regular expression may be used as the rule pattern. Additionally, a proc may be used to calculate the name of the source file. This allows for complex patterns and sources.
The following rule is equivalent to the example above:
rule(/\.o$/ =>
->(t_name){ t_name.sub /\.o$/, '.c' }) do |t|
sh "cc #{t.source} -c -o #{t.name}"
end
NOTE: Because of a quirk in Ruby syntax, parentheses are required around a rule when the first argument is a regular expression.
The following rule might be used for Java files:
rule '.class' => ->(t_name){ t_name
.sub(/\.class$/, '.java')
.sub(/^classes\//, 'src/') } do |t|
java_compile(t.source, t.name)
end
Below is an example of a simple Rake recipe:
namespace :cake do
desc 'make pancakes'
task :pancake => [:flour,:milk,:egg,:baking_powder] do
puts "sizzle"
end
task :butter do
puts "cut 3 tablespoons of butter into tiny squares"
end
task :flour => :butter do
puts "use hands to knead butter squares into 1{{frac|1|2}} cup flour"
end
task :milk do
puts "add 1{{frac|1|4}} cup milk"
end
task :egg do
puts "add 1 egg"
end
task :baking_powder do
puts "add 3{{frac|1|2}} teaspoons baking powder"
end
end
See also
編輯External links
編輯- Rake documentation
- GitHub project page for Rake
- Using the Rake build language by Martin Fowler
- Ruby on Rails Rake tutorial at railsenvy.com
- Custom Rake Tasks at railscasts.com
- Rake Tutorial at lukaszwrobel.pl
|