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
|
<chapter id="installation">
<title>Installation</title>
<sect1 id="build-and-install">
<title>Build LCDproc</title>
<para>
Now that you have downloaded the LCDproc distribution you can
start building it.
</para>
<note>
<para>
If you have installed the debian package with apt-get (or another
debian tool), you can skip this this chapter.
</para>
</note>
<para>
If you're building this version from CVS, you'll need
autoconf, automake, aclocal & autoheader installed.
</para>
<para>
If you have autoconf and friends, run:
</para>
<screen>
<prompt>$</prompt> <userinput>sh autogen.sh</userinput>
</screen>
<para>
This produces the configure script and supporting files. It has allready
been run if you using the tarball distribution.
</para>
<para>
Once the above command has run, the rest is pretty standard:
</para>
<screen>
<prompt>$</prompt> <userinput>./configure --help</userinput>
</screen>
<para>
Read about the options, figure out what to use.
</para>
<screen>
<prompt>$</prompt> <userinput>./configure --prefix=/usr/local --enable-drivers=ncurses,cfontz</userinput>
</screen>
<para>
Be sure to replace /usr/local with the prefixdir you want (e.g. /usr
for RedHat) and ncurses,cfontz with comma-separated list
of drivers you want.
</para>
<screen>
<prompt>$</prompt> <userinput>make</userinput>
</screen>
<para>
Congratulations: You have just compiled your version of LCDproc ;)
</para>
</sect1>
<sect1 id="direct-install">
<title>Install LCDproc Directly From The Sources </title>
<para>
If you want to install LCDproc more or less permanently you
can run:
</para>
<screen>
<prompt>$</prompt> <userinput>su</userinput>
<prompt>Password:</prompt> <userinput>top secret</userinput>
<prompt>#</prompt> <userinput>make install</userinput>
</screen>
<note>
<para>
make install is absolutely OPTIONAL
You can also run LCDproc directly from the source directory. See
<link linkend="lcdd-commandline">below</link> for details.
</para>
</note>
</sect1>
<sect1 id="package-install">
<title>Generate And Install Packages of LCDproc</title>
<para>
As an alternative (which is actually better ;) to installing
directly from the sources you can generate packages using the
packaging tool EPM.
</para>
<para>
First of all you may need to download EPM from
<ulink url="http://www.easysw.com/epm/">http://www.easysw.com/epm/</ulink>
and install it according to the instructions that are included
in its source distribution.
</para>
<note>
<para>
There are of course other and maybe better ways to generate
packages for your system. The reason for us to choose EPM
was that it provide the developers with a tool that makes it
possible to write one list file for all platforms defining
what the resulting package is meant to look like. This way we
do not have to learn all the package managing tools of the
different platforms that are supported by LCDproc.
</para>
</note>
<para>
To generate an LCDproc package follow these instructions:
</para>
<tip>
<para>
It is of certain importance that you have run ./configure with
the correct pathname settings for your system. Otherwise the
resulting package will install the files in the wrong directories.
</para>
</tip>
<screen>
<prompt>$</prompt> <userinput>epm -v -f native LCDproc</userinput>
</screen>
<note>
<para>
Generating an RPM package as a non-root user will fail, RPM wants
to generate the files from the tree under <filename>/usr/src/RPM</filename>,
which you do not have write access to as a non-root user.
If you want to generate the package as a non-root user anyway, you may
want to follow these instructions.
</para>
</note>
<para>
A workaround for the described problem is creating a file named
<filename>~/.rpmmacros</filename>
which contains:
</para>
<screen>
<![CDATA[
%_topdir ~/rpm
]]>
</screen>
<important>
<para>
<filename>~/rpm</filename> must contain the same tree usually found under
<filename>/usr/src/RPM</filename>
</para>
</important>
<para>
Unfortunately epm does not read <filename>~/.rpmmacros</filename>
and of course returns warnings.
Don't worry! That's OK ;)
</para>
<para>
In order to actually install the generated package follow the instructions
in your system's manual.
</para>
</sect1>
</chapter>
|
