The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Sorry, this is not an answer, but I stuck at the same procedure. My problem occurs, when I try to compile the first message folder (roscd ipc_roslib && make). The output message is:
[ rosmake ] rosmake starting...
[ rosmake ] Packages requested are: ['ipc_bridge_ros']
[ rosmake ] Logging to directory <my_dir>/.ros/rosmake/rosmake_output-20121108-150035
[ rosmake ] Expanded args ['ipc_bridge_ros'] to:
['ipc_bridge_ros']
[rosmake-1] Starting >>> ipc [ make ]
[rosmake-0] Starting >>> roslang [ make ]
[rosmake-2] Starting >>> geometry_msgs [ make ]
[rosmake-2] Finished <<< geometry_msgs No Makefile in package geometry_msgs
[rosmake-0] Finished <<< roslang No Makefile in package roslang
[rosmake-2] Starting >>> sensor_msgs [ make ]
[rosmake-0] Starting >>> roscpp [ make ]
[rosmake-3] Starting >>> nav_msgs [ make ]
[rosmake-2] Finished <<< sensor_msgs No Makefile in package sensor_msgs
[rosmake-0] Finished <<< roscpp No Makefile in package roscpp
[rosmake-3] Finished <<< nav_msgs No Makefile in package nav_msgs
[rosmake-1] Finished <<< ipc [PASS] [ 0.83 seconds ]
[rosmake-1] Starting >>> ipc_bridge [ make ]
[rosmake-1] Finished <<< ipc_bridge No Makefile in package ipc_bridge
[rosmake-1] Starting >>> ipc_bridge_ros [ make ]
[rosmake-1] Finished <<< ipc_bridge_ros No Makefile in package ipc_bridge_ros
[ rosmake ] Results:
[ rosmake ] Built 8 packages with 0 failures.
[ rosmake ] Summary output to directory
[ rosmake ] <my_dir>/.ros/rosmake/rosmake_output-20121108-150035
I guess, that the folder ipc_msgs is not at the right place (I did not see an intruction for that, thus I placed it into the ipc_bridge_stack folder, which is agained placed into the ROS package/stack folder).
| | 2 | No.2 Revision |
Sorry, this is not an answer, but I stuck at the same procedure. My problem occurs, when I try to compile the first message folder (roscd ipc_roslib && make). The output message is:
[ rosmake ] rosmake starting...
[ rosmake ] Packages requested are: ['ipc_bridge_ros']
[ rosmake ] Logging to directory <my_dir>/.ros/rosmake/rosmake_output-20121108-150035
[ rosmake ] Expanded args ['ipc_bridge_ros'] to:
['ipc_bridge_ros']
[rosmake-1] Starting >>> ipc [ make ]
[rosmake-0] Starting >>> roslang [ make ]
[rosmake-2] Starting >>> geometry_msgs [ make ]
[rosmake-2] Finished <<< geometry_msgs No Makefile in package geometry_msgs
[rosmake-0] Finished <<< roslang No Makefile in package roslang
[rosmake-2] Starting >>> sensor_msgs [ make ]
[rosmake-0] Starting >>> roscpp [ make ]
[rosmake-3] Starting >>> nav_msgs [ make ]
[rosmake-2] Finished <<< sensor_msgs No Makefile in package sensor_msgs
[rosmake-0] Finished <<< roscpp No Makefile in package roscpp
[rosmake-3] Finished <<< nav_msgs No Makefile in package nav_msgs
[rosmake-1] Finished <<< ipc [PASS] [ 0.83 seconds ]
[rosmake-1] Starting >>> ipc_bridge [ make ]
[rosmake-1] Finished <<< ipc_bridge No Makefile in package ipc_bridge
[rosmake-1] Starting >>> ipc_bridge_ros [ make ]
[rosmake-1] Finished <<< ipc_bridge_ros No Makefile in package ipc_bridge_ros
[ rosmake ] Results:
[ rosmake ] Built 8 packages with 0 failures.
[ rosmake ] Summary output to directory
[ rosmake ] <my_dir>/.ros/rosmake/rosmake_output-20121108-150035
I guess, that the folder ipc_msgs is not at the right place (I did not see an intruction for that, thus I placed it into the ipc_bridge_stack folder, which is agained placed into the ROS package/stack folder).
EDIT:
When compiling the message folder, an error similar to "unknown command "mex"" could appear. This happens, when the matlab command "mex" is not available in the environment variable "PATH". To do so, use the following line in your .bashrc script:
export PATH=<your path="" to="" matlab="">/bin:$PATH
With it, you should be able to call the mex command from anywhere in the shell.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.