https://github.com/gbenm/pintos-vscode

vscode extension for PintOS project
https://github.com/gbenm/pintos-vscode

debugging debugging-tool devcontainers pintos testing testing-tools vscode vscode-extension

Last synced: about 1 month ago
JSON representation

vscode extension for PintOS project

• Host: GitHub
• URL: https://github.com/gbenm/pintos-vscode
• Owner: gbenm
• License: mit
• Created: 2022-09-23T05:14:59.000Z (over 2 years ago)
• Default Branch: main
• Last Pushed: 2023-01-06T16:19:33.000Z (almost 2 years ago)
• Last Synced: 2023-03-04T03:03:58.755Z (almost 2 years ago)
• Topics: debugging, debugging-tool, devcontainers, pintos, testing, testing-tools, vscode, vscode-extension
• Language: TypeScript
• Homepage: https://gbenm.github.io/pintos-utils/pintosvsc
• Size: 34.1 MB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# PintOS vscode

> **Important:** this is a testing version, the stable version is coming soon

Pintos extension, go to [pintos vscode docs](https://gbenm.github.io/pintos-utils/pintosvsc)

for full documentation (in Spanish only. It's strongly recommend reading)

## Features

- Initial setup for PintOS

- Dev container with [gbenm/pintos](https://hub.docker.com/r/gbenm/pintos)

- Run tests

- Debugger

## Requirements

- Git

- Docker (optional)

- Linux environment (windows needs docker for this)

- Editor Config extension

- C/C++ extension (in linux)

- [Dev containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) (if you use docker)

## Extension Settings

- `pintos.buildUtils` by default `true`. Runs `cd utils && make` before execute "pintos health" command

- `pintos.addUtilsToPath` by default `true`. Adds the local `utils/` 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 default `false`. When spawn make processes to grade, compile, etc. This spawn other children process, if you use the native `subprocess.kill([signal])` only kill the parent process, to solve this the extension use [tree-kill](https://www.npmjs.com/package/tree-kill) package

- `pintos.simulator` by default `qemu`. The extension uses `make` 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.

### They're used as default for configuration (confirmation is always requested)

- `pintos.baseRepository` the repo URL to get a snapshot of pintos code

- `pintos.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

## Credits

Extension icon by [Flat Icons](https://www.flaticon.com/authors/flat-icons) - [Flaticon](https://www.flaticon.com)