While you're at it, it would be really helpful to update to the latest version of window_cocoa.mm in modules/highgui/src -- there was a really bad memory leak that is fixed now. However it is not fixed in the version pulled by ros.

Thanks for your help. 

--Nick 


On Aug 24, 2010, at 12:43 PM, Brian Gerkey wrote:

> On Tue, Aug 24, 2010 at 11:42 AM, Nicholas Butko <nbutko@ucsd.edu> wrote:
>> Granite:OpenCV_HelloWorld nick$ otool -L bin/OpenCV_HelloWorld
>> bin/OpenCV_HelloWorld:
>> libopencv_core.2.1.dylib (compatibility version 2.1.0, current version
>> 2.1.1)
>> libopencv_imgproc.2.1.dylib (compatibility version 2.1.0, current version
>> 2.1.1)
>> libopencv_highgui.2.1.dylib (compatibility version 2.1.0, current version
>> 2.1.1)
>> libopencv_ml.2.1.dylib (compatibility version 2.1.0, current version 2.1.1)
>> libopencv_video.2.1.dylib (compatibility version 2.1.0, current version
>> 2.1.1)
>> libopencv_objdetect.2.1.dylib (compatibility version 2.1.0, current version
>> 2.1.1)
>> libopencv_features2d.2.1.dylib (compatibility version 2.1.0, current version
>> 2.1.1)
>> libopencv_calib3d.2.1.dylib (compatibility version 2.1.0, current version
>> 2.1.1)
>> libopencv_contrib.2.1.dylib (compatibility version 2.1.0, current version
>> 2.1.1)
>> libopencv_legacy.2.1.dylib (compatibility version 2.1.0, current version
>> 2.1.1)
>> /Users/nick/ros/ros/core/roscpp/lib/libros.dylib (compatibility version
>> 0.0.0, current version 0.0.0)
>> /opt/local/lib/libboost_signals-mt.dylib (compatibility version 0.0.0,
>> current version 0.0.0)
>> /Users/nick/ros/ros/3rdparty/xmlrpcpp/lib/libXmlRpc.dylib (compatibility
>> version 0.0.0, current version 0.0.0)
>> /Users/nick/ros/ros/core/rosconsole/lib/librosconsole.dylib (compatibility
>> version 0.0.0, current version 0.0.0)
>> /opt/local/lib/libboost_thread-mt.dylib (compatibility version 0.0.0,
>> current version 0.0.0)
>> /opt/local/lib/liblog4cxx.10.dylib (compatibility version 11.0.0, current
>> version 11.0.0)
>> /Users/nick/ros/ros/core/roslib/lib/libroslib.dylib (compatibility version
>> 0.0.0, current version 0.0.0)
>> /Users/nick/ros/ros/tools/rospack/lib/librospack.dylib (compatibility
>> version 0.0.0, current version 0.0.0)
>> /Users/nick/ros/ros/tools/rospack/lib/librosstack.dylib (compatibility
>> version 0.0.0, current version 0.0.0)
>> /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version
>> 7.9.0)
>> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
>> 125.2.0)
>> It seems like the absolute path information is getting lost for OSX opencv2
>> linking?
> 
> hi Nick,
> 
> I believe that that indicates that the OpenCV libs don't know their
> own full names, usually because install_name_tool wasn't invoked.  The
> OpenCV folks have reportedly fixed this on trunk of OpenCV (e.g.,
> https://code.ros.org/trac/opencv/changeset/3298).  We should probably
> pull the necessary fix(es) into cturtle/vision_opencv.
> 
> 	brian.
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users