eof's profile - activity

2018-02-16 20:54:12 -0500	received badge	● Student (source)
2016-06-19 20:05:23 -0500	received badge	● Famous Question (source)
2015-12-16 02:56:30 -0500	received badge	● Popular Question (source)
2015-12-16 02:56:30 -0500	received badge	● Notable Question (source)
2015-06-05 04:04:16 -0500	received badge	● Enthusiast
2015-05-10 12:26:13 -0500	commented question	Difference in loading 3rd party lib from Node vs. Nodelet called it in onInit(), a boost::thread and ros::Timer callback - same result...
2015-05-07 17:12:35 -0500	asked a question	Difference in loading 3rd party lib from Node vs. Nodelet I'm trying to use a 3rd party C library (aravis) in a nodelet but one crucial call (arv_camera_new) inexplicably fails. All works fine though when I convert the nodelet into a node (or even when I wrap the C lib in another ROS-independent C++ lib and use that in my executable). What could be different for the execution of the library code between beeing part of an ELF or SO? ldd output seems to indicate the crucial dependencies (AFAICT) are linked similarly and they (at least aravis itself) show up in the memory maps of the nodelet manager process. If used in a node, the call in question also works outside the main thread. In a nodelet, I can't get it to work no matter what. Any ideas?