jensenb's profile - activity

Should I make another edit of the post for clarity?

The issue was resolved, turns out there was another robotino_node package on the path that was resolved first, and this incorrect robotino_node package had an incorrect launch file. Take away lesson: always check the ROS_PACKAGE_PATH.

Just out of curiosity, can you run "python -c 'import sipconfig' " from the command line and check if you also get an error? In general looks like you have PYTHONPATH issues. I also suggest you open a new question for the issue, since it's not intrinsic to OS X 10.9 support

@JetForMe your pastebin links are invalid, can you update them?

@demmeln, @Artem: You are right after all, I had not updated my rosinstall_generator for a while and so I didn't see the package regrouping, my mistake. I have updated the answer accordingly.

You can also do the same thing for the WS_DIR/src/robot_model directory. If all else fails, simply create a new separate ROS workspace and follow the current Hydro installation instructions again, and the steps above should cover all the current build issues.

The warning means you already applied the first change, meaning you have the orocos_kdl upstream version per the previous instructions. If you delete this directory from WS_DIR/src and do 'wstool update -t WD_DIR/src', you should get a clean copy and so that you can apply the steps from the answer.

Take a look at the patch files in your browser and you will see what I mean.

No I am pretty sure the instructions are correct. The pull request patches are relative to the host repository, and since both orocos_kdl and robot_model are split so that each subdir becomes a new repository root, the patches have to be applied to WS_DIR/src and not one level deeper.

@William I Understand, my mistake. But in general if you follow the installation guide on the wiki wstool will checkout git repositories released using bloom, right?

How did you create your hydro workspace? The error message indicates orocos_kdl was not checked out from source with wstool.

I am having a problem building groovy from source on OS X 10.8.3 using homebrew. The RVIZ catkiin package fails to build the python bindings with the following error message:

==> Processing catkin package: 'rviz'
==> Building with env: '/Users/brian/ros_catkin_ws/install_isolated/env.sh'
Makefile exists, skipping explicit cmake invocation...
==> make cmake_check_build_system in '/Users/brian/ros_catkin_ws/build_isolated/rviz'
==> make -j2 -l2 in '/Users/brian/ros_catkin_ws/build_isolated/rviz'
Linking CXX shared library /Users/brian/ros_catkin_ws/devel_isolated/rviz/lib/librviz.dylib
[ 60%] Built target rviz
Linking CXX executable /Users/brian/ros_catkin_ws/devel_isolated/rviz/lib/rviz/rviz
[ 61%] Built target executable
Linking CXX shared library /Users/brian/ros_catkin_ws/devel_isolated/rviz/lib/libdefault_plugin.dylib
[ 93%] Built target default_plugin 
Linking CXX executable /Users/brian/ros_catkin_ws/devel_isolated/rviz/lib/rviz/image_view
[ 94%] Built target rviz_image_view
[ 94%] Running Shiboken generator for librviz Python bindings...
./QtCore.framework/Headers/QtCore
/Users/brian/ros_catkin_ws/src/rviz/src/QtCore.framework/Headers/QtCore
....
    enum 'QRegExp::CaretMode' is specified in typesystem, but not declared
type 'QFileOpenEvent' is specified in typesystem, but not defined. This could potentially lead to compilation errors.
type 'QPyTextObject' is specified in typesystem, but not defined. This could potentially lead to compilation errors.
enum 'QDateTimeEdit::Section' is specified in typesystem, but not declared

Could not find a minimal constructor for type 'QPixmap'. This will result in a compilation error.

/bin/sh: line 1:  8180 Abort trap: 6           /usr/local/Cellar/shiboken/1.1.2/bin/shiboken --  generatorSet=shiboken --include-paths=/Users/brian/ros_catkin_ws/src/rviz/src::/usr/include:/Library/Frameworks/QtCore.framework --typesystem-paths=/usr/local/Cellar/pyside/1.1.2/share/PySide/typesystems --output-directory=/Users/brian/ros_catkin_ws/build_isolated/rviz/src/python_bindings/shiboken global.h typesystem.xml
make[2]: *** [src/python_bindings/shiboken/librviz_shiboken/librviz_shiboken_module_wrapper.cpp]    Error 134
make[1]: *** [src/python_bindings/shiboken/CMakeFiles/rviz_shiboken.dir/all] Error 2
make: *** [all] Error 2
make: INTERNAL: Exiting with 3 jobserver tokens available; should be 2!

<== Failed to process package 'rviz': 
Command '/Users/brian/ros_catkin_ws/install_isolated/env.sh make -j2 -l2' returned non-zero exit status 2

Could this be a problem with my installed shiboken / pyside version (1.1.2)? Any other suggestion or idea what might be causing the problem?

Please do not answers to your question that are not answers but further questions. Instead either edit your original question, or post a comment to my answer. You should delete this post.

To answer your last question, you do not necessarily need to compile your standalone (in the sense of ROS independent) c code within catkin. It is pretty straight forward to compile your c code as a shared or static library, and then link your ROS node to it using the standard CMake syntax (by adding your c library to target_link_libraries(...) for example).

To address your linker errors. You are not missing header files, you are improperly specify the libraries to link to and the library search paths. Remember that "-L" specifies the search path, and the "-l" specifies the library name (preferably without path and without ending). For object files ".o" you do not need the "-l" flag prefix. you are missing lots of opencv libraries in command, you can try adding "-lopencv_core" and "-lcv_bridge -limage_transport" to take care of the missing OpenCV and OpenCV binding symbols.

But I highly recommend you use the cakin for building and integrating your ROS code, and not to build things by hand.

EDIT: Responding to your further comments, you are using the CMake commands incorrectly. To create your library and link to it in CMake you should use:

add_library(upd_to_ros SHARED src/upd_to_ros3.cpp) #add the source files for your "external" library code here
add_executable(imageconv_node src/ros_cpp.cpp )
target_link_libraries(imageconv_node 
    upd_to_ros
    ${catkin_LIBRARIES} 
)

Note that your ROS node imageconv_node declared in your CMakeLists.txt will need a typical main function, and it is bad practice to hard code full paths in a CMakeLists.txt.

I have not had a problem similar to that, sounds like something related to the image transport is broken.

The issue you are seeing is caused by a problem in the roscpp_core upstream package and has been disused and fixed in https://github.com/ros/roscpp_core/pull/15. Unfortunately an updated release of this package has not been created for hydro, so you will have to make the change to package by hand.

cd <path to="" ros="" workspace="">/src/roscpp_traits/include/ros curl https://raw.github.com/ros/roscpp_core/8292898d4a90ecc8cf3d42c5ce4e51e14b02a8db/roscpp_traits/include/ros/message_forward.h -o message_forward.h

Here <path to="" ros="" workspace=""> is the path of your ros workspace.

The current release version of PyQt (4.10.3) has some issues with libc++/clang build settings necessary for Mavericks. Basically PyQt incorrectly parses the QMake build settings that were used to build Qt, resulting in incorrect build flags being generated for PyQt interoperable projects. There is a fix proposed for homebrew here: https://github.com/Homebrew/homebrew/pull/25225 and for PyQt here: http://www.riverbankcomputing.com/pipermail/pyqt/2013-December/033537.html

brew install <a href="https://raw.github.com/jensenb/homebrew/76e8bf65dccdeeb785ca2f296ac2458460ba2fde/Library/Formula/pyqt.rb">https://raw.github.com/jensenb/homebrew/76e8bf65dccdeeb785ca2f296ac2458460ba2fde/Library/Formula/pyqt.rb</a>

I also agree with Hansg91. While most of the issues with hydro on OS X have been resolved, not all have been released (so you will still need to patch the packages by hand), and some packages like Orocos KDL have no immediate solution in sight.

libc++ is used by default, but c++11 support is only active is your set the flag, not be default.

To clarify I would the dynamic_reconfigure currently requires the source directory, from which it was installed, to persist even after it is installed. Upon starting dynamic reconfigure reads file its source directory, and not just from its installation location.

So what exactly are you asking here?

You can use the following shell code to print out the commands that will remove all the known system dependencies installed for ROS packages:

rosdep db | awk '{if ($3) print $3}' | { while read package; do [ "$package" == "->" ] || (brew info $package &> /dev/null && echo "brew remove $package") || (pip list | grep $package &> /dev/null  && echo "pip uninstall $package") || echo "# $package is neither brew formula or a python package"; done; }

This will print out one line for each system dependency needed by ROS with the appropriate command for its removal. This does not actually remove the packages as I think this is unwise. Many system dependencies needed by ROS are likely also needed by other software on your system, so you need to evaluate on an individual package basis, what should be uninstalled.

The ROS python tools can be uninstall with:

pip uninstall wstool rosdep rosinstall rosinstall_generator rospkg catkin-pkg

Other than this your ROS installation should be self contained under your ROS workspace directory, or where ever you have placed your ROS installation.

What version of OS X are you using? And can you post a gist of the full build log, not just the last snippet?

Description here: http://answers.ros.org/question/100741/catkin-fails-on-osx-109-cant-find-__main__-module-in-empy-31-py27eggempyc/?answer=101061#post-id-101061

I should correct my previous statement. The easy_install command completed successfully, but it built and installed an egg package, which apparently is supported by catkin.