haloopdy/3dtoys
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases 2 Wiki Activity

Some clarifications

Browse Source
This commit is contained in:
Carlos Sanchez 2024-08-12 22:03:55 -04:00
parent 8a2648c171
commit d4886f2ff2
2 changed files with 8 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
Makefile
View File

@ -12,7 +12,7 @@ full:
echo "Please specify a sample to build (ends with .exe)" echo "Please specify a sample to build (ends with .exe)"
$(HALOOLIB): $(HALOOLIB):
cd haloo3d && make full cd haloo3d && $(MAKE) full
# Rule to build .o files in main folder # Rule to build .o files in main folder
$(BUILDD)/%.o: %.c %.h $(BUILDD)/%.o: %.c %.h

10
README.md
View File

@ -22,13 +22,17 @@ include all your .c files into the main file, in the right order.
This may change in the future. 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 ## Haloo3d
You can compile haloo3d using the provided makefile, or include the You can compile haloo3d using the makefile provided in the library
.h and .c files directly into the main translation unit like unigi repo, or include the .h and .c files directly into the main
currently expects. translation unit like unigi currently expects.
For these samples, they expect you to build the `haloo3d_full.a` For these samples, they expect you to build the `haloo3d_full.a`
library using `make full` in the haloo3d submodule. For convenience, library using `make full` in the haloo3d submodule. For convenience,
the makefile for the samples assumes you are using the submodule the makefile for the samples assumes you are using the submodule
and runs make in there for you. and runs make in there for you.