Posted by @ss2080:
following error was occurred ( Ubuntu 22.04 LTS clean installed & ROS2 humble installed)
Any help would be appreciated.
$rosdep install --from-paths src --ignore-src --rosdistro humble -y
ERROR: the following packages/stacks could not have their rosdep keys resolved
to system dependencies:
rmf_demos_gz: Cannot locate rosdep definition for [ros_ign_bridge]
Chosen answer
Answer chosen by @ss2080 at 2022-09-16T03:20:58Z.
Answered by @Yadunund:
Hi there! Could you re-run the rosdep update command and try again? Let us know if the problem persists
Posted by @Yadunund:
Hi there! Could you re-run the rosdep update command and try again? Let us know if the problem persists
This is the chosen answer.
Posted by @ss2080:
I did rosdep update but the same error occurred.
Edited by @ss2080 at 2022-09-15T14:44:00Z
Posted by @aaronchongth:
This is an interesting issue, I recently performed a dist-upgrade from 20.04 to 22.04 without running rosdep update for a while now, and I was able to perform rosdep install thanks to it still using the one from galactic, rosdistro/galactic/distribution.yaml at master · ros/rosdistro · GitHub. For humble it looks like it still has not been added to the rosdep distribution, rosdistro/humble/distribution.yaml at master · ros/rosdistro · GitHub. (Edit: once I ran rosdep update I was facing the same issue as well)
I believe once ros_gz: 0.244.6-1 in 'humble/distribution.yaml' [bloom] by ahcorde · Pull Request #34557 · ros/rosdistro · GitHub gets merged, this issue will resolve itself. For the time being, could you run sudo apt install ros-humble-ros-ign-bridge manually? This will probably apply if more packages related to ros_gz: 0.244.6-1 in 'humble/distribution.yaml' [bloom] by ahcorde · Pull Request #34557 · ros/rosdistro · GitHub gets flagged.
Edited by @aaronchongth at 2022-09-15T16:00:05Z
Posted by @ss2080:
“sudo apt install ros-humble-ros-ign-bridge” solved the error but another error occured at colcon build step as follows.
$colcon build --mixin “release lld”
usage: colcon [-h] [–log-base LOG_BASE] [–log-level LOG_LEVEL]
{acceleration,alias,build,coveragepy-result,edit,extension-points,extensions,graph,info,lcov-result,list,metadata,mixin,rerun,test,test-result,version-check}
…
colcon: error: Mixin ‘release lld’ is not available for ‘build’
Posted by @aaronchongth:
Apologies there is a mistake in the documentation, please these instead. Note that there is no " wrapping the 2 mixin names, and the correct environment variable is CC not CX
export CXX=clang++
export CC=clang
colcon build --mixin release lld
Edited by @aaronchongth at 2022-09-15T16:36:58Z
Posted by @ss2080:
colcon build was started with CC=clang and no " wrapping but finally I got following outputs from console (28 packages had stderr output ).
All console outputs is here: https://gist.github.com/ss2080/ee1a1355209dc7e339c2a69a8f791ee5
Summary: 58 packages finished [45min 18s]
28 packages had stderr output: ament_cmake_catch2 menge_vendor nlohmann_json_schema_validator_vendor pybind11_json_vendor rmf_api_msgs rmf_building_map_tools rmf_building_sim_common rmf_building_sim_gz_plugins rmf_demos_bridges rmf_demos_dashboard_resources rmf_demos_fleet_adapter rmf_demos_maps rmf_demos_panel rmf_demos_tasks rmf_fleet_adapter rmf_fleet_adapter_python rmf_robot_sim_gz_plugins rmf_task rmf_task_ros2 rmf_task_sequence rmf_traffic rmf_traffic_editor rmf_traffic_editor_assets rmf_traffic_editor_test_maps rmf_traffic_ros2 rmf_visualization_building_systems rmf_visualization_rviz2_plugins rmf_visualization_schedule
Posted by @aaronchongth:
@ss2080 that looks good! Most of them are minor compilation warnings which we will attempt to reduce over time. Your workspace has been built, and the fix to documentation has been merged, Fixing clang CC variable, mixin without apostrophes by aaronchongth · Pull Request #225 · open-rmf/rmf · GitHub. Please mark this question as answered.
Posted by @ss2080:
@aaronchongth I could run Office World demo.
Thank you for your prompt response!!