fix ./run finction

[hakuturu583]

Status

DEVELOPMENT

Description

autowarefoundation/autoware_ai#585

Related PRs

#2004

Todos

• Tests
• Documentation

Steps to Test or Reproduce

Build Autoware with colcon or

catkin_make -DCMAKE_BUILD_TYPE=Release install

./run

[mitsudome-r]

I have confirmed that runtime manager starts up properly with ./colcon_release and ./run

[gbiggs]

Why do you need to run colcon_release before launching the runtime manager? Did you test with a more standard colcon build; colcon install approach?

[amc-nu]

@gbiggs Runtime Manager depends on autoware_msgs.

[mitsudome-r]

@gbiggs
Thank you for your advice.

I used colcon_release script because I thought that the script is the replacement of catkin_make_release, which Autoware Build Instruction tells the users to use.
I thought that this would be the most "basic" way to build Autoware(at least for the first time).
https://github.com/CPFL/Autoware/wiki/Source-Build

Also, the error won't be reproduced just by running colcon build; colcon install if the user has done catkin_make before colcon bulid. The script will make sure that "devel" directory is deleted before running colcon build. (Although I think this operations should be removed in colcon_release script because the directory is not related to colcon.)

Anyway, you are correct that normal colcon users would be more familiar with your commands, so I just tested with your commands and checked that it works fine.

[hakuturu583]

@mitsudome-r Thank you for review!!

[amc-nu]

@mitsudome-r CMakeLists.txt created by catkin_make will cause colcon build to fail. For this reason colcon_release script removes the conflicting file. Read here

Many users didn't know about this, so it was added here and improved here

The instructions in the wiki are for master branch. These will be updated once the 1.11 is released.

[sgermanserrano]

@hakuturu583 @mitsudome-r @amc-nu when building using colcon instead of catkin a setup.bash and a local_setup.bash files are created.
Using local_setup.bash is the suggested method in https://colcon.readthedocs.io/en/released/user/quick-start.html.
setup.bash will also source the parent workspace, /opt/ros/DISTRO, while this would not lead to compatibility problems at the moment, I believe it might lead to issues down the line when .Auto is also part of .Ai since /opt/ros2/DISTRO will also be sourced.
Sourcing local_setup.bash seems to me like a safer way to go