Important: this is a testing version, the stable version is coming soon
Pintos extension, go to pintos vscode docs for full documentation (in Spanish only. It's strongly recommend reading)
- Initial setup for PintOS
- Dev container with gbenm/pintos
- Run tests
- Debugger
- Git
- Docker (optional)
- Linux environment (windows needs docker for this)
- Editor Config extension
- C/C++ extension (in linux)
- Dev containers extension (if you use docker)
pintos.buildUtils
by defaulttrue
. Runscd utils && make
before execute "pintos health" commandpintos.addUtilsToPath
by defaulttrue
. Adds the localutils/
to PATH (only in this process, it doesn't change your config files)pintos.phases
the folders of the phases (probably you don't need to change it)pintos.useNodejsNativeKill
by defaultfalse
. When spawn make processes to grade, compile, etc. This spawn other children process, if you use the nativesubprocess.kill([signal])
only kill the parent process, to solve this the extension use tree-kill packagepintos.simulator
by defaultqemu
. The extension usesmake
to run the tests, but the debugger need to spawn a gdb server, in this moment extension need to use pintos CLI directly, for those cases, the extension needs to know what emulator should use.
pintos.baseRepository
the repo URL to get a snapshot of pintos codepintos.baseRepositoryCodeFolder
the folder containing the source code of PintOS, if your Git supports sparse checkout only clon the folder (with the original project the size will be reduced from 30MB to ~11MB)pintos.personalRepoUrl
the Url of your personal repository
Extension icon by Flat Icons - Flaticon