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