This website requires JavaScript.
Explore
Help
Register
Sign In
lpnf
/
lovr
mirror of
https://github.com/bjornbytes/lovr.git
Watch
1
Star
0
Fork
You've already forked lovr
0
Code
Issues
Projects
Releases
Wiki
Activity
9b0e43b249
lovr
/
.gitignore
14 lines
96 B
Plaintext
Raw
Normal View
History
Unescape
Escape
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
*.config
/build.sh
/watch.sh
/debug.sh
Separate Lua API;
2016-08-10 06:28:17 +00:00
/lovr
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-*
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