This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit 4f481ef285c1c7285f830a88f4c453ce5207a7b9
tree 4f75544ca3739c65d66af0489156a00a8db99df3
parent cbc3307bdfa0fb757545a75258249daa5e0a8506
tree 4f75544ca3739c65d66af0489156a00a8db99df3
parent cbc3307bdfa0fb757545a75258249daa5e0a8506
biild /
| name | age | message | |
|---|---|---|---|
| |
INSTALL | Wed Oct 28 02:46:12 -0700 2009 | |
| |
README | Tue Oct 27 01:35:55 -0700 2009 | |
| |
example/ | Wed Oct 28 02:45:50 -0700 2009 | |
| |
lib/ | Wed Oct 28 02:45:50 -0700 2009 | |
| |
spec/ | Tue Oct 27 01:35:55 -0700 2009 |
README
:: Biild :: A very tiny build system ::
Biild is a build system modeled after
Ruby Rake and built in the Ioke language.
:: How to Use ::
When Biild is run, it looks for a script
called a Biildfile in the current directory.
It can be called any of these things:
Biildfile
Biildfile.ik
biildfile
biildfile.ik
The first one that matches will be found
and loaded.
:: The Biildfile ::
Biildfiles are actually a simple DSL
interpreter that tasks are defined inside
of. A simple task looks like this:
task(:bloop,
"Inside the bloop task!" println
true
)
Then when Biild is run, like this:
$ biild bloop
The bloop task will be executed.
Tasks can also be namespaced, allowing
related tasks to be grouped together.
namespace(:sounds,
task(:buzz,
"bzzzzzzzzzzzzz" println
)
task(:hum,
"H M M M M M M" println
)
)
Namespace nesting isn't limited,
namespaces can be multiple levels deep.
To access a namespaced task, use the
convention namespace:task, i.e.:
$ biild sounds:buzz
:: More Information ::
Justin Poliey http://justinpoliey.com
Rake http://rake.rubyforge.org
Ioke http://ioke.org







