Autoware.Auto - Config.cmake file not found during colcon build
Workstation: Ubuntu 18.4, Docker version: 19.03.12, ROS: ROS2 Dashing
Task: Building Autoware.Auto in a docker container with the instructions from the documentation: https://autowarefoundation.gitlab.io/...
When entering the command "colcon build" the following error message appears before the installation is aborted:
CMake Error at CMakeLists.txt:19 (find_package): By not providing "Findament_cmake_auto.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "ament_cmake_auto", but CMake did not find one.
Could not find a package configuration file provided by "ament_cmake_auto" with any of the following names:
ament_cmake_autoConfig.cmake
ament_cmake_auto-config.cmake
Add the installation prefix of "ament_cmake_auto" to CMAKE_PREFIX_PATH or set "ament_cmake_auto_DIR" to a directory containing one of the above files. If "ament_cmake_auto" provides a separate development package or SDK, be sure it has been installed.
The installed ROS version is ROS 2 Dashing - installed according to this documentation: https://index.ros.org/doc/ros2/Instal...
Although the error message is very descriptive, I do not think that it would be the right approach to edit any source files from the original autoware code, since that should run "out of the box". From my understanding the path to the requested config files should be in the variable "CMAKE_MODULE_PATH", but the package should do that automatically.
I did make sure to source the ROS2 env setup via source /opt/ros/dashing/setup.bash. Thus all ROS2 packages should be available. What am I missing? Is this a known issue in either ROS2 or Autoware.Auto? Any feedback is welcome.
--update-- I confirmed that ROS2 commands are running in ADE by running a simple sender / listener command. But when trying to source the setup.bash file within ADE I get the error
bash: /home/jpalo/ros2_dashing/install/setup.bash: No such file or directory
But the file is there, and when I am outside of ADE the command works. There might be a reference to this issue https://github.com/ros2/ros2/issues/653.
Regarding my last comment: the problem was solved by un-installing the source installation of ros2 and relying solely on the ros2 environment integrated in ade. The command "which ros2" returns the path that also contains the setup.bash file. The colcon build problem is persistent.
It is correct, thank you. I'm using binariy installation ROS2. It works to run"which ros2" before running "colcon build"