Remove use of ament_target_dependencies#3708
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3708 +/- ##
==========================================
- Coverage 46.22% 0.00% -46.21%
==========================================
Files 726 515 -211
Lines 59503 46480 -13023
Branches 7623 6025 -1598
==========================================
- Hits 27499 0 -27499
- Misses 31836 46480 +14644
+ Partials 168 0 -168 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Thanks for the effort! I tested that branch locally and it compiled fine and was usable. (Tested the RViz path planning plugin with an existing moveit config). @nbbrooks Do you need any help in finishing this? |
0b98baf to
caf50c1
Compare
|
With the current version I get a different build error than the CI job: |
|
Interesting, what OS and version of ros2 are you on? I guess this would be ros2 rolling. Are you building anything from source other than moveit2? |
I'm using Ubuntu 24.04 with Rolling. I have a ros2_control master-source build as an underlay, but I don't think, this is affecting this. My main assumption would be that this comes from the fact that I have both, Qt5 and Qt6 installed on my system (Which may be the case for many users, though not the build farm) My workspace: |
|
Hmmm sounds like ros2/rviz#1689 but I thought I had some cmake code to cover that case in my moveit2 qt6 pr |
|
I thought so, as well looking at the changes and the previous version before the rebase also worked for me. You removed finding rviz2. This, the check for Which seems like something, I have seen before. |
That is ....odd. I would have expected qt5 v. qt6 issues in the version before the rebase. Do you think it was compiling for Qt5 in that version, despite the rviz2 change? |
|
I did a clean build today with the version from fe0fc9d and it compiled and was usable :-) I noticed, that using the dropdown menus for selecting a start / goal state in the MotionPlanning RViz plugin did not work, though. That might be Qt6-related, hence I am mentioning it here. Edit: I noticed the following output Edit 2: This solved it for me: diff --git a/moveit_ros/visualization/motion_planning_rviz_plugin/src/motion_planning_frame.cpp b/moveit_ros/visualization/motion_planning_rviz_plugin/src/motion_planning_frame.cpp
index 81ba5e291..b187078c4 100644
--- a/moveit_ros/visualization/motion_planning_rviz_plugin/src/motion_planning_frame.cpp
+++ b/moveit_ros/visualization/motion_planning_rviz_plugin/src/motion_planning_frame.cpp
@@ -119,9 +119,9 @@ MotionPlanningFrame::MotionPlanningFrame(MotionPlanningDisplay* pdisplay, rviz_c
connect(ui_->execute_button, SIGNAL(clicked()), this, SLOT(executeButtonClicked()));
connect(ui_->plan_and_execute_button, SIGNAL(clicked()), this, SLOT(planAndExecuteButtonClicked()));
connect(ui_->stop_button, SIGNAL(clicked()), this, SLOT(stopButtonClicked()));
- connect(ui_->start_state_combo_box, SIGNAL(activated(QString)), this, SLOT(startStateTextChanged(QString)));
- connect(ui_->goal_state_combo_box, SIGNAL(activated(QString)), this, SLOT(goalStateTextChanged(QString)));
- connect(ui_->planning_group_combo_box, SIGNAL(currentIndexChanged(QString)), this,
+ connect(ui_->start_state_combo_box, SIGNAL(textActivated(QString)), this, SLOT(startStateTextChanged(QString)));
+ connect(ui_->goal_state_combo_box, SIGNAL(textActivated(QString)), this, SLOT(goalStateTextChanged(QString)));
+ connect(ui_->planning_group_combo_box, SIGNAL(currentTextChanged(QString)), this,
SLOT(planningGroupTextChanged(QString)));
connect(ui_->database_connect_button, SIGNAL(clicked()), this, SLOT(databaseConnectButtonClicked()));
connect(ui_->save_scene_button, SIGNAL(clicked()), this, SLOT(saveSceneButtonClicked())); |
Description
Address removal of ament_target_dependencies in ament/ament_cmake#614
Checklist