VSCode

TODO: VSCode

Modifications: Feel free to change the provided workspace settings and install additional extensions, but be aware of the fact, that the contents of the .vscode directory is overwritten every time you run CMake. As a workaround you might want to change the templates for the VSCode configuration which can be found in config/vscode/ or if required comment the related configure_file statements out in the files init_local_projects.cmake and init_remote_projects.cmake.

Caveats using VSCode for Remote Development

While this approaches allow you to development in your normal system (f.e. Windows OS) with few slowdowns when editing files and navigating though the project, The performance when building and running the emulator isn’t that great due to the overheads of the remote development setup.

Especially starting a Debugging session takes some time as a gdbserver has to be launched on the Guest every time before entering the Debug Console is possible.

While the Docker-based setup is way more lightweight that the VirtualBox image, there are additional latencies running most of the make targets, as they first have to ensure that the latest version of the container image is downloaded and booted.

At the moment, it is not possible to have a look at the SYSOUT of the running executable, so you have to rely on the possibility to print out variable contents inside the GDB (Debugger) console or display them using Drawing statements.