/
INSTALL
200 lines (138 loc) · 6.67 KB
/
INSTALL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
===============================================================================
Modular OpenRobots Simulator Engine
Copyright (c) 2009-2010 ONERA
Copyright (c) 2009-2016 LAAS-CNRS
Copyright (c) 2015-2016 ISAE-SUPAERO
Copyright held by the MORSE authors or the institutions employing them,
refer to the AUTHORS file for the list. The list of the contributors to
each file can be obtained from the commit history ('git log <file>').
===============================================================================
All this information can be read online:
http://www.openrobots.org/morse/doc/stable/user/installation.html
General requirements
--------------------
Hardware
++++++++
A decent machine is required (typically, with an Intel i5 + 4GB RAM, you
should be comfortable).
To display textures correctly in the simulator, as well as to generate images
using the simulated cameras, you will need to have a graphics card that
supports GLSL shading. The Blender website lists these graphic cards as
compatible with GLSL:
- ATI Radeon 9x00, Xx00, X1x00, HD2x00 and HD3x00 series and newer. - NVidia
Geforce FX, 6x00, 7x00, 8x00, 9x00 and GTX 2x0 and newer.
If you do not need cameras and OpenGL textures/shaders, you are advised to
run your simulation in fastmode (refer to the simulation's Builder
API) for vastly improved loading time and performances.
Supported operating systems
+++++++++++++++++++++++++++
Only Linux (x86, x86_64) is currently officially supported. MORSE is mainly
developed on Fedora and Ubuntu, but we don't expect problems on other
distributions.
Other UNIXes systems probably work as well (like FreeBSD or Apple MacOSX).
Windows is supported, but not fully tested.
Packaged versions
-----------------
morse-1.0 is available on Debian Wheezy/Ubuntu >= 13.04. You can install
the package morse-simulator with your favorite software manager::
$ sudo apt-get install morse-simulator
You can also install the Python bindings with::
$ sudo apt-get install python3-morse-simulator
You can also easily install MORSE with:
- robotpkg
- brew (MacOSX)
See their associated documentation for details.
If you plan to use the simulator with raw sockets or text files as interface
(for instance, to integrate MORSE with MatLab or other specific
applications), you don't need anything else. Otherwise, you need to install
the software for the desired middlewares.
If you want to distribute your simulation in a multinode infrastructure,
MORSE provides by default a socket service for multinode synchronization. If
you want to use HLA, you have to first install the CERTI and PyHLA packages.
Manual installation
-------------------
The directory where MORSE is installed will be referred to as $MORSE_ROOT
in this document.
It is recommended to store this environment variable, as it is necessary to
use the Builder API scripts to generate simulation
scenes with custom equipped robots.
Prerequisites
+++++++++++++
- cmake
- Python (3.3 or +)
- python-dev package
- Blender (>= 2.65) build with Python >= 3.3. You can simply get a binary from
Blender website
If building on Windows, ensure that your Python version and architecture matches
the bundled Python in Blender (currently Python 3.5.3 for Blender 2.79).
Installation
++++++++++++
Linux
-----
Download the latest version of the source code. It is stored in a git
repository::
$ git clone https://github.com/morse-simulator/morse.git
You can also get a tarball version here.
Go to the directory where you have previously downloaded the MORSE source.
Then type these commands::
$ mkdir build && cd build
$ cmake ..
By default, MORSE will install in /usr/local. You can easily change the
install directory by giving additional parameters to cmake. You can also
change the installation type and disable use middleware bindings by using
these additional parameters.
- CMAKE_INSTALL_PREFIX controls where will be installed MORSE. The install
prefix directory is referred to as $MORSE_ROOT.
- BUILD_CORE_SUPPORT controls the builds and install of Morse core. It is
ON by default
- BUILD_DOC_SUPPORT controls the build of the documentation (require
sphinx)
- BUILD_HLA_SUPPORT controls the builds of HLA support for multi-node
simulations in MORSE
- BUILD_POCOLIBS_SUPPORT controls the build of pocolibs support in MORSE.
- BUILD_YARP_SUPPORT controls the build of YARP support in MORSE.
- BUILD_ROS_SUPPORT controls the build of ROS support in MORSE.
- BUILD_MOOS_SUPPORT controls the build of MOOS support in MORSE.
- PYMORSE_SUPPORT controls the build and installation of pymorse, a
library to interact with Morse through the socket interface. It is needed
for test infrastructure.
- CMAKE_BUILD_TYPE controls the optimization stuff for C/C++ extension
(Release is a good choice).
- PYTHON_EXECUTABLE indicate where the python executable is in your system
(must be >= 3.3)
You can set up the different variables using the command line.
For instance, to build and install MORSE with YARP support in /opt, you need something like::
$ cmake -DBUILD_YARP_SUPPORT=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/opt ..
Or to tell MORSE where to find a Python installed in a different location::
$ cmake -DPYTHON_EXECUTABLE=/usr/local/bin/python3.3 ..
Alternatively, you can use ccmake .. to change all of these parameters using a
graphical interface. You can modify many different variables by switching to
"advanced mode" (pressing the t key).
After configuring the necessary parameters, compile with::
$ sudo make install
The optional $MORSE_BLENDER environment variable can be set to let the
simulator know where to look for Blender if it is not accessible from the
path.
You can check your configuration is ok with::
$ morse check
When updating MORSE to a more recent version, you'll simply have to do::
$ git checkout [version]
$ cd build
$ make install
Windows
-------
Download the latest version of the source code. It is stored in a git
repository::
$ git clone https://github.com/morse-simulator/morse.git
The MORSE_BLENDER environment variable should be set to the location and filename
of the Blender executable (ie "C:\Program Files\Blender\blender.exe").
Additionally, both cmake and Python should be on the system path.
Go to the directory where you have previously downloaded the MORSE source.
Then run the winbuild.bat script.
By default, MORSE will install in C:\morse. You can easily change the
install directory by editing the MORSE_ROOT variable in
winbuild.bat
Installation troubleshooting
----------------------------
In case of problems installing MORSE, verify the list of Frequently Asked
Questions.