# grinder 0.5.2

Grinder - a task based, dependency aware build system.




## Installing
```
export PUB_HOSTED_URL=https://pub.mirror.p-hatan.ir
flutter pub add 'grinder:0.5.2'
```
Published: 2014-04-11T22:01:23.705470Z
Expected archive SHA-256: 86b75995e5bf2f4e281b00e6826d427757e5e7b47358b48eea4c468b2f9a215a

Available in cache; verification: upstream_checksum
## Direct dependencies
- args: any
- quiver: >=0.18.0 <0.19.0

## Package README (untrusted upstream documentation)
# Grinder

Grinder - a task based, dependency aware build system.

[![Build Status](https://drone.io/github.com/google/grinder.dart/status.png)](https://drone.io/github.com/google/grinder.dart/latest)

### Intro

A library and tool to drive a command-line build.

Grinder build files are entirely specified in Dart code. This allows you to
write and debug your build files with the same tools you use for the rest of
your project source.

Generally, a Grinder implementation will look something like this:

    void main([List<String> args]) {
      defineTask('init', taskFunction: init);
      defineTask('compile', taskFunction: compile, depends: ['init']);
      defineTask('deploy', taskFunction: deploy, depends: ['compile']);
      defineTask('docs', taskFunction: deploy, depends: ['init']);
      defineTask('all', depends: ['deploy', 'docs']);

      startGrinder(args);
    }

    init(GrinderContext context) {
      context.log("I set things up");
    }

    ...

Tasks to run are specified on the command line. If a task has dependencies,
those dependent tasks are run before the specified task.

### Command-line usage
    usage: dart grinder.dart <options> target1 target2 ...

    valid options:
    -h, --help    show targets but don't build
    -d, --deps    display the dependencies of targets

### API documentation

Documentation is available [here](http://google.github.io/grinder.dart/).

## Changelog







 
