lovr/src/Tupdefault

include_rules

: foreach *.c | $(ROOT)/src/resources/*.h |> !compile |>
Add tup build system; It's still a rough draft and likely only works on my machine, but can be improved over time. Rough explanation: - tup.config contains high-level build configuration defaults. - Tuprules.tup contains mostly compiler flags (generated from the tup.config) and declares some macros used to compile code. - Tupfile takes all generated object files and links them into the lovr executable. - src/Tupdefault defines the default build steps for src and all subdirectories, which is to compile all .c files to .o files and put them in the <objects> bucket for linking by the toplevel Tupfile. It's possible to have multiple configs active at once for different platforms, projects, etc. To do this, create a folder for each build variant you want, and place a tup.config in each folder (it can be a symlink, which is helpful). Then, invoking `tup` will build all your variants, or you can build a specific one by doing `tup <foldername>`. 2019-06-10 10:41:31 +00:00			`include_rules`

			`: foreach .c \| $(ROOT)/src/resources/.h \|> !compile \|>`