Robotics StackExchange | Archived questions

Creating a custom message. Compile error: PROTOBUF_PROTOC_EXECUTABLE-NOTFOUND: not found

Hi

I'm trying to learn how to build my own messages and to that end I'm looking at this tutorial.

After following the tutorial and copying the code into into the appropriate files I try to compile but get an error. The following is the output of cmake ..; make:

-- The C compiler identification is GNU 4.8.2
-- The CXX compiler identification is GNU 4.8.2
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Boost version: 1.54.0
-- Found the following Boost libraries:
--   system
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.26") 
-- checking for module 'gazebo'
--   found gazebo, version 4.0.0
-- checking for module 'sdformat'
--   found sdformat, version 2.0.1
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
-- Found PROTOBUF: /usr/lib/x86_64-linux-gnu/libprotobuf.so  
-- Configuring done
-- Generating done
-- Build files have been written to: /home/nicolas/collision_map_creator/build
[ 10%] Running C++ protocol buffer compiler on /usr/include/gazebo-4.0/gazebo/msgs/proto/time.proto
/bin/sh: 1: PROTOBUF_PROTOC_EXECUTABLE-NOTFOUND: not found
make[2]: *** [msgs/time.pb.cc] Error 127
make[1]: *** [msgs/CMakeFiles/collision_map_creator_msgs.dir/all] Error 2
make: *** [all] Error 2

You wouldn't think following that tutorial would leave any room to make mistakes, but apparently I managed to do so anyway.

Can someone tell me what goes wrong and how I can fix it?

Thanks, Nick

Asked by NickDP on 2014-09-17 19:13:07 UTC

Comments

Answers

It was fixed by installing the protobuf-compiler package.

Asked by ifklikk on 2016-04-05 15:09:12 UTC

Comments

Assuming you using ubuntu this can be done via the following command:

sudo apt-get install protobuf-compiler

Thanks for the info btw!!

Asked by chutsu on 2016-10-20 22:42:22 UTC