lpnf
/
lovr
mirror of https://github.com/bjornbytes/lovr.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
lovr/.gitignore

43 lines
386 B
Plaintext
Raw Normal View History

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
Improve tup config; - Add config folder that contains tup config files. There is a default config added to source control, but everything else in that folder is gitignored so you can add your own custom configurations. - Remove and gitignore tup.config. - This results in the following setup: - You can now create a tup.config symlink that points at the config you want to use. - Or, you can use the `tup variant` command to manage multiple build configurations at the same time (e.g. debug, release, wasm).
2019-12-29 18:52:44 +00:00
tup.config
config/*
I can't into gitignore;
2020-01-01 02:23:56 +00:00
*.ttf.h
*.json.h
*.lua.h
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
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
/build.sh
/watch.sh
/debug.sh
Update .gitignore;
2019-12-20 11:48:53 +00:00
/db
Separate Lua API;
2016-08-10 06:28:17 +00:00
/lovr
Tup build system for android;
2020-05-29 22:27:49 +00:00
/lovr.apk
tup windows support;
2020-05-15 21:01:10 +00:00
/lovr.exe
/lovr.exp
/lovr.lib
tup win32 track pdb files;
2020-10-03 01:36:39 +00:00
/lovr.pdb
/lovr.ilk
tup: fully support web builds;
2020-03-04 03:27:58 +00:00
/lovr.js
/lovr.worker.js
/lovr.html
/lovr.wasm
Tup build system for android;
2020-05-29 22:27:49 +00:00
/classes.dex
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
build
build-*
Tup build system for android;
2020-05-29 22:27:49 +00:00
/lib
Rework Tupfiles; - One toplevel Tupfile that makes it more clear what happens. - Add config flags for -Werror, -fsanitize, and separate debug/optimize flags. - Automatically integrate with libs built by CMake (build folder, rpath, libs folder). - Disabling modules actually works, only the stuff that's needed is built.
2019-12-13 14:52:57 +00:00
/libs
Tup build system for android;
2020-05-29 22:27:49 +00:00
/org
/tmp
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
bin
No game screen;
2017-04-02 12:55:21 +00:00
/data
Update .gitignore;
2018-02-24 21:14:07 +00:00
/*.lua
Update .gitignore;
2017-01-05 07:57:11 +00:00
.DS_Store
Include .vs in .gitignore (visual studio code)
2019-12-18 00:50:51 +00:00
.vs
Increase specificity of 'test' gitignore;
2019-08-26 22:46:38 +00:00
/test
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: Move actions into resources;
2020-08-22 21:40:52 +00:00
deps/openxr
OpenXR Android stuff;
2020-08-30 01:45:52 +00:00
deps/OpenXR-Oculus
Plugins; - The plugins folder can contain native plugins. - CMake will build plugins with CMakeLists in them - They can check the LOVR variable to see if they are being built inside LOVR. - They can set the LOVR_PLUGIN_TARGETS variable to a list of targets they build. - If blank, all non-imported targets added in the folder will be used. - The libraries built by their targets will be moved next to the executable or into the apk. - The library loader now tries to load libraries next to the executable or in the APK. - It is "fixed function" now, this may be improved in the future. - The lovr.filesystem C require path has been removed. - enet and cjson have been removed. Use plugins.
2020-12-27 17:55:35 +00:00
/plugins/*