xperroni's profile - activity

I had this problem the other day, but in my case it was due to a network configuration issue. The entry in /etc/hosts in

For anyone interested in a horribly over-engineered solution for suppressing TF_REPEATED_DATA warnings on the receiving

It seems there's still no direct support for loading components from XML files, for the time being I'm using the <exe

When building the latest version of teb_local_planner in ROS Kinect from source, I get the following error:

CMake Error at teb-local-planner/CMakeLists.txt:197 (target_link_libraries):
  Target "tf" of type EXECUTABLE may not be linked into another target.  One
  may link only to STATIC or SHARED libraries, or to executables with the
  ENABLE_EXPORTS property set.


CMake Error at teb-local-planner/CMakeLists.txt:208 (target_link_libraries):
  Target "tf" of type EXECUTABLE may not be linked into another target.  One
  may link only to STATIC or SHARED libraries, or to executables with the
  ENABLE_EXPORTS property set.

Cheking the CMakeLists.txt file, lines 197 and 208 correspond to target_link_libraries() directives; when checking the value of ${catkin_LIBRARIES} I do see a reference to the tf executable.

Why is catkin adding the tf executable to the libraries variable?

Edit: I'm running ROS Kinetic on Ubuntu Xenial (16.04) and Intel notebook, with cmake 3.5.1 and gcc 5.4.0.

As pitpet noticed, ScanShadowsFilter works by computing the angle differences between successive readings and discarding

Error when building TEB local planner: "Target 'tf' of type EXECUTABLE may not be linked into another target" When build

I still don't understand why catkin is doing that, but I noticed that compiling with catkin_make_isolated instead of cat

Error when building TEB local planner: "Target 'tf' of type EXECUTABLE may not be linked into another target" When build

See this tutorial for reference: http://wiki.ros.org/hokuyo_node/Tutor...

I had the same problem when trying to start the node from a .launch file, but it worked alright when starting roscore and the hokuyo node separately from the terminal. I used rosparam to set the device port though, so you might want to try it out.