Due to the limitations of vexcode (the now defunct vex editor) we had to do some strange things to get include paths to work (Basically we couldn't change the include path of the editor so intellisene was alwayws messed up). We are now free from vexcode and use vscode going forward.
The old version meant we had to abuse relative imports to get at core #include "../../../core/include/thing_we_want.h.
Now that we have control over include paths, we can add core/include to the include path and (with some updates) import headers as #include "core/thing_we_want.h" - a much nicer to use system that many large c++ libraries suggest.
[ ] Add updated include paths to makefile
[ ] Add updated include paths to the vscode settings file
Due to the limitations of vexcode (the now defunct vex editor) we had to do some strange things to get include paths to work (Basically we couldn't change the include path of the editor so intellisene was alwayws messed up). We are now free from vexcode and use vscode going forward. The old version meant we had to abuse relative imports to get at core
#include "../../../core/include/thing_we_want.h. Now that we have control over include paths, we can addcore/includeto the include path and (with some updates) import headers as#include "core/thing_we_want.h"- a much nicer to use system that many large c++ libraries suggest.