Mercurial > pidgin

comparison INSTALL @ 21100:29d8c86c14cd

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
propagate from branch 'im.pidgin.pidgin' (head cd2be742f6c45c200000003fc5a6341297bbe857) to branch 'im.pidgin.cpw.khc.msnp14.soap' (head 1d7d51174ae87c7f03bb1290a8e447bf2a1704a5)
author Ka-Hing Cheung <khc@hxbc.us>
date Thu, 04 Oct 2007 06:13:01 +0000
parents f46ae7e62d13
children 5ab7766a6c83
comparison
equal deleted inserted replaced
20537:c49b886231d5 21100:29d8c86c14cd
30 using `csh' on an old version of System V, you might need to type 30 using `csh' on an old version of System V, you might need to type
31 `sh ./configure' instead to prevent `csh' from trying to execute 31 `sh ./configure' instead to prevent `csh' from trying to execute
32 `configure' itself. 32 `configure' itself.
33 33
34 Running `configure' takes awhile. While running, it prints some 34 Running `configure' takes awhile. While running, it prints some
35 messages telling which features it is checking for. 35 messages telling which features it is checking for. If it finishes
36 36 successfully, it will print out of a summary of the build options.
37 2. Type `make' to compile the package. 37 This summary will also appear in the help->about dialog.
38
39 2. Type `make' to compile the package. On some systems, you may need
40 to use `gmake' instead.
38 41
39 3. Optionally, type `make check' to run any self-tests that come with 42 3. Optionally, type `make check' to run any self-tests that come with
40 the package. 43 the package.
41 44
42 4. Type `make install' to install the programs and any data files and 45 4. Type `make install' to install the programs and any data files and
43 documentation. 46 documentation. You must have write access to the prefix you are
47 installing to. See below for more details on the prefix.
44 48
45 5. You can remove the program binaries and object files from the 49 5. You can remove the program binaries and object files from the
46 source code directory by typing `make clean'. To also remove the 50 source code directory by typing `make clean'. To also remove the
47 files that `configure' created (so you can compile the package for 51 files that `configure' created (so you can compile the package for
48 a different kind of computer), type `make distclean'. There is 52 a different kind of computer), type `make distclean'. There is
49 also a `make maintainer-clean' target, but that is intended mainly 53 also a `make maintainer-clean' target, but that is intended mainly
50 for the package's developers. If you use it, you may have to get 54 for the package's developers. If you use it, you may have to get
51 all sorts of other programs in order to regenerate files that came 55 all sorts of other programs in order to regenerate files that came
52 with the distribution. 56 with the distribution.
57
58 6. If you have *not* run make distclean, you can use the target
59 `make uninstall` to remove the files installed by `make install`.
53 60
54 Compilers and Options 61 Compilers and Options
55 ===================== 62 =====================
56 63
57 Some systems require unusual options for compilation or linking that 64 Some systems require unusual options for compilation or linking that
117 For packages that use the X Window System, `configure' can usually 124 For packages that use the X Window System, `configure' can usually
118 find the X include and library files automatically, but if it doesn't, 125 find the X include and library files automatically, but if it doesn't,
119 you can use the `configure' options `--x-includes=DIR' and 126 you can use the `configure' options `--x-includes=DIR' and
120 `--x-libraries=DIR' to specify their locations. 127 `--x-libraries=DIR' to specify their locations.
121 128
129 By default both the GTK+ UI (Pidgin) and the ncurses UI (Finch) will be
130 built, assuming that configure finds the necessary libraries and headers for
131 each. You can disable the GTK+ UI with `--disable-gtkui' and the ncurses UI
132 with `--disable-consoleui'.
133
134 `--disable-screensaver' will build libpurple without support for detecting
135 when it should mark accounts idle based on mouse or keyboard usage.
136
137 `--disable-sm' will build without support for the X session management.
138 Doing so will remove the ability to have pidgin start up with your window
139 manager.
140
141 `--disable-gtkspell' will remove the ability to highlight misspelled words.
142
143 `--disable-gevolution' will cause the evolution integration plugin not to
144 compile.
145
146 `--disable-gstreamer' will build without sound support. This applies to
147 *both* Pidgin and Finch.
148
149 `--enable-gnutls=yes,no' will enable or disable the use of gnutls for ssl support. Disabling both gnutls and nss will mean you cannot use either MSN or Google Talk. There is no static option for gnutls at this time.
150
151 `--enable-nss=yes,no,static' will enable or disable the use of nss for ssl support. This is the only option for ssl support if you are attempting to compile a static version of Pidgin or Finch.
152
153 Optional Packages:
154
155 `--with-silc-includes=DIR' and `--with-silc-libs=DIR' can be used if your silc libraries are installed to a location not in your path.
156
157 `--with-static-prpls' takes a list of comma separated protocols to build in statically (rather than as plugins). Use this with care.
158
159 `--with-dynamic-prpls' takes a list of comma separated protocols also. If used only those listed will be built. If no protocols are listed with either `--with-static-prpls' or with `--with-dynamic-prpls' then Pidgin and Finch will be effectively useless.
160
161 If configure does not find python, it will build without DBUS support. Thiswill disable scripts such as purple-remote and purple-uri-handler, effectively disabling integration with the browser. You can tell configure where your python binary is located with `--with-python=PATH'
162
122 Specifying the System Type 163 Specifying the System Type
123 ========================== 164 ==========================
124 165
125 There may be some features `configure' can not figure out 166 There may be some features `configure' can not figure out
126 automatically, but needs to determine by the type of host the package 167 automatically, but needs to determine by the type of host the package
177 218
178 `--version' 219 `--version'
179 Print the version of Autoconf used to generate the `configure' 220 Print the version of Autoconf used to generate the `configure'
180 script, and exit. 221 script, and exit.
181 222
182 `configure' also accepts some other, not widely useful, options. 223 `configure' also accepts some other, not widely useful, options. Many of these are related to having various optional libaries installed to locations outside of your path.