If the path to your numpy installation may change.
This can happen e.g. if you want to cross-compile ROS2 and want to do it on some CICD setups.
The issue is that right now, e.g. for std_msgs export_std_msgs__rosidl_generator_pyExport.cmake sets the INTERFACE_INCLUDE_DIRECTORIESproperty of std_msgs::std_msgs__rosidl_generator_py to an absolute path (which causes issues if the folder of your numpy installation changes.
With this patch all include directories are consistently added PRIVATE instead of PUBLIC. There shouldn't be a need to expose them anyways.
This helps in situations in which:
This can happen e.g. if you want to cross-compile ROS2 and want to do it on some CICD setups.
The issue is that right now, e.g. for
std_msgs export_std_msgs__rosidl_generator_pyExport.cmake
sets theINTERFACE_INCLUDE_DIRECTORIES
property ofstd_msgs::std_msgs__rosidl_generator_py
to an absolute path (which causes issues if the folder of your numpy installation changes.With this patch all include directories are consistently added
PRIVATE
instead ofPUBLIC
. There shouldn't be a need to expose them anyways.