-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsistency between CPP/H names in rclUE and gen_ue_from_ros #27
Comments
@yuokamoto, |
Thanks for your comments and sorry not responding. I will look into. |
Could you provide more details on which step you encountered the error? |
Bychanging this part in config.yaml, you can change msg name Line 18 in 48989f6
|
|
Hi!
I've been trying to just build my custom msgs for use within UE and rclUE.
I did not understand how to get docker to work so I've been building it locally using the scripts inside BuildROS2 and CodeGen
I've had to make a number of minor changes to the script to make it work (which I will detail below) but the biggest one is the inconsistency between CPP/H names in rclUE and gen_ue_from_ros.
In rclUE, the names of the files are all
ROS2+<MSG_NAME>
e.g. a pose message is ROS2Pose.cpp with all references within the header files to the same name.However, the
update_msg_name
function inside gen_ue_from_ros will generate a name which isROS2+<PKG_NAME>+<MSG_NAME>
, i.e. ROS2GeometryMsgsPose.cppNow this is an issue for two reasons
I did change
update_msg_name
back to just using the type name, but unfortunately I had a msg name clash between an existing package and mine.My final hacky solution was to use the
DEFAULT_DEPENDENCY_PKGS
to choose whether we append the pkg name, with custom msgs always having their pkg name. Not ideal!So either the rclUE branch (UE5_devel_humble) should be updated with the new format, or something done here to mitigiate for it!
Other bugs:
import os
at the topros2_ws
hardcoded in, took me a while to figure out how to point UE_TOOLS at my msgsHope these observations help!
The text was updated successfully, but these errors were encountered: