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
The are a number of different builds that need to be taken into account. Not all versions of each combination will need to be supported. Ideally we would maintain a single openhaptics/driver combination (most recent per device) and then have a build per ros/ubuntu/arch combination. Some of it will be as simple as an ENV flag, others may be more involved. It might be a good idea to break out the legacy device and have them in different branches/repositories?
Wonder if these need to be tested against vanilla ubuntu and ones with the Xenomai or PREEMPT_RT kernel patches? The current UR ROS drives when used with the e-series are meant to use the PREEMPT_RT patch for realtime communication.
The documentation will need to be updated to cover this.
https://github.com/jdrew1303/ros_duckie (uses cross compiling for arm builds. this might need tweaking for libs and cpp support. also need to checkout NEON and VFP(v2, v3, v4))
The are a number of different builds that need to be taken into account. Not all versions of each combination will need to be supported. Ideally we would maintain a single openhaptics/driver combination (most recent per device) and then have a build per ros/ubuntu/arch combination. Some of it will be as simple as an ENV flag, others may be more involved. It might be a good idea to break out the legacy device and have them in different branches/repositories?
The documentation will need to be updated to cover this.
WIP Build Matrix
Some notes for matrix builds:
The text was updated successfully, but these errors were encountered: