This checks both gcc and clang on linux, but only clang on mac
Because there are so many debug warnings they are suppressed in a very hacky way:
Make is run first with error output ignored.
Then an incremental build is run which has the error output, but will only build the files that errored the first time (and will error again).
There is probably a better way to ignore the warnings in cmake, but I'm a bit hesitant to change the cmake files and I couldn't find a way to do it with command line arguments.
Only after writing this I found out that there is a CI pull request already: https://github.com/GarageGames/Torque3D/pull/2211
That older PR probably has more features (including running a windows build on appveyor, and I believe it runs the tests too) but this script is simpler.
We'll go ahead and roll this in for now(as mentioned, it's simpler) and can look to bringing over aspects of #2211 next to fully flesh out our CI setup.
This is essentially the same as #2289 but with a cleaner git history.
It follows the compilation steps from http://wiki.torque3d.org/coder:compiling-in-linux#toc11
This checks both gcc and clang on linux, but only clang on mac
Because there are so many debug warnings they are suppressed in a very hacky way: Make is run first with error output ignored. Then an incremental build is run which has the error output, but will only build the files that errored the first time (and will error again). There is probably a better way to ignore the warnings in cmake, but I'm a bit hesitant to change the cmake files and I couldn't find a way to do it with command line arguments.
Only after writing this I found out that there is a CI pull request already: https://github.com/GarageGames/Torque3D/pull/2211 That older PR probably has more features (including running a windows build on appveyor, and I believe it runs the tests too) but this script is simpler.