Commit 5382d99d authored by Olivier Stasse's avatar Olivier Stasse
Browse files

Update download and installation procedures.

parent eb5516e5
......@@ -6,8 +6,8 @@ GEM
minitest (~> 5.1)
thread_safe (~> 0.3, >= 0.3.4)
tzinfo (~> 1.1)
addressable (2.6.0)
public_suffix (>= 2.0.2, < 4.0)
addressable (2.7.0)
public_suffix (>= 2.0.2, < 5.0)
coffee-script (2.4.1)
coffee-script-source
execjs
......@@ -25,18 +25,18 @@ GEM
ffi (>= 1.3.0)
eventmachine (1.2.7)
execjs (2.7.0)
faraday (0.15.4)
faraday (0.17.0)
multipart-post (>= 1.2, < 3)
ffi (1.11.1)
forwardable-extended (2.6.0)
gemoji (3.0.1)
github-pages (198)
github-pages (201)
activesupport (= 4.2.11.1)
github-pages-health-check (= 1.16.1)
jekyll (= 3.8.5)
jekyll-avatar (= 0.6.0)
jekyll-coffeescript (= 1.1.1)
jekyll-commonmark-ghpages (= 0.1.5)
jekyll-commonmark-ghpages (= 0.1.6)
jekyll-default-layout (= 0.1.4)
jekyll-feed (= 0.11.0)
jekyll-gist (= 1.5.0)
......@@ -47,7 +47,7 @@ GEM
jekyll-readme-index (= 0.2.0)
jekyll-redirect-from (= 0.14.0)
jekyll-relative-links (= 0.6.0)
jekyll-remote-theme (= 0.3.1)
jekyll-remote-theme (= 0.4.0)
jekyll-sass-converter (= 1.5.2)
jekyll-seo-tag (= 2.5.0)
jekyll-sitemap (= 1.2.0)
......@@ -72,8 +72,8 @@ GEM
listen (= 3.1.5)
mercenary (~> 0.3)
minima (= 2.5.0)
nokogiri (>= 1.8.5, < 2.0)
rouge (= 2.2.1)
nokogiri (>= 1.10.4, < 2.0)
rouge (= 3.11.0)
terminal-table (~> 1.4)
github-pages-health-check (1.16.1)
addressable (~> 2.3)
......@@ -108,10 +108,10 @@ GEM
jekyll-commonmark (1.3.1)
commonmarker (~> 0.14)
jekyll (>= 3.7, < 5.0)
jekyll-commonmark-ghpages (0.1.5)
jekyll-commonmark-ghpages (0.1.6)
commonmarker (~> 0.17.6)
jekyll-commonmark (~> 1)
rouge (~> 2)
jekyll-commonmark (~> 1.2)
rouge (>= 2.0, < 4.0)
jekyll-default-layout (0.1.4)
jekyll (~> 3.0)
jekyll-feed (0.11.0)
......@@ -133,7 +133,8 @@ GEM
jekyll (~> 3.3)
jekyll-relative-links (0.6.0)
jekyll (~> 3.3)
jekyll-remote-theme (0.3.1)
jekyll-remote-theme (0.4.0)
addressable (~> 2.0)
jekyll (~> 3.5)
rubyzip (>= 1.2.1, < 3.0)
jekyll-sass-converter (1.5.2)
......@@ -203,7 +204,7 @@ GEM
jekyll (~> 3.5)
jekyll-feed (~> 0.9)
jekyll-seo-tag (~> 2.1)
minitest (5.11.3)
minitest (5.12.2)
multipart-post (2.1.1)
nokogiri (1.10.4)
mini_portile2 (~> 2.4.0)
......@@ -215,11 +216,11 @@ GEM
rb-fsevent (0.10.3)
rb-inotify (0.10.0)
ffi (~> 1.0)
rouge (2.2.1)
rouge (3.11.0)
ruby-enum (0.7.2)
i18n
ruby_dep (1.5.0)
rubyzip (1.2.3)
rubyzip (1.3.0)
safe_yaml (1.0.5)
sass (3.7.4)
sass-listen (~> 4.0.0)
......@@ -245,4 +246,4 @@ DEPENDENCIES
github-pages
BUNDLED WITH
1.16.2
2.0.2
......@@ -4,9 +4,9 @@ title: Download & Install
category: Getting Started
---
<h2> How to install the stack of tasks on your machine?</h2>
<h2> How to install the stack of tasks on your machine? </h2>
<h2> Prerequisites</h2>
<h2> Prerequisites </h2>
The current software architecture has been tested entirely on Ubuntu 16.04 LTS, Ubuntu 14.04 LTS, and Ubuntu 12.04 LTS.
A large part of the basic algorithms have been tested on Windows and Mac a while go, but there is no guarantee that it is still true.
......@@ -16,7 +16,7 @@ advice its <a href="http://robotpkg.openrobots.org/debian.html">binary repositor
You have to use also the <a href="http://robotpkg.openrobots.org/robotpkg-wip.html">wip (work in progress) part of robotpkg</a>.
Please follow the section entitled "Binary packages in robotpkg/wip".
<h3> Dependencies</h3>
<h3> Dependencies </h3>
The needed software are:
- git, CMake, boost, lapack, blas, python 2.7
......@@ -28,55 +28,55 @@ The needed software are:
- ROS
Please note that most of the packages are ROS-independent, but some packages allow to link the SOT framework to ROS
(e.g. `dynamic_graph_bridge`, `redundant_manipulator_control`)
(e.g. <b>dynamic_graph_bridge</b>,<b>redundant_manipulator_control</b>)
<h2> Binary installation</h2>
<h2> Binary installation </h2>
We are currently providing the stack of tasks through robotpkg on Ubuntu 18.04, 16.04 and 14.04
<h3> Setting a source.list file</h3>
<h3> Setting a source.list file </h3>
Robotpkg has two apt repository: a main repository and a work-in-progress repository:
```bash
{% highlight bash %}
sudo tee /etc/apt/sources.list.d/robotpkg.list <<EOF
deb [arch=amd64] http://robotpkg.openrobots.org/wip/packages/debian/pub $(lsb_release -cs) robotpkg
deb [arch=amd64] http://robotpkg.openrobots.org/packages/debian/pub $(lsb_release -cs) robotpkg
EOF
```
{% endhighlight %}
<h3> Register the robotpkg authentication key</h3>
```bash
<h3> Register the robotpkg authentication key </h3>
{% highlight bash %}
curl http://robotpkg.openrobots.org/packages/debian/robotpkg.key | sudo apt-key add -
```
<h3> Update the list of available packages</h3>
Please follow the instructions given [here](http://robotpkg.openrobots.org/debian.html) to access the package repository.
>>>>>>> master:download.html
{% endhighlight %}
<h3> Update the list of available packages </h3>
Please follow the instructions given <a href="http://robotpkg.openrobots.org/debian.html">here</a> to access the package repository.
{% highlight bash %}
To install the package sot-core-v3 you can use
```bash
sudo apt update
sudo apt install robotpkg-sot-core-v3
```
{% endhighlight %}
<h2> Source installation</h2>
<h2> Source installation </h2>
The source installation can be realized through robotpkg.
Please follow the instructions given [here](http://robotpkg.openrobots.org/install.html) to get the package repositories.
Please follow the instructions given <a href="http://robotpkg.openrobots.org/install.html">here</a> to get the package repositories.
You will also have to install the wip (work in progress) part of robotpkg. The installation procedure is described [here](http://robotpkg.openrobots.org/robotpkg-wip.html).
You will also have to install the wip (work in progress) part of robotpkg. The installation procedure is described
<a href="http://robotpkg.openrobots.org/robotpkg-wip.html">here</a>.
To compile and install the package `sot-core-v3` then you can type:
To compile and install the package <b>sot-core-v3</b> then you can type:
```bash
{% highlight bash %}
cd robotpkg/wip/sot-core-v3
make install
```
{% endhighlight %}
<h2> Environment variables</h2>
<h2> Environment variables </h2>
To setup the environment variables you can use the following script:
```bash
{% highlight bash %}
#!/bin/bash
export ROBOTPKG_BASE=/opt/openrobots
export PATH=$PATH:$ROBOTPKG_BASE/sbin:$ROBOTPKG_BASE/bin
......@@ -85,11 +85,11 @@ export PYTHONPATH=$PYTHONPATH:$ROBOTPKG_BASE/lib/python2.7/site-packages:$ROBOTP
export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:$ROBOTPKG_BASE/lib/pkgconfig/
export ROS_PACKAGE_PATH=$ROS_PACKAGE_PATH:$ROBOTPKG_BASE/share:$ROBOTPKG_BASE/stacks
export CMAKE_PREFIX_PATH=$CMAKE_PREFIX_PATH:$ROBOTPKG_BASE
```
{% endhighlight %}
If you name the script **setup-opt-robotpkg.sh** then the variables are setup by
If you name the script <b>setup-opt-robotpkg.sh</b> then the variables are setup by
sourcing the file:
```bash
{% highlight bash %}
source setup-opt-robotpkg.sh
```
{% endhighlight %}
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment