Cross-platform tool for generating clean, testable FTC robot projects without editing the SDK installation. Features: - Standalone project generation with proper separation from SDK - Per-project SDK configuration via .weevil.toml - Local unit testing support (no robot required) - Cross-platform build/deploy scripts (Linux/macOS/Windows) - Project upgrade system preserving user code - Configuration management commands - Comprehensive test suite (11 passing tests) - Zero-warning builds Architecture: - Pure Rust implementation with embedded Gradle wrapper - Projects use deployToSDK task to copy code to FTC SDK TeamCode - Git-ready projects with automatic initialization - USB and WiFi deployment with auto-detection Commands: - weevil new <name> - Create new project - weevil upgrade <path> - Update project infrastructure - weevil config <path> - View/modify project configuration - weevil sdk status/install/update - Manage SDKs Addresses the core problem: FTC's SDK structure forces students to edit framework internals instead of separating concerns like industry standard practices. Weevil enables proper software engineering workflows for robotics education.
10 lines
317 B
Markdown
10 lines
317 B
Markdown
# File: tests/fixtures/mock-ftc-sdk/README.md
|
|
# Mock FTC SDK for testing
|
|
|
|
This directory contains a minimal FTC SDK structure for testing purposes.
|
|
|
|
Structure:
|
|
- FtcRobotController/ - Main controller module
|
|
- TeamCode/ - Where user code gets deployed
|
|
- build.gradle - Root build file
|
|
- gradlew - Gradle wrapper script |