lovr/.gitignore

.DS_Store
.vs
.tup
.obj
bin
build*
plugins
*.*.h
*.lua
*.config
Activity*.java
AndroidManifest*.xml
deps/VrApi
deps/pico
deps/OpenXR-Oculus
tup: output to bin folder; toplevel config; 2021-02-02 06:48:15 +00:00			`.DS_Store`
			`.vs`
Initial commit; 2016-07-07 07:04:24 +00:00			`.tup`
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			`.obj`
tup: output to bin folder; toplevel config; 2021-02-02 06:48:15 +00:00			`bin`
			`build*`
			`plugins`
			`..h`
			`*.lua`
			`*.config`
mv Activity.java Activity_vrapi.java; 2020-07-27 18:49:41 +00:00			`Activity*.java`
Android: Organize tup rules; Fix manifest; 2020-06-25 19:27:18 +00:00			`AndroidManifest*.xml`
vrapi gitignore case sensitivity; 2020-07-27 19:48:06 +00:00			`deps/VrApi`
Start pico headset backend; 2020-07-27 19:58:52 +00:00			`deps/pico`
OpenXR Android stuff; 2020-08-30 01:45:52 +00:00			`deps/OpenXR-Oculus`