0
$\begingroup$

Rosanswers logo

I am new to ROS. I just installed ROS (Desktop full) on a 64-bit Fedora 16 system using the instructions at http://www.ros.org/wiki/electric/Installation/Fedora . I did an su to root, then installed to /ros so it would be available to all users. I had two minor problems (and possible solutions):

  1. During installation it could not find Python SVN support, so it said to install python-svn. At least in Fedora 16 the package does not exist under that name; it is called pysvn. I installed that, then ROS installed without errors, as far as I could see.

  2. I followed the instructions and modified my .bashrc file and that looks OK. Then I continued to the ROS Tutorials pages: http://www.ros.org/wiki/ROS/Tutorials/InstallingandConfiguringROSEnvironment . My ROS_ROOT was /ros/ros . I created a ros_workspace directory under my home directory. Then I went to add my workspace to ROS_PACKAGE_PATH, which already had about two dozen directories in it (they looked OK). The instructions said to add my workspace and /opt/ros/electric/stacks to ROS_PACKAGE_PATH. Of course /opt/ros did not exist, so I figured I would just use something like /ros/ros/electric/stacks . I used the "find" command and there is no directory electric or directory stacks anywhere under /ros . I tried just leaving that directory out of the path. But then I continued to the next page of the tutorial: http://www.ros.org/wiki/ROS/Tutorials/NavigatingTheFilesystem . and typed rospack find roscpp and it could not find that. So I used find to find roscpp and it was at /ros/ros_comm/clients/cpp/roscpp . So I added just /ros to my ROS_PACKAGE_PATH and now rospack can find roscpp.

So anyway I think I have my installation working. Does anyone know if this is the best way? And how do we get the instructions changed? Thanks.


Originally posted by Ciaraldi on ROS Answers with karma: 1 on 2012-03-03

Post score: 0

$\endgroup$

1 Answer 1

0
$\begingroup$

Rosanswers logo

On non-Ubuntu installs all ros installation and package files will be stored in your home directory... ~/ros will contains all the binaries including roscd, rosmake, roslaunch, etc. etc...

Your ROS_PACKAGE_PATH will contain all the packages that will be accessible by the ros commands. If you create another directory where you want to write all your packages you have to add to the setup.sh bash file located at /home/user/ros and then run

source ~/ros/setup.sh

You path will also become changed so that way you shell will have access to the ros programs.

To fix your problems just modify the setup.sh file providing you haven't changed it and messed up something, but your probably haven't. Add your directory to the ROS_PACKAGE_PATH variable.

Also understand your workspace should not be going anywhere near /opt/ this is a global root user location for programs and files and should be touched at all, and left to automatic installation that occurs only in Ubuntu.


Originally posted by TheLegace with karma: 76 on 2012-03-03

This answer was ACCEPTED on the original site

Post score: 0


Original comments

Comment by Ciaraldi on 2012-03-03:
Thanks for the info. As I mentioned in the original posting, I tried to install ROS in /ros so it would be accessible to all users on the system. Since I am the only user it is not a hardship to install it under my home directory, but that seems a strange way to do it.

Comment by Ciaraldi on 2012-03-03:
What is different about Ubuntu that ROS should be installed in /opt, as compared with other distros where it should be in someone's personal directory? Just wondering...

Comment by TheLegace on 2012-03-03:
Generally because A) ROS doesn't officially support other distros and there just way to many linking issues and B) As oppose to Ubuntu you have to manually compile all the packages in other distros

Comment by TheLegace on 2012-03-03:
Generally because A) ROS doesn't officially support other distros and there just way to many linking issues

Comment by TheLegace on 2012-03-03:
Generally because A) ROS doesn't officially support other distros and there just way to many linking issues

Comment by TheLegace on 2012-03-03:
Generally because A) ROS doesn't officially support other distros and there just way to many linking issues

Comment by tfoote on 2012-04-26:
As of Fuerte the build system is being redesigned to support install targets. Prior to Fuerte there was a lot of hacks and tricks to get the installation into /opt/ros to work when packaged.

$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.