2024-08-13 00:29:39 +00:00
|
|
|
# 3D Toys
|
|
|
|
|
|
|
|
|
|
Everything in here is a little sample program or otherwise which
|
|
|
|
|
uses [haloo3d](https://github.com/randomouscrap98/haloo3d) and
|
|
|
|
|
[unigi](https://git.lumen.sh/Fierelier/unigi).
|
|
|
|
|
|
|
|
|
|
The libraries required are set as submodules, so you can pull them
|
|
|
|
|
with:
|
|
|
|
|
|
|
|
|
|
```
|
|
|
|
|
git submodule update --init
|
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
You don't need to pull in the submodules if you setup your includes
|
|
|
|
|
and stuff.
|
|
|
|
|
|
2024-08-13 01:21:18 +00:00
|
|
|
## Unigi
|
2024-08-13 00:29:39 +00:00
|
|
|
|
2024-08-13 01:21:18 +00:00
|
|
|
For the time being, unigi is designed such that it expects you to
|
|
|
|
|
compile your entire program as a single unit. This means you must
|
|
|
|
|
include all your .c files into the main file, in the right order.
|
|
|
|
|
|
|
|
|
|
This may change in the future.
|
|
|
|
|
|
|
|
|
|
## Haloo3d
|
|
|
|
|
|
|
|
|
|
You can compile haloo3d using the provided makefile, or include the
|
|
|
|
|
.h and .c files directly into the main translation unit like unigi
|
|
|
|
|
currently expects.
|
|
|
|
|
|
|
|
|
|
For these samples, they expect you to build the `haloo3d_full.a`
|
|
|
|
|
library using `make full` in the haloo3d submodule. For convenience,
|
|
|
|
|
the makefile for the samples assumes you are using the submodule
|
|
|
|
|
and runs make in there for you.
|
