didi2002's profile - activity

Removing the googletest + libgtest-dev package from my system fixes the build but breaks other projects

I have setup using clean debian stretch and a ros kinetic from source. Until a couple of days ago, everything worked just fine, but when running this:

rosinstall_generator ros_comm --deps --rosdistro kinetic --wet-only --tar > test.rosinstall
wstool init -j4 src test.rosinstall
catkin init
catkin config --install --install-space /opt/ros/kinetic
catkin build

I now get the following error:

Starting >>> catkin
No handlers could be found for logger "trollius"
Errors << catkin:install /home/user/ros_catkin_ws/logs/catkin/build.install.000.log
CMake Error at gtest/cmake_install.cmake:42 (file):
  file INSTALL cannot find
  "/home/user/ros_catkin_ws/build/catkin/gtest/libgtest.so".
Call Stack (most recent call first):
  cmake_install.cmake:154 (include)

make: *** [install] Error 1

Using catkin_make_isolated instead, I get

WARNING: Target "gtest" has EXCLUDE_FROM_ALL set and will not be built by default but an install rule has been provided for it.

For every single package processed by catkin_make. The important part is the "--install" parameter, both methods work when installing is disabled I'm not sure if this is a ros_comm / catkin / gtest related error or something wrong with my setup. Does anyone have an idea a) where to file an appropriate bug? b) how I messed up my setup?

The ros-service is also used by the other nodes, not only for checking if the connection is up. I like the idea of using the parameter server, but I want to avoid polling and sleeping because that introduced quite a delay.

Thanks for your reply!

Hi all!

I'm trying to connect my robot to a webserver using a node communication node.
This node creates the service "/get_webdata" when the connection is established and authenticated. When the connection is lost, the service is destroyed again. This allows me to use wait_for_service in other nodes, which is pretty useful for waiting without ugly sleep-loops.

So my question is: is this a common ros practice to use:

webdata = rospy.Service("/get/webdata", Webdata, self.web_cb)

and

webdata.shutdown("Connection lost")

to signal other nodes if the connection is up?
I didn't read anywhere that it's bad practice, but it feels like I'm abusing this feature. Would it be a better solution to keep the service running all the time and instead return a status variable, indicating that the connection is unavailable?