-
Notifications
You must be signed in to change notification settings - Fork 8
Directory Structure
This is a brief guide on the directory layout of taproot.
Contains the CI Docker image and build tools.
Contains VSCode project settings and tasks for building code through the VSCode interface.
Contains tooling used to build generated code. Files in this directory may be generated and used in projects that utilize taproot.
Contains all the relevant information necessary for building the generated documentation using Exhale.
A submodule (embedded git repository) of modm, used during code
generation.
Contains python and shell scripts that are either useful for developers or are used during CI builds.
Contains all header and source files that are a part of taproot.
Contains all tests for taproot that validate the correctness of the library code.
Contains a test project that taproot. It can be used for basic testing and as a generation/build smoke-test. However, changes made by ARUW members should typically be tested in the context of aruw-mcb before being merged here.
Looking for something else or would like to contribute to the wiki?
This wiki is a readonly mirror of our GitLab wiki. We use mermaid diagrams in this wiki, which are not supported in GitHub. We recommend referring to the GitLab wiki for the best experience or if you would like to contribute.
Architecture Design
- Directory Structure
- Build Targets Overview
- Drivers Architecture
- Command Subsystem Framework
- Generated Documentation
Using Taproot
Software Tools
- Docker Overview
- Debugging Safety Information
- Debugging With ST-Link
- Debugging With J-Link
- Git Tutorial
- How to Chip Erase the MCB
RoboMaster Tools
Software Profiling
System Setup Guides
- Windows Setup
- Debian Linux Setup
- Fedora Linux Setup
- macOS Setup
- Docker Container Setup
- (deprecated) Windows WSL Setup
Control System Design Notes
Miscellaneous and Brainstorming
Submit edits to this wiki via the taproot-wiki-review repo.