4. Creating a Workspace

If code is available, a .vscode directory with all needed configurations is generated when running waf configure. The generated workspace is properly configured.

4.1. Launching code

It is best to use the provided launcher script ide.bat to open code as then all environment variables are automatically correctly set.

If using the launcher scripts is not desired the following steps need to be taken into account:

  1. All required build tools etc. need to be in path and environment variables need to be correctly set.

  2. Open code.

  3. Goto File->Open Folder and select the cloned foxBMS 2 repository.

4.2. Build Tasks

Build commands are executed by running Build Tasks. A Build Task is executed either selecting Terminal->Run Build Task from the menu or pressing Ctrl + Shift + B. A list of possible build commands is shown and the desired one can be executed by clicking with the cursor or navigating with the arrow keys and pressing Enter.

4.3. Test Explorer

With the Test Explorer (which is listed among the recommended extensions) you can directly interact with the Ceedling unit tests. The Test Explorer is found in the activity bar under Test.

4.4. Hints

These are the default shortcuts in code. They can be adapted to fit the user’s needs.

  1. Jumping to definition: F12

  2. Show all references: Shift + F12

  3. Find file: Ctrl + P

  4. Open command palette: Ctrl + Shift + P

  5. Search within active file: Ctrl + F

  6. Search within whole project: Ctrl + Shift + F

  7. Run Build Tasks: Ctrl + Shift + B

  8. Open header file to active source file: Alt + O

  9. Navigate history: Ctrl + Tab

  10. Navigate back: Alt + Left

  11. Navigate forward: Alt + Right