Fun stuff with unigi and haloo3d
Go to file
2024-08-15 03:53:13 -04:00
haloo3d@d19e5e7fbd maze more 2024-08-15 03:33:11 -04:00
resources Setting up first example 2024-08-12 21:21:18 -04:00
unigi Near 60fps 2024-08-13 00:40:03 -04:00
.gitignore Initial commit 2024-08-12 20:29:39 -04:00
.gitmodules Added submodules 2024-08-12 20:34:22 -04:00
camera.h Nearly working freecam 2024-08-13 02:08:21 -04:00
keys.h Nearly working freecam 2024-08-13 02:08:21 -04:00
LICENSE License 2024-08-12 21:54:25 -04:00
Makefile More accurate frame timer 2024-08-12 22:17:14 -04:00
maze.c better timers 2024-08-15 03:53:13 -04:00
README.md Some clarifications 2024-08-12 22:03:55 -04:00
scene_freecam.c Nearly working freecam 2024-08-13 02:08:21 -04:00
scene.c Setting up maze 2024-08-15 02:28:37 -04:00

3D Toys

Everything in here is a little sample program or otherwise which uses haloo3d and 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.

Unigi

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.

Unigi expects some kind of graphics backend to run. In this case, our samples use SDL1, so you'll need to get that.

Haloo3d

You can compile haloo3d using the makefile provided in the library repo, 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.