You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently I am removing some ROS1 code from carma-utils and carma-platform.
Carma-platform itself has only carma_record and mock_drivers as ROS1.
However, due to how CMake and build script is written, it is still taking some non-trivial time to parse through each packages to determine whether to build or not. This can be optimized by not trying to build it in the first place.
See below how each package is almost taking 4s on my local VM before determining it is ROS2 and should not be built.
It is not a huge optimiziation, but something we probably can easily do if ROS1 is here to stay for a while.
Reasoning for new functionality
No response
The text was updated successfully, but these errors were encountered:
Summary
Currently I am removing some ROS1 code from carma-utils and carma-platform.
Carma-platform itself has only carma_record and mock_drivers as ROS1.
However, due to how CMake and build script is written, it is still taking some non-trivial time to parse through each packages to determine whether to build or not. This can be optimized by not trying to build it in the first place.
See below how each package is almost taking 4s on my local VM before determining it is ROS2 and should not be built.
It is not a huge optimiziation, but something we probably can easily do if ROS1 is here to stay for a while.
Reasoning for new functionality
No response
The text was updated successfully, but these errors were encountered: