Closed LeonBrands closed 2 years ago
note that there are no current protections on develop - this PR is not a git-flow requirement, but exists nonetheless for receiving feedback on the current status of the build system. Do not merge after a single accepted review, I will do so when all (or sufficient) reviews are done
note that there are no current protections on develop - this PR is not a git-flow requirement, but exists nonetheless for receiving feedback on the current status of the build system. Do not merge after a single accepted review, I will do so when all (or sufficient) reviews are done
would you prefer working on this through the default git use and PR workflow? since I removed all protections for any hard changed you had to make or cases where you had to force git to do what you want. but i feel like we've gotten past that by now? I could setup the branch protection back up again.
@GlynLeine leave it off for now, I might need to do some more work where gitflow will just get in the way. Am kind of selectively picking things that I want reviewed right now
Sets up the basic build system for rythe engine/editor - The current system detects modules and allows enabling them through CMake flags. If a module is enabled, a matching editor module will be attempted to be enabled as well.
Header files and library files are copied to the appropriate include/ and lib/ folders.
This version contains no applications, tests, or docs of any form yet.