uros/rcl: RCL_COMMAND_LINE_ENABLED requires RCL_LOGGING_ENABLED?

[gavanderhoorn]

(not sure whether this is the correct venue, but micro-ROS/rcl doesn't have the tracker enabled)

Just wanted to ask whether micro-ROS/rcl/rcl requires RCL_LOGGING_ENABLED if RCL_COMMAND_LINE_ENABLED is enabled?

I'm running into unresolved symbol errors when loading a binary linked against a libmicroros.a which was built with RCL_LOGGING_ENABLED:OFF and RCL_COMMAND_LINE_ENABLED:ON (to get access to rcl_parse_arguments(..)).

Specifically: rcl_log_levels_fini, rcl_log_levels_copy, rcl_log_levels_init, rcl_log_levels_shrink_to_size, rcl_get_zero_initialized_log_levels and rcl_log_levels_add_logger_setting, which all appear to be used in rcl/arguments.c (rcl_get_zero_initialized_log_levels() here for instance).

(transferred from #557)

[pablogs9]

RCL_COMMAND_LINE_ENABLED is not intended to be enabled in micro-ROS as far as the is no CLI handling in micro-ROS.

[gavanderhoorn]

I understand.

But it seems to be necessary to get access to rcl_parse_arguments(..), which is needed to get remapping working (at least until ros2/rcl#998 is addressed).

Would you know of another way to get remapping working?

The ROS 2 feature comparison table has this to say for the Static remapping of ROS names item:

Should be available if passed as argument via standard rcl API – to be checked.

I checked, and it does appear to work. But not without RCL_COMMAND_LINE_ENABLED (and RCL_LOGGING_ENABLED).