]>
Commit | Line | Data |
---|---|---|
753453e4 | 1 | INSTALL - CUPS v1.2.0 - 12/26/2001 |
61bdcfa6 | 2 | ---------------------------------- |
3 | ||
93d2f0c0 | 4 | This file describes how to compile and install CUPS from source |
5 | code. For more information on CUPS see the file called | |
6 | "README.txt". A complete change log can be found in | |
7 | "CHANGES.txt". | |
61bdcfa6 | 8 | |
9 | ||
10 | BEFORE YOU BEGIN | |
11 | ||
93d2f0c0 | 12 | You'll need ANSI-compliant C and C++ compilers, plus a make |
13 | program and Bourne shell. The GNU compiler tools work well - | |
14 | we've tested the current CUPS code against GCC 2.95.x with | |
15 | excellent results. | |
61bdcfa6 | 16 | |
93d2f0c0 | 17 | The makefiles used by the project should work with all versions |
18 | of make. We've tested them with GNU make as well as the make | |
19 | programs shipped by Compaq, HP, SGI, and Sun. FreeBSD users | |
20 | should use GNU make (gmake). | |
61bdcfa6 | 21 | |
22 | Besides these tools you'll want the following libraries: | |
23 | ||
24 | - JPEG 6b or higher | |
25 | - PNG 1.0.6 or higher | |
26 | - TIFF 3.4 or higher | |
27 | - ZLIB 1.1.3 or higher | |
28 | ||
29 | CUPS will compile and run without these, however you'll miss out on | |
30 | many of the features provided by CUPS. | |
31 | ||
32 | ||
33 | CONFIGURATION | |
34 | ||
35 | CUPS uses GNU autoconf, so you should find the usual "configure" | |
36 | script in the main CUPS source directory. To configure CUPS for | |
37 | your system, type: | |
38 | ||
93d2f0c0 | 39 | ./configure ENTER |
40 | ||
41 | The default installation will put the CUPS software in the | |
42 | "/etc", "/usr", and "/var" directories on your system, which | |
43 | will overwrite any existing printing commands on your system. | |
44 | Use the "--prefix" option to install the CUPS software in | |
45 | another location: | |
46 | ||
47 | ./configure --prefix=/some/directory ENTER | |
48 | ||
93d2f0c0 | 49 | If the PNG, JPEG, TIFF, and ZLIB libraries are not installed in |
50 | a system default location (typically "/usr/include" and | |
753453e4 | 51 | "/usr/lib") you'll need to set the CFLAGS, CXXFLAGS, DSOFLAGS, |
52 | and LDFLAGS environment variables prior to running configure: | |
93d2f0c0 | 53 | |
54 | setenv CFLAGS "-I/some/directory" ENTER | |
55 | setenv CXXFLAGS "-I/some/directory" ENTER | |
753453e4 | 56 | setenv DSOFLAGS "-L/some/directory" ENTER |
93d2f0c0 | 57 | setenv LDFLAGS "-L/some/directory" ENTER |
58 | ./configure ... ENTER | |
59 | ||
60 | or: | |
61 | ||
62 | CFLAGS="-I/some/directory"; export CFLAGS ENTER | |
63 | CXXFLAGS="-I/some/directory"; export CXXFLAGS ENTER | |
753453e4 | 64 | DSOFLAGS="-L/some/directory"; export DSOFLAGS ENTER |
93d2f0c0 | 65 | LDFLAGS="-L/some/directory"; export LDFLAGS ENTER |
66 | ./configure ... ENTER | |
67 | ||
7428af94 | 68 | To enable support for encryption, you'll also want to add the |
69 | "--enable-ssl" option: | |
70 | ||
71 | ./configure --enable-ssl | |
72 | ||
73 | SSL and TLS support require the OpenSSL library, available at: | |
74 | ||
75 | http://www.openssl.org | |
76 | ||
753453e4 | 77 | If the OpenSSL header files and libraries are not in a standard |
78 | location, specify the locations of these files using the | |
79 | --with-openssl-includes and --with-openssl-libs directives: | |
80 | ||
81 | ./configure --enable-ssl \ | |
82 | --with-openssl-includes=/foo/bar/include \ | |
83 | --with-openssl-libs=/foo/bar/lib | |
84 | ||
1c9e0181 | 85 | See the file "ENCRYPTION.txt" for information on using the |
86 | encryption support in CUPS. | |
87 | ||
93d2f0c0 | 88 | Once you have configured things, just type: |
89 | ||
90 | make ENTER | |
91 | ||
753453e4 | 92 | or if you have FreeBSD, NetBSD, or OpenBSD type: |
93d2f0c0 | 93 | |
94 | gmake ENTER | |
95 | ||
96 | to build the software. | |
97 | ||
98 | ||
99 | INSTALLING THE SOFTWARE | |
100 | ||
101 | Once you have built the software you need to install it. The | |
102 | "install" target provides a quick way to install the software on | |
103 | your local system: | |
104 | ||
105 | make install ENTER | |
106 | ||
753453e4 | 107 | or for FreeBSD, NetBSD, or OpenBSD: |
93d2f0c0 | 108 | |
109 | gmake install ENTER | |
110 | ||
111 | You can also build binary packages that can be installed on other | |
112 | machines using the RPM spec file ("cups.spec") or EPM list file | |
113 | ("cups.list"). The latter also supports building of binary RPMs, | |
114 | so it may be more convenient to use - we use EPM to build all of | |
115 | our binary distributions. | |
116 | ||
117 | You can find the RPM software at: | |
118 | ||
119 | http://www.rpm.org | |
120 | ||
121 | The RPM software is at: | |
122 | ||
123 | http://www.easysw.com/epm | |
124 | ||
125 | ||
126 | CREATING BINARY DISTRIBUTIONS WITH EPM | |
127 | ||
128 | The top level makefile supports generation of many types of binary | |
129 | distributions using EPM. To build a binary distribution type: | |
130 | ||
131 | make <format> ENTER | |
132 | ||
133 | or | |
134 | ||
135 | gmake <format> ENTER | |
136 | ||
753453e4 | 137 | for FreeBSD, NetBSD, and OpenBSD. The <format> target is one of |
138 | the following: | |
93d2f0c0 | 139 | |
140 | epm - Builds a portable shell script and tar file based | |
141 | distribution. This format will also backup your | |
142 | existing printing system if you decide to remove | |
143 | CUPS at some future time. | |
753453e4 | 144 | aix - Builds an AIX binary distribution. |
145 | bsd - Builds a *BSD binary distribution. | |
93d2f0c0 | 146 | deb - Builds a Debian binary distribution. |
147 | depot - Builds a HP-UX binary distribution. | |
148 | pkg - Builds a Solaris binary distribution. | |
753453e4 | 149 | rpm - Builds a RPM binary distribution. |
93d2f0c0 | 150 | tardist - Builds an IRIX binary distribution. |
151 | ||
152 | ||
153 | REPORTING PROBLEMS | |
154 | ||
155 | If you have problems, READ THE DOCUMENTATION FIRST! If the | |
156 | documentation does not solve your problems please send an email | |
157 | to "cups-support@cups.org". Include your operating system and | |
158 | version, compiler and version, and any errors or problems you've | |
159 | run into. The "/var/log/cups/error_log" file should also be sent, | |
160 | as it often helps to determine the cause of your problem. | |
161 | ||
162 | If you are running a version of Linux, be sure to provide the | |
163 | Linux distribution you have, too. | |
164 | ||
165 | Please note that the "cups-support@cups.org" email address goes | |
166 | to the CUPS developers; they are busy people, so your email may | |
167 | go unanswered for days or weeks. In general, only general build | |
168 | or distribution problems will actually get answered - for | |
169 | end-user support see the "README.txt" for a summary of the | |
170 | resources available. |