Closed joshikaustubh closed 1 month ago
I've also run into this bug, is there a workaround for now?
I also encountered exactly the same issue with this for 1 week. However, one thing i discovered is that my colleague could do 'colcon build' successfully without problems but, mine cannot. Please someone leave the comments for this issue.
We are currently in the process of adding new features. Is there a reason why you would like to build from source? Otherwise I would recommend using the available apt packages as suggested in the installation documentation.
In case you really want to build from source, you'll also have to build the upstream packages from source as mentioned in point 6 of that docs.
I get the same issue when running colcon build
when using the available apt packages through rosdep install --ignore-src --from-paths src -y
. Same for me it worked a couple weeks ago, but now is not because of the latest commit.
This is normal and expected until the next sync. If you want to build the driver from source, use an all-source build where you also build ur_msgs from source as mentioned above.
On Thursday there will be a Humble sync, with which this should go away.
Humble binary is building again.
Affected ROS2 Driver version(s)
ur_controllers
Used ROS distribution.
Humble
Which combination of platform is the ROS driver running on.
Linux in a virtual machine
How is the UR ROS2 Driver installed.
Build the driver from source and using the UR Client Library from binary
Which robot platform is the driver connected to.
URSim in a virtual machine
Robot SW / URSim version(s)
Gazebo
How is the ROS driver used.
Headless without using the teach pendant
Issue details
Summary
I am trying to build the drivers from source fr certain modifications
Issue details
I am getting an error when running
colcon build
after sourcing the package for thehumble
branchSteps to Reproduce
git clone -b humble https://github.com/UniversalRobots/Universal_Robots_ROS2_Driver.git
Expected Behavior
I expected a successful build
Actual Behavior
Workaround Suggestion
I noticed this is happening since last 2-3 days. The version I had from last week was working totally fine. I don't know if that's the issue.
Relevant log output
No response
Accept Public visibility