-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathREADME
80 lines (51 loc) · 2.42 KB
/
README
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
Copyright (c) 1993-2011 LAAS/CNRS
-- EXTERNAL TOOLS REQUIREMENTS ------------------------------
- autoconf version 2.59 or later
- automake version 1.8 or later
- make version 3.79 or later <http://www.gnu.org/software/make/make.html>
- pkgconfig version 0.15 or later (usually part of Gnome devlpmt packages)
- groff 1.10 or later (Usually part of system packages).
- Tcl/Tk 8.0 or later development files (for eltclsh) <http://tcl.tk/>
-- GETTING LAAS/OPENROBOTS TOOLS -----------------------------
<http://www.openrobots.org/>
- mkdep: LAAS tool to determine dependencies
- pocolibs: system communication and real-time primitives
- libedit (editline): generic line editing and history functions
- eltclsh: interactive TCL shell (optional but very practical)
- GenoM: generator of modules
--- ROBOTPKG -------------------------------------------------
The easiest way to install Genom and most of the openrobots
tools is to use robotpkg.
See <http://robotpkg.openrobots.org/> for details.
--- INSTALLATION INSTRUCTIONS --------------------------------
Instructions when not using robotpkg:
Most of the time, it is a simple sequence of untar, autogen, configure,
build, and install. Configure options may vary, and some packages don't
require the autogen step. It is recommended that you build in a separate
directory.
Use './configure --help' to find out all the available configure
options.
The --prefix option (default: /usr/local) defines the base directory
of the installation. We recommend a dedicated path (eg,
$PREFIX=/usr/local/openrobots).
The --exec-prefix option allows to specify where to install binaries.
The default value (equal to --prefix) is usualy great. But if you have
different type of machine sharing this files tree, you will have to define
dedicated path like --exec-prefix=$PREFIX/$MACHTYPE-$OSTYPE (eg,
--exec-prefix=$PREFIX/i386-linux, for a PC running linux).
On some systems, --with-tcl=DIR and --with-tk=DIR will be
required to specify where to find tclConfig.sh (resp. tkConfig.h).
-- EXAMPLE for "mkdep-XYZ" :
tar xfvz mkdep-XYZ.tar.gz
cd mkdep-XYZ
[./autogen.sh] (only for libedit, eltclsh and GenoM)
mkdir build
cd build
../configure --prefix=$PREFIX
make
make install
--- CONFIGURATIONS -----------------------------------------
Modify (or set if not previously defined) the following
environment variables :
PATH : add ${exec_prefix}/bin
PKG_CONFIG_PATH : add ${exec_prefix}/lib/pkgconfig