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
|
<chapter>
<title>Building PowerShell</title>
<para>
This chapter explains the procedure of compiling PowerShell from
the source code. If you do not want to do this, feel free to
grab a precompiled
<ulink url="http://www.rpm.org/"><citetitle>RPM</citetitle></ulink> or
<ulink url="http://www.debian.org/"><citetitle>Debian package</citetitle></ulink>
of PowerShell.
<note><title>Note</title>
<para>
This follows the same procedure as most
<ulink url="http://www.gnu.org/"><citetitle>GNU</citetitle></ulink>
software, so if you are familiar with the configure/make/make install
procedure, you may skip this section.
</para>
</note>
</para>
<sect1 id="powershell-configuring">
<title>Configuring PowerShell</title>
<sect2>
<title>The General Case</title>
<para>
PowerShell uses GNU
<ulink url="http://www.gnu.org/software/autoconf/autoconf.html">
<citetitle>autoconf</citetitle></ulink>, like most GNU software,
and has a pretty standard build procedure. In the simplest case,
configuring PowerShell consists of the following (you must be in the
directory where you unpacked the source.)
</para>
<para>
<ProgramListing>
./configure
</ProgramListing>
</para>
<para>
This will check your system for some standard libraries as well as
make sure that you have the proper version of GTK+ and gnome-libs.
If all is well, it will create the Makefile for the program. Since
you did not specify otherwise, it will install it under
<Literal>/usr/local</Literal>.
</para>
</sect2>
<sect2>
<title>Specifying Options</title>
<para>
PowerShell's configure script currently does not have many useful
arguments. The only one which is really of any use is the
<Literal>--prefix</Literal> option. It works like this:
</para>
<para>
<ProgramListing>
./configure --prefix=/usr
</ProgramListing>
</para>
<para>
This tells configure that you want to install PowerShell in
<Literal>/usr</Literal> rather than <Literal>/usr/local</Literal>.
The binary will be installed in <Literal>/usr/bin</Literal> rather
than <Literal>/usr/local/bin</Literal>.
</para>
</sect2>
<sect2>
<title><Literal>configure</Literal>'s output</title>
<para>
If all goes well, you should see output such as the following:
</para>
<para>
<ProgramListing>
creating cache ./config.cache
checking for gcc... gcc
checking whether the C compiler (gcc ) works... yes
checking whether the C compiler (gcc ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for a BSD compatible install... /usr/bin/install -c
checking for GTK+ 1.2 or greater... yes
checking for Gnome 1.0.13 or greater... yes
checking for gdk_imlib_init in -lgdk_imlib... yes
checking for login_tty in -lutil... yes
checking for zvt_term_match_add in -lzvt... yes
checking for zvt_term_match_check in -lzvt... yes
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... no
checking for fcntl.h... yes
checking for sys/time.h... yes
checking for unistd.h... yes
checking for strstr... no
updating cache ./config.cache
creating ./config.status
creating Makefile
creating config.h
</ProgramListing>
</para>
<para>
One difference you may notice is that <Literal>configure</Literal>
may not be able to find <Literal>zvt_term_match_add</Literal> or
<Literal>zvt_term_match_check</Literal>. This means your version of
gnome-libs is relatively old and doesn't support URL matching in
<Literal>ZvtTerm</Literal> (which is what PowerShell uses to draw
the terminal itself). This will not prevent you from compiling and
running PowerShell successfully, but it will not be compiled with
support for URL matching.
</para>
</sect2>
<sect2>
<title>Troubleshooting</title>
<para>
If all is not well, you may need to
examine config.log and see exactly what happened. In most cases,
this happens when either your library versions are too old or
configure is finding the wrong version of gtk-config or gnome-config.
Check your PATH variable to make sure the correct one (the one from
the newest version you have installed) comes before the older versions
in your path. Or even better, delete the older versions.
</para>
<para>
This is the first program I've written that uses a
<Literal>configure</Literal> script, and because of this there may
be bugs in it. One has been reported to be when running under Solaris,
but there may be others.
</para>
</sect2>
</sect1>
<sect1 id="powershell-compiling">
<title>Compiling PowerShell</title>
<sect2>
<title>Running <Literal>make</Literal></title>
<para>
If you have not yet configured PowerShell, please go back
and read the section on
<link linkend="powershell-configuring">configuring PowerShell</link>.
</para>
<para>
Once you have successfully configured PowerShell, you are ready to
build it. This is the easiest step of all - just a simple command:
</para>
<para>
<ProgramListing>
make
</ProgramListing>
</para>
<para>
This should go through each source file and compile it. You will see
output from <Literal>gcc</Literal> (the C compiler) at this point.
There should not be any problems at this point - if there are, please
let me know.
</para>
</sect2>
</sect1>
<sect1>
<title>Final Steps</title>
<sect2>
<title>Installing PowerShell</title>
<para>
Once you have successfully compiled PowerShell, installing it is
easy. All it takes is:
</para>
<para>
<ProgramListing>
make install
</ProgramListing>
</para>
<para>
This will install PowerShell in the directory you specified when you
were configuring it (or <Literal>/usr/local/bin</Literal> if you didn't
specify anything.)
</para>
<para>
At this point, if you wish, you can delete the whole directory containing
the source for PowerShell.
</para>
</sect2>
<sect2>
<title>Running PowerShell</title>
<para>
Once PowerShell is installed, you can run it by typing
<Literal>/path/to/powershell</Literal> (obviously, replace
<Literal>/path/to</Literal> with the directory in which you installed
it.) If the directory is in your current path (such as
<Literal>/usr/bin</Literal> or possibly <Literal>/usr/local/bin</Literal>),
you may just type <Literal>powershell</Literal>.
</para>
</sect2>
</sect1>
</chapter>
|
