3D Toys

Everything in here is a little sample program or otherwise which uses haloo3d and unigi. It's all software rendered, but you'll need to get sdl2 so it can render to screen.

The libraries required are set as submodules, so you can pull them when cloning with:

git clone --recurse-submodules https://git.lumen.sh/haloopdy/3dtoys.git

Or if you already cloned, you can do this after the fact:

git submodule update --init

Then, to build any example, just do make name.exe. For example, to build terrain.c, you would do

make terrain.exe
./terrain.exe

If you're having trouble building, you can try to force past the warnings (they're usually nothing):

make FORCE=1 terrain.exe

Unigi

Unigi is a small library and is built manually using the 3dtoys makefile. You can tinker around with Unigi if you like; it has its own make system, but I'm not sure what is required. The parts that are required for 3dtoys are handled with the 3dtoys makefile.

Unigi expects some kind of graphics backend to run. In this case, our samples use SDL2, 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. For convenience, the makefile for the samples here assumes you are using the submodule and runs make in there for you.

More info

When building examples for most platforms, we build a haloo3d_full.a using make full in the haloo3d submodule. This is linked into the final program when appropriate; you can utilize this same strategy. However, when building for PS2 and other consoles, we include everything directly into the main c file. Feel free to use either method.

Legacy code

I changed haloo3d a lot and it required a code split. All the old examples that built against this older codebase still work, they're just in the v1 folder. The same instructions above apply in this folder too.

Unless you need to, I wouldn't build against the v1 codebase. I don't plan on maintaining it.