It is interesting, I wonder why the `rosws`[1] command is not used here?  I suppose it might be trying to explain the role of ROS_PACKAGE_PATH and ROS_WORKSPACE, but I think it would be better to add information about ROS_WORKSPACE here: http://ros.org/wiki/ROS/EnvironmentVariables, and use `rosws` in the tutorial.  Manually creating a setup.sh file seems tedious and unnecessary.

[1] http://www.ros.org/doc/api/rosinstall/html/

--

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
William Woodall
Graduate Software Engineering
Auburn University
w@auburn.edu
wjwwood@gmail.com
williamjwoodall.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~



On Mon, May 7, 2012 at 12:50 PM, David <spamfuerdavid@gmx.de> wrote:
Hi,

IMHO there is a bug in the configuration tutorial on http://www.ros.org/wiki/ROS/Tutorials/InstallingandConfiguringROSEnvironment in section 3.2:

If you run the first line of the listing, the $ROS_PACKAGE_PATH variable is expanded, which should not be done like that. If there is no $ROS_PACKAGE_PATH set on call time of the command, the string is expanded to "export ROS_PACKAGE_PATH=~/ros_workspace:"

If you want to rosmake your first package this results in
[rospack] Error: package/stack shutter depends on non-existent package roscpp

Greets,
David
_______________________________________________
ros-users mailing list
ros-users@code.ros.org
https://code.ros.org/mailman/listinfo/ros-users