This adds the base 4coder core repository and the non-source repository as git sub-trees, maintaining their respective commit histories. Simplifying the setup process for new users, and centralizes the codebase.
This is a pretty chunky list of changes, so its probably best to verify that it still builds for you both by checking out the branch.
it essentially reorganizes the repo such that the dion-systems/4coder repo is within 4cc/code
and the dion-systems/4coder-non-code is within the 4cc/non-code directory.
The .gitignore ignores the build artifacts generated in, what will be, the 4cc/build, 4cc/distributions, and 4cc/current_dist_[super/demo]_[x64/x86] directories. Along with relevant changes to the build.cpp file.
If either of you are on linux, please lmk if this breaks anything. I think most of the changes required to maintain building are contained in the 4coder_build.cpp but things could get funky.
This adds the base 4coder core repository and the non-source repository as git sub-trees, maintaining their respective commit histories. Simplifying the setup process for new users, and centralizes the codebase.
This is a pretty chunky list of changes, so its probably best to verify that it still builds for you both by checking out the branch. it essentially reorganizes the repo such that the
dion-systems/4coderrepo is within4cc/codeand thedion-systems/4coder-non-codeis within the4cc/non-codedirectory. The .gitignore ignores the build artifacts generated in, what will be, the4cc/build,4cc/distributions, and4cc/current_dist_[super/demo]_[x64/x86]directories. Along with relevant changes to the build.cpp file. If either of you are on linux, please lmk if this breaks anything. I think most of the changes required to maintain building are contained in the4coder_build.cppbut things could get funky.We will also have to deal with mac at some point.