Ask Your Question

Blacklist ROS2 package for ARM build

asked 2019-06-15 10:04:18 -0500

bruno_dmt gravatar image

I've recently added a repository with three ROS2 packages ( to the Crystal distribution ( The amd64 build is working fine and I can already install the packages through the testing repository.

The problem is that the arm64 build keeps failing. This is actually expected since the plugin uses a third party library that does not support arm, and since the package is a plugin for a game that only works on amd64 it makes sense.

Is there a way to prevent the buildfarm from trying to build these packages for arm64?

I've found that for ROS (1) there is a blacklist in, but the ROS2 distributions aren't listed in that repository and couldn't find anything equivalent.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2019-06-15 10:34:24 -0500

gvdhoorn gravatar image

updated 2019-06-15 10:42:51 -0500

The ROS 2 buildfarm configuration is stored in the ros2/ros_buildfarm_config fork of ros/ros_buildfarm_config.

I believe the file you are looking for is ros2/ros_buildfarm_config/crystal/release-bionic-arm64-build.yaml.

There don't appear to be any packages blacklisted yet for arm, but release-bionic-arm64-build.yaml is a REP-143 compatible release build file so it should support the package_blacklist field (refer to REP-141: Release build file - package_blacklist).

edit flag offensive delete link more


Thanks!! I was focusing so much on finding the blacklist (which doesn't exist yet) that it didn't occur to me to look for the ROS 2 buildfarm configuration.

bruno_dmt gravatar image bruno_dmt  ( 2019-06-15 15:07:43 -0500 )edit

That's an interesting plugin/node you have there.

What do you use ROS 2 for after you get the telemetry out of ETS? An actual driving simulator?

gvdhoorn gravatar image gvdhoorn  ( 2019-06-15 15:15:15 -0500 )edit

Last year we built a cockpit (sort of) with actual car components (like the cluster and the infotainment system) using ETS. At that time we used this plugin but it had two limitations for us: only works on Windows and it uses a REST API. This year the goal is to build a system that gives recommendations based on the driving behavior (like aggresive acceleration) using machine learning. As part of that project we started building this new plugin. At the same time, other team is working on detecting the driver behavior (like distractions or drowsiness) using OpenVINO. They started using the plugin to adapt the alerts based on the state. You can check that project at

bruno_dmt gravatar image bruno_dmt  ( 2019-06-15 19:55:52 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2019-06-15 10:04:18 -0500

Seen: 139 times

Last updated: Jun 15 '19