search

anqixu / ueye_cam

A ROS nodelet and node that wraps the driver API for UEye cameras by IDS Imaging Development Systems GMBH.
Other
60 stars 102 forks source link

hydro build failing #12

Closed 130s closed 9 years ago

130s commented 9 years ago

Just wanted to give headsup that Hydro DEB build has been failing (as @anqixu might be already aware of).

anqixu commented 9 years ago

Yes, I've been talking to @dirk-thomas about this and other related issues, and we agree that the current situation is very awkward:

Consequently, this package will not be able to build on Jenkins for the time being.

I have contacted IDS Imaging and asked them to either re-package their driver as a .deb, or give us permission to re-distribute the necessary files.

gavanderhoorn commented 9 years ago

I know it's not how packages (debs) normally 'work' in ROS distributions, but has anyone ever considered something like how dkms works? dkms debs may contain binaries of the drivers they package, but may also install only sources, which get build during installation (I think in a post-install hook) using the dkms build infrastructure.

Perhaps something like that could be something for ROS packages that interact with proprietary, binary only, drivers that need to be installed by the user (as the mfg / vendor doesn't allow us to redistribute them).

ROS pkg <-> driver blob interactions could be refactored into a small dynamic library that gets build on install. The rest of the node(s) do get build by the osrf infrastructure, and users do install a binary deb. They just need to make sure they've first installed the necessary driver package from the mfg / vendor before installing the ROS deb that interacts with it.

One disadvantage would be that tests that include actual interaction with the device will need the "small dynamic library" present. But tests with the actual driver will most likely need access to real hardware anyway, which is also not available on the Jenkins server.

anqixu commented 9 years ago

@gavanderhoorn I understand the gist of your suggestion, but I'm afraid that I do not have the necessary expertise to pull off this custom packaging job. I would welcome you or anyone else to attempt to resolve the driver installation issue with such a workaround, while we all wait for IDS Imaging's response.

anqixu commented 9 years ago

I'm getting slightly annoyed at the situation, where this package is being stuck in limbo due to legal red tape. While waiting for IDS's response to my formal request, I'm switching to using unofficial re-packaged IDS drivers (credits due to ueye ROS package maintainers): 8e7abd68b2043e3e302bcf9a7cf9a1f4f028e381 a2eaba96804410d56305e410f24a4f5037f16b33

Hopefully this will make the buildfarm happy.

130s commented 9 years ago

At least I'm able to download-install version 0.0.3. Won't have time to test within a week though. Thanks for the work!

(fyi @youtalk)

130s commented 9 years ago

Sorry I checked ueye 0.0.3. Looks like ueye_cam 1.0.4 is still failing to build for hydro.

anqixu commented 9 years ago

f30beac817fd84d465ce6c7831ca4a41fa8bccb2

anqixu commented 9 years ago

Builds seem to be finally passing.

http://jenkins.ros.org/view/HbinP32/job/ros-hydro-ueye-cam_binarydeb_precise_i386/90/ http://jenkins.ros.org/view/IbinS32/job/ros-indigo-ueye-cam_binarydeb_saucy_i386/90/

dirk-thomas commented 9 years ago

:tada: