Update readme
This commit is contained in:
parent
6eaf0d9961
commit
30e4507317
20
README.md
20
README.md
@ -2,17 +2,29 @@
|
|||||||
|
|
||||||
Everything in here is a little sample program or otherwise which
|
Everything in here is a little sample program or otherwise which
|
||||||
uses [haloo3d](https://github.com/randomouscrap98/haloo3d) and
|
uses [haloo3d](https://github.com/randomouscrap98/haloo3d) and
|
||||||
[unigi](https://git.lumen.sh/Fierelier/unigi).
|
[unigi](https://git.lumen.sh/Fierelier/unigi). It's all software
|
||||||
|
rendered, but you'll need to get sdl1 so it can render to screen.
|
||||||
|
|
||||||
The libraries required are set as submodules, so you can pull them
|
The libraries required are set as submodules, so you can pull them
|
||||||
with:
|
when cloning with:
|
||||||
|
|
||||||
|
```
|
||||||
|
git clone --recurse-submodules
|
||||||
|
```
|
||||||
|
|
||||||
|
Or if you already cloned, you can do this after the fact:
|
||||||
|
|
||||||
```
|
```
|
||||||
git submodule update --init
|
git submodule update --init
|
||||||
```
|
```
|
||||||
|
|
||||||
You don't need to pull in the submodules if you setup your includes
|
Then, to build any example, just do `make name.exe`. For example, to
|
||||||
and stuff.
|
build maze.c, you would do
|
||||||
|
|
||||||
|
```
|
||||||
|
make maze.exe
|
||||||
|
./maze.exe
|
||||||
|
```
|
||||||
|
|
||||||
## Unigi
|
## Unigi
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user