blob: 4f1dc31667961f57fe7d80a5684494924345d7c8 (
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
43
|
Building from source:
You've probably already done this, but first clone the repo:
`git clone git://git.pengaru.com/sars`
There are a few submodules which must be initialized recursively
before sars will be able to compile, this does the trick:
`git submodule update --init --recursive --remote`
*** New enough git versions support recursive clone too:
` git clone --recursive git://git.pengaru.com/sars`
Now it's fairly run of the mill autotools:
```
$ mkdir build
$ ./bootstrap
$ cd build
$ ../configure
$ make
$ ./src/sars
```
The program assumes there will be assets found under the assets/
folder relative to the sars executable's parent directory.
These are some .ogg files and .wav files, and they're not checked
into the git repo to keep development low-bw friendly.
You may find the assets in a build available at:
https://dl.pengaru.com/hungrycat/sars/
The latest build should reflect the current state of the master git
branch:
https://dl.pengaru.com/hungrycat/sars/hungrycat-sars-latest.zip
There's also a Pouet entry for sars with youtube and other links:
https://www.pouet.net/prod.php?which=85496
|
