Don't jinx us... Now we are down, hopefully they will go for the punt and we'll come back with a td, but if we play like this all year, it will be a long one... Also, you can usually find a link to the bug tracker at the bottom of the respectively wiki page. (Ken had to point this out to me too) -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ William Woodall Graduate Software Engineering Auburn University w@auburn.edu wjwwood@gmail.com williamjwoodall.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On Sat, Sep 3, 2011 at 1:28 PM, Kevin Walchko wrote: > Thanks. To honest, I am never really sure where to go to look up bugs, that > is why I always post what I find here so people can correct me. > > At least Auburn is finally up over Utah … you'll just have to hold on for 1 > more quarter. :) > > > > On Sep 3, 2011, at 2:13 PM, William Woodall wrote: > > Anytime, you guys should do a quick search on the bug trackers when you hit > an issue, I have tried to put tickets up for all the non-homebrew specific > problems I've solved so far on OS X. I have patches all the way up to rviz. > I still need to put patches up for rviz, but I was holding off because > there are still issues and some of it is a bit hack-ish. > > Also, if you don't see something on a bug tracker, I might have a > non-ticketed fix in the stack level patches on my github, so check there > too. > > > https://github.com/wjwwood/ros-osx/tree/master/electric-lion-homebrew/patches > > -- > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > William Woodall > Graduate Software Engineering > Auburn University > w@auburn.edu > wjwwood@gmail.com > williamjwoodall.com > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > On Sat, Sep 3, 2011 at 1:10 PM, Kevin Walchko wrote: > >> Thanks!! I was able to build the entire orocos_kinematics_dynamics stack >> using your patch in ticket #4. >> >> >> >> On Sep 3, 2011, at 2:06 PM, Nicholas Butko wrote: >> >> > In the port install log, you will see the correct checksum. You can >> manually update the Portfile with the new checksum. >> > >> > >> > >> > On Sep 3, 2011, at 10:49 AM, Kevin Walchko >> wrote: >> > >> >> I am working on it right now … >> >> >> >> My problem is python_orocos_kdl is looking for eigen and I can't load >> it from macports due to a checksum miss match. Googling around, it appears >> that author likes to do stealth updates and I can't seem to figure out how >> to force macports to install eigen. Did you have this problem? >> >> >> >> On Sep 3, 2011, at 1:45 PM, Nicholas Butko wrote: >> >> >> >>> Kevin, can you build python_orocos_kdl? I fixed the cmake problems >> with orocos_kdl, similar to you, but I get a ton of undefined symbol link >> errors for the python version, which prevents many stacks from building. It >> is a huge point of failure for me right now. >> >>> >> >>> >> >>> >> >>> On Sep 3, 2011, at 10:22 AM, Kevin Walchko >> wrote: >> >>> >> >>>> Hi, >> >>>> >> >>>> [setup] >> >>>> >> >>>> ROS Electric >> >>>> OSX Lion with Macports >> >>>> >> >>>> [Problem] >> >>>> >> >>>> Eigen3.cmake couldn't find eigen3 >> >>>> >> >>>> [Solution] >> >>>> >> >>>> Instead of using the included cmake files in >> orocos_kdl/config/Eigen3.cmake I changed CMakeLists.txt to use pkg-config >> which macports automatically sets up for OSX. Don't know if Linux does this >> too. >> >>>> >> >>>> CMakeLists.txt: >> >>>> include($ENV{ROS_ROOT}/core/rosbuild/FindPkgConfig.cmake) >> >>>> pkg_check_modules(EIGEN3 REQUIRED eigen3) >> >>>> include_directories(${EIGEN3_INCLUDE_DIRS}) >> >>>> #INCLUDE(${PROJ_SOURCE_DIR}/config/FindEigen3.cmake) >> >>>> #INCLUDE_DIRECTORIES(${EIGEN3_INCLUDE_DIR}) >> >>>> >> >>>> >> >>>> Not sure why the pkg-config wasn't used in the first place, it seems >> to work nice. >> >>>> >> >>>> The included Eigen3.cmake appears to be too limited in where it >> looks, at least for OSX. Could add /opt/local/include/eigen3 but didn't try. >> >>>> >> >>>> config/Eigen3.cmake: >> >>>> FIND_PATH(EIGEN3_INCLUDE_DIR Eigen/Core /usr/include >> /usr/include/eigen3) >> >>>> >> >>>> Thanks. >> >>>> >> >>>> Kevin >> >>>> >> >>>> _______________________________________________ >> >>>> ros-users mailing list >> >>>> ros-users@code.ros.org >> >>>> https://code.ros.org/mailman/listinfo/ros-users >> >>> _______________________________________________ >> >>> ros-users mailing list >> >>> ros-users@code.ros.org >> >>> https://code.ros.org/mailman/listinfo/ros-users >> >> >> >> _______________________________________________ >> >> ros-users mailing list >> >> ros-users@code.ros.org >> >> https://code.ros.org/mailman/listinfo/ros-users >> > _______________________________________________ >> > ros-users mailing list >> > ros-users@code.ros.org >> > https://code.ros.org/mailman/listinfo/ros-users >> >> _______________________________________________ >> ros-users mailing list >> ros-users@code.ros.org >> https://code.ros.org/mailman/listinfo/ros-users >> > > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users > > > > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users > >