Repository navigation
Conversation
Sentry and aerial used sentry_ref for the same RobotGameRefereePack that every other robot publishes on robot_game_ref. The NUC navigation bridge must switch together: QDU-VRobot/ROS2_LIBXR#1.
User/xrobot_main.hpp is generated from User/xrobot.yaml and xrobot.lock and now committed; LibXR refuses to build it once either input changes. CI regenerates app_main.cpp, libxr_config.yaml, the entry and Modules/CMakeLists.txt from the committed inputs with the locked module commits (--frozen) and fails when they differ from the commit. Registrations follow the generated object order; the unused device_aliases table is gone. LibXR pinned to the stamp check.
Only indentation of list items changes (xrobot format); values, comments and order are untouched.
Positional parameter values of structs defined in the Module headers (RMMotor/DMMotor Param, launcher and chassis parameters) become mappings with field names; fields a positional value omitted keep their default member initializers explicitly. hero's instances Gimbal and EventBinder become gimbal and event_binder (ids may not repeat class names).
Install the XRobot and CodeGenerator versions pinned in modules.yaml and libxr_config.yaml; check the CodeGenerator outputs and the config layout; resolve the lock frozen with the release-line gate of the target branch; select each product with xrobot gen. The generated entry, module list and lock are no longer diffed. Release assets are read from the artifact's dist layout.
modules.yaml pins xrobot 1.0.0 and libxr_config.yaml pins the generator 6.0.0; CI installs exactly these. User/xrobot_main.hpp and Modules/CMakeLists.txt are produced by xrobot setup and are no longer committed. Remove the STATIC_CANDIDATE.md task notes.
The call moves from User Code 3 to right after it, where the generator now writes it (and refuses to regenerate while a user region still contains it).
…ecks LibXR now requires the generated module list, checks the entry header against the files it lists, prints the selected product, rejects RawData callback payloads and keeps init-time topic type checks in Release.
Gimbal takes its subscribed euler/gyro topic names from Param: omni_infantry_3/4 and sentry name the topics their AHRS publishes (gimbal_euler, gimbal_gyro), which the hard-coded names never matched; aerial and hero keep ahrs_euler and bmi088_gyro. xrobot.lock pins the Module feature heads these configs were checked against.
… LICENSE Rewrite the README for xrobot setup/gen, product selection and BSP object regeneration. Merge the still-valid content of Modules/AGENTS.md, User/AGENTS.md and master's CLAUDE.md and .claude/skills into one root AGENTS.md for the static assembly model; it supersedes those files and is excluded from source archives. License the repository under Apache-2.0 and list the vendored third-party code with its own licenses in NOTICE.
The script still called xrobot_gen_main, which XRobot 1.0 removed, so it stopped at the PATH check. It now requires the xrobot command and runs `xrobot gen -c <config>`; the usage example names an existing config.
USB goes through LibXR's own stack. Only six *_template files (and, in bsp-dev-c, the library's LICENSE.txt) were left over from before the switch; nothing builds or includes them, the .ioc enables no USB_DEVICE middleware, and STM32CubeMX does not recreate them when the project is generated again. They carried ST's SLA0044 license, which NOTICE listed as if the library were in use; the entry goes with them.
Chassis, Gimbal, the launchers, Dart, MiniGimbal and SuperPower now take the names of the topics they subscribe to as parameters instead of fixed strings; `xrobot sync` added them with their defaults (the names used before), so the links do not change. The lock follows the Module heads. All ten products build.
# Conflicts: # .gitattributes
Normalize line endings
Merge the XRobot 1.0 migration into dev
XRobot 1.0: merge feat/static-assembly-20260915 into dev
The README keeps this BSP's own values and links the LibXR.CMake rules and the shared CI to the website. The directory listing is a text block as in the other BSPs, commands carry no prompt, the configuration link points to the format page, and regeneration uses libxr stm32 setup, which leaves an unchanged project untouched; AGENTS.md no longer calls it a one-time command. Section 1 lists the 0.x aliases with the object names that replace them.
Apply the pre-release audit recommendations (audit/apply-20261004)
…e used, xrobot.lock on the released Modules
Release: LibXR V2.0.0 and the released tools
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release step 6 of RELEASE.md in xrobot-org/XRobot.