Scripts for project setup
proj_shell.bat - opens a cmd window where all scripts should be run within. Recommend double click to run.
proj_debugger.bat - opens a visual studio solution from the specified exe
> proj_debugger.bat ..\Build\TinkerApp.exe
or
> proj_debugger.bat ..\ToolsBin\TinkerSC.exe
Scripts that compile code
build_app_and_game_dll.bat - builds platform app exe and game dll into Build/
> build_app_and_game_dll.bat [Release | Debug] [VK | DX]
build_benchmarks.bat - builds benchmark exe into Build/.
> build_benchmarks.bat [Release | Debug]
build_app.bat - builds platform app exe into Build/
> build_app.bat [Release | Debug]
build_game_dll.bat - builds game dll into Build/. Note game dll hotloads!
> build_game_dll.bat [Release | Debug] [VK | DX]
build_server.bat - builds server exe into Build/
> build_server.bat [Release | Debug]
build_shadercompiler.bat - builds shader compiler exe into ToolsBin/
> build_shadercompiler.bat [Release | Debug] [VK | DX]
build_spirv-vm.bat - (.sh also exists) builds unit test exe into Build/
> build_spirv-vm.bat [Release | Debug]
build_tests.bat - builds unit test exe into Build/
> build_tests.bat [Release | Debug]
ez-build_release.bat - runs multiple release builds by simply calling the aforementioned scripts:
- build_app.bat Release VK
- build_shadercompiler.bat Release VK
- build_server.bat Release VK
- build_benchmarks.bat Release VK
- build_tests.bat Release VK
> ez-build_release.bat [Release | Debug]
Scripts that run built exe's
run_benchmarks.bat - runs the built benchmark exe
> run_benchmarks.bat
run_game.bat - runs the built Tinker engine exe
> run_game.bat
run_spirv-vm-demo.bat - runs the build spirv virtual machine exe
> run_spirv-vm-demo.bat
run_tests.bat - runs the built unit test exe
> run_tests.bat
timecmd.bat - runs your batch script and outputs the time it took to run. So far I used this for coarse build performance timing.
> timecmd.bat <your .bat> <args for your .bat>