Skip to content
Snippets Groups Projects
Commit a54a3efd authored by Tommy Persson's avatar Tommy Persson
Browse files

Fix for devenv.

parent de8c93ee
No related branches found
No related tags found
No related merge requests found
......@@ -137,7 +137,7 @@ export WORLD_ORIGIN_ELEVATION=29.8
#source /opt/ros/melodic/setup.bash
source ${HOME}/wara_ws/devel/setup.bash
export PATH=${HOME}/waraps/script:${PATH}
export PATH=${HOME}/lrs_devenv_common/script:${PATH}
```
Then log in and log out to the development system for the docker commands to work. Test this with:
......@@ -145,8 +145,12 @@ Then log in and log out to the development system for the docker commands to wor
```bash
docker ps
```
++++++++++++++++ What should this say? Is it just a test that nothing crashes or do you want to see something in particular?
It should show:
```bash
tompe@philo:~$ docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
tompe@philo:~$
```
At this point your system now has the necessary software installed.
......@@ -157,12 +161,15 @@ glxgears
glmark2
```
If the above commands execute without errors you can test that Gazebo works correctly on your development system:
If the above commands execute without errors you can test that Gazebo
works correctly on your development system:
```bash
roslaunch lrs_wara_gazebo gazebo.launch
roslaunch lrs_wara_gazebo dji_to_gazebo.launch name:=dji0 with_laser:=true x:=5
```
+++++++++++++++++++ Does any of this require an actual development environment to be installed or is this completely self-contained in the playbook software etc?
All files to run these tests should be available in lrs_wara_gazebo
which is installed in wara_ws by the Playbook above. The first command
starts Gazebo and the second command add a model of a DJI M100 to the
Gazebo world.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment