Failed to build from source (#226)

Posted by @cwrx777:

OS: Ubuntu 22.04.1
ROS: Humble

Installed CCD from source

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_traffic_ros2: Cannot locate rosdep definition for [uuid-dev]

Error message:

...
Starting >>> rmf_traffic
Finished <<< rmf_traffic [1.76s]                        
Starting >>> rmf_traffic_ros2
--- stderr: rmf_traffic_ros2                            
CMake Error at CMakeLists.txt:27 (find_package):
  By not providing "Findnlohmann_json.cmake" in CMAKE_MODULE_PATH this
  project has asked CMake to find a package configuration file provided by
  "nlohmann_json", but CMake did not find one.

  Could not find a package configuration file provided by "nlohmann_json"
  with any of the following names:

    nlohmann_jsonConfig.cmake
    nlohmann_json-config.cmake

  Add the installation prefix of "nlohmann_json" to CMAKE_PREFIX_PATH or set
  "nlohmann_json_DIR" to a directory containing one of the above files.  If
  "nlohmann_json" provides a separate development package or SDK, be sure it
  has been installed.


---
Failed   <<< rmf_traffic_ros2 [1.64s, exited with code 1]

Summary: 11 packages finished [34.3s]
  1 package failed: rmf_traffic_ros2
  1 package had stderr output: rmf_traffic_ros2
  46 packages not processed


Chosen answer

Answer chosen by @cwrx777 at 2022-09-17T15:03:27Z.
Answered by @mxgrey:

Thanks for reporting these outputs; it’s valuable to see what kind of outcomes users are experiencing on their own machines.

I can’t think of any reason that installing libccd from source would cause any of the outputs that you’re reporting.

The complaint about uuid-dev means we used the wrong key name for the libuuid dependency in the package.xml. I’ve created a PR to fix this so please pull that and try it out at your earliest convenience.

I think the complaint about nlohmann_json missing shouldn’t happen if you have nlohmann_json_schema_validator_vendor in your colcon workspace and rosdep was run successfully for it. I suspect rosdep may have terminated prematurely because of the uuid-dev issue, so if you can try out the PR I linked and let me know if the issue persists, I would appreciate that.

Posted by @mxgrey:

Thanks for reporting these outputs; it’s valuable to see what kind of outcomes users are experiencing on their own machines.

I can’t think of any reason that installing libccd from source would cause any of the outputs that you’re reporting.

The complaint about uuid-dev means we used the wrong key name for the libuuid dependency in the package.xml. I’ve created a PR to fix this so please pull that and try it out at your earliest convenience.

I think the complaint about nlohmann_json missing shouldn’t happen if you have nlohmann_json_schema_validator_vendor in your colcon workspace and rosdep was run successfully for it. I suspect rosdep may have terminated prematurely because of the uuid-dev issue, so if you can try out the PR I linked and let me know if the issue persists, I would appreciate that.


This is the chosen answer.

Posted by @cwrx777:

Hi @mxgrey ,

The PR fixed the issue.
Thank you