blob: c88482b36f7a2d215d1cc2a921ed25c37827aebf (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
+++
title = "Zero Install Option"
weight = 40
+++
Don't want to depend on another binary in your environment? You can run mage
directly out of your vendor directory (or GOPATH) with `go run`.
Just save a file like this (I'll call it `mage.go`, but it can be named
anything. Note that the build tag is *not* `+build mage`. Mage will create its own main file, so we need this one to be excluded from when your magefiles are compiled.
Now you can `go run mage.go <target>` and it'll work just as if you ran `mage
<target>`
```go
// +build ignore
package main
import (
"os"
"github.com/magefile/mage/mage"
)
func main() { os.Exit(mage.Main()) }
```
Note that because of the peculiarities of `go run`, if you run this way, go run
will only ever exit with an error code of 0 or 1. If mage exits with error code
99, for example, `go run` will print out `exit status 99" and then exit with
error code 1. Why? Ask the go team. I've tried to get them to fix it, and
they won't.
## Use Mage as a library
All of mage's functionality is accessible as a compile-in library. Checkout
[godoc.org/github.com/magefile/mage/mage](https://godoc.org/github.com/mage/mage)
for full details.
Fair warning, the API of mage/mage may change, so be sure to use vendoring.
|
