forked from KDE/marble
-
Notifications
You must be signed in to change notification settings - Fork 0
/
INSTALL
154 lines (87 loc) · 3.83 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
This file describes how to build and install Marble
The most recent version of this file can be found at:
http://marble.kde.org/sources.php
Please refer to the online version above if possible.
NOTE: This file describes how to build Marble as a stand-alone
application. If you are building Marble as part of the KDE-EDU
module, then you should instead read the file INSTALL in the top
level directory of this module and ignore this one. This is
most likely ../INSTALL.
Prerequisites for building Marble are:
- Qt 4.7 or newer
- cmake version 2.4 or newer
- (optional): kdelibs from the KDE subversion repositories.
- other dependencies are optional
A checkout of Marble. You can check out Marble using GIT via the command:
git clone git://anongit.kde.org/marble ~/marble/sources
You can build and install Marble in two different ways:
1. As a Qt-only application.
2. As a KDE application, using kdelibs and KDE based classes.
Choose one of them and read below for how to do it.
NOTE: If you wish to build Marble with debug info include the argument
-DCMAKE_BUILD_TYPE=debug in the cmake command below.
1. Build Marble as a Qt only application.
1.1 Create a build directory
Create a build directory parallel to the source directory. Suppose
that the source directory is named 'marble'. Then create a new
directory called 'marble-build'.
1.2 Configure the build tree
Go into the build directory and type
cmake -DQTONLY=ON ../marble
By default, marble is installed into /usr/local. If you want to
install it into any other directory, add
-DCMAKE_INSTALL_PREFIX=/path/to/install/into like in this example:
cmake -DQTONLY=ON -DCMAKE_INSTALL_PREFIX=~/apps ../marble
If you have no write permission to the installation directory of cmake
(because you have a system installed cmake) you need to add another
parameter -DPACKAGE_ROOT_PREFIX=~/apps to the cmake command:
cmake -DQTONLY=ON -DCMAKE_INSTALL_PREFIX=~/apps \
-DPACKAGE_ROOT_PREFIX=~/apps ../marble
To modify the position of the data directory at compile time, see the notes
at 3.1 .
1.3 Build marble
Also in the build directory, type:
make
1.4 Install marble
Finally, also from the build directory, type:
make install
and start Marble either from the menu or via the command line:
marble
2. Build Marble as a KDE application.
2.1 Create a build directory
This is the same step as for a Qt-only build:
Create a build directory parallel to the source directory. Suppose
that the source directory is named 'marble'. Then create a new
directory called 'marble-build'.
2.2 Configure the build tree
Go into the build directory and type
cmake ../marble
From now on the steps are the same as for a Qt-only build.
2.3 Build marble
make
2.4 Install marble
make install
and start Marble either from the menu or via the command line:
marble
3 Adjust Marble's search path for the maps and data
There are several ways to adjust the path where Marble is
drawing it's data from:
3.1 At Compiletime
Use the cmake option -DMARBLE_DATA_PATH to specify the
built-in system path that Marble gathers its data from:
Example:
cmake -DQTONLY=ON -DMARBLE_DATA_PATH /mnt1/marble/data ~/marble
3.2 "At Runtime"
There are two solutions to adjust the data path for a
precompiled Marble binary:
a) Enter a key and a value
marbleDataPath="/smb/marble/data"
to the config file "marblerc" or
"~/.config/KDE/Marble\ Desktop\ Globe.conf" and (re)start the
application.
b) Start Marble using the command line option --marbleDataPath:
marble --marbleDataPath ~/marble/data
4. Known Issues:
- If you don't specify any install path using cmake then Marble will probably install under /usr/local.
If your distribution doesn't include /usr/local/lib in your LD_LIBRARY_PATH you might need to add that directory via:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib