ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Buildfarm issues with shared libraries [closed]

asked 2014-09-01 13:04:13 -0600

Miquel Massot gravatar image

Hi all,

I just decided to release for indigo a package that I had working for hydro and could not solve a problem with an external shared library. My package is avt_vimba_camera, a driver for Allied Vision Technologies cameras using ethernet (mainly). For that I need to use AVT SDK called VIMBA. In my package, I have VIMBA libraries and I "find_library" them from the CMakeLists.txt, who checks for the appropiate architecture (32 vs 64 bit).

The package itself compiles on my machine and on another machine with no issue at all, but on jenkins, the library cannot be found (example).

What is the difference on these builfarms that cause the library to be "NOTFOUND"?

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Miquel Massot
close date 2015-03-24 05:10:35.993273

1 Answer

Sort by ยป oldest newest most voted

answered 2014-09-01 13:37:18 -0600

Dirk Thomas gravatar image

Each job on the build farm starts with a "fresh" image which does not have any packages installed. Then it clones your repo and uses the information in the package.xml files to install declared dependencies.

I don't see any reference to the SDK in your package.xml ( ). That might be a reason why the build farm does not install it and therefore CMake can't find the library.

On your development machine you will have the SDK installed and therefore the library can be found.

edit flag offensive delete link more


It is in lib/{32,64}bit ->

This SDK has to be manually installed, that's why I unziped in lib/ and in include/ so that my executables can find it.

Miquel Massot gravatar image Miquel Massot  ( 2014-09-02 02:51:46 -0600 )edit

Nothing tries to search libraries in your sources lib folder for libraries. Also you don't install those libraries which means they would not even be part of the Debian package. May be on your development machine you have the libraries additionally in a different location?

Dirk Thomas gravatar image Dirk Thomas  ( 2014-09-02 19:31:43 -0600 )edit

Question Tools

1 follower


Asked: 2014-09-01 13:04:13 -0600

Seen: 153 times

Last updated: Sep 01 '14