You should never edit /opt/ros/boxturtle/setup.sh by hand

You correct way to solve this problem is to create a new setup.sh
which sources /opt/ros/boxturtle/setup.sh and then adds your package
to it.  That way there will not be side-effects for other people on
your system using the shared install.

In your own directory you want to create a file like  'mysetup.sh':

. opt/ros/boxturtle/setup.sh
export ROS_PACKAGE_PATH=/path/to/mypackage:${ROS_PACKAGE_PATH}



On Thu, Apr 22, 2010 at 3:19 AM, Ugo Cupcic <ugo@shadowrobot.com> wrote:
> Hi,
>
> If it was not created in the standard ros stack directory, you need to add
> the path to your package in </opt/ros/boxturtle>/setup.sh. And then source
> the setup.sh
>
> Cheers,
>
> Ugo
>
> On 22/04/10 11:16, shayan sengupta wrote:
>
> hi
>
> I am trying to create a package in ROS, I am able to create the package but
> roscd is not able to find the package.I have also tried rospack find but the
> result's the same.Do we need to set some path or something like that so that
> rospack can find it?
>
> Btw i am using pre-compiled ros binary.
>
> --shayan
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>
> --
> Ugo Cupcic         |  Shadow Robot Company | ugo@shadowrobot.com
> Software Engineer      251 Liverpool Road
> need a Hand?           London  N1 1LX       | +44 20 7700 2487
> http://www.shadowrobot.com/hand/              @shadowrobot
>
>
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>
>