summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKonAki <konaki@anokonaki.org>2026-10-17 13:47:41 +0800
committerKonAki <konaki@anokonaki.org>2026-10-17 13:47:41 +0800
commit61ea96c953728f034cb766fe44f5419e4f679795 (patch)
tree00e70027916ed951377009ce078071fa47c551a0
parentff67f703fbdbb4d0239594213dfba6b6b0dcc702 (diff)
readme: building with build.c
-rw-r--r--README.md11
1 files changed, 10 insertions, 1 deletions
diff --git a/README.md b/README.md
index dfd6e68..238c648 100644
--- a/README.md
+++ b/README.md
@@ -69,7 +69,7 @@ The 3D part of konsofren (cameras, triangles, meshes, billboards, fog) is only c
- linux
- bsd
-- windows (cross compiled with mingw, not tested much yet)
+- windows (build.c with gcc or clang from w64devkit or llvm-mingw, or cross compiled with mingw, not tested much yet)
- web (planned)
## Usage
@@ -101,6 +101,15 @@ targets are `all`, `run`, `clean`, `tools`, `pack` and `examples`.
If you'd rather use make directly, the [Makefile](Makefile) is a normal one. The script just sets the flags and calls it. It was made to stay as POSIX as I can.
+No sh or make, for example on Windows? [build.c](build.c) does the same job with only a C compiler. It takes the same options and targets, and rebuilds itself when it changes:
+
+```sh
+cc -o build build.c
+./build -m font,assets,image,audio
+```
+
+It uses [konbuild.h](kon/konbuild.h), a small single header for build programs written in C. build.sh and build.c are kept to the same module list, so when you add a module add it in both.
+
### Your own program
The shortest way to a window is konprogram: