Skip to content
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

Link ifm3d library files with another ros package when using ros-<distro>-ifm3d-core #275

Closed
tanay-bits opened this issue Dec 4, 2020 · 3 comments

Comments

@tanay-bits
Copy link

Hi,

I installed both the ifm3d ros wrapper as well as the driver package from apt using apt install ros-melodic-ifm3d.

I want to use the core (driver) libraries components such as ifm3d::Camera, ifm3d::FrameGrabber, etc. in my custom ros package. I have included ifm3d as a catkin package in my package's CMakeLists.txt as well as package.xml, but AFAIK that refers to just the ros wrapper -- https://github.com/ifm/ifm3d-ros and gives access to the msgs from it.

When I run catkin_make in my workspace, it is failing when it tries to link my node with ifm3d driver libraries, as it cannot locate the .so files.

What is the correct way to link ifm3d core libraries in this situation? Since the ros package ifm3d_core does not provide any cmake files, including that in my CMakeLists doesn't help.

@graugans
Copy link
Member

graugans commented Dec 7, 2020

Hey tanay-bits,

could you please provide some background information like which ROS version are you using and how the ifm3d package was installed. Have you used the ifm apt repositories or the ROS distribution?

While we developped the packages for the ROS index we ran into an issue with the naming. This was why the ifm3d base library is called ifm3d_core and the ifm3d ROS wrapper is called ifm3d.

Am I right you don't want to use our ROS driver but you are planning to develop your own ROS wrapper which uses the ifm3d_core libraries. Would it be fine to provide an Docker container with an example set-up?

Best,
Christian

@github-actions
Copy link

This issue is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale label Oct 28, 2022
@github-actions
Copy link

This issue was closed because it has been inactive for 14 days since being marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants