Skip to content

feat: removed visualizers and updated build.#258

Open
iandareid wants to merge 2 commits into
mainfrom
seperate-simulation-visualizers
Open

feat: removed visualizers and updated build.#258
iandareid wants to merge 2 commits into
mainfrom
seperate-simulation-visualizers

Conversation

@iandareid

Copy link
Copy Markdown
Contributor

I have separated the visualizers from the rest of the repo. They are now 3 seperate repos in the rosflight org. These are selectively cloned by the user based on their needs. Now the standalone is the only visualizer that ships with rosflight.

@iandareid iandareid self-assigned this Jun 5, 2026

@JMoore5353 JMoore5353 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this will be a great fix, and will help reduce some of the build times.

Comment thread rosflight_sim/package.xml
<depend>rclcpp</depend>
<depend>rclpy</depend>

<depend condition="$ROS_DISTRO == 'humble'">gazebo_dev</depend>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we make sure users get these deps when they are using Gazebo classic? I briefly glanced at the rosflight_viz_gazebo_classic, but didn't see a fix (just a warning). These tags are needed to successfully install deps for GZ classic when doing the "rosdep install ..." command.

@@ -0,0 +1,3 @@
# Using Other Visualizations.

To use another visualizer, git clone one of the `rosflight_viz_*` repos from the ROSflight organization on GitHub into this repo and build as normal.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is nitpicky. Could we maybe move this READme to the top level rosflight_ros_pkgs readme? Otherwise I could see people having a hard time finding it.

We should also tell them exactly which directory to clone the rosflight_viz_* packages into, to avoid confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants