]> git.ipfire.org Git - thirdparty/cups.git/blame - INSTALL.txt
Merge changes from 1.1.x into 1.2 devel.
[thirdparty/cups.git] / INSTALL.txt
CommitLineData
753453e4 1INSTALL - CUPS v1.2.0 - 12/26/2001
61bdcfa6 2----------------------------------
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
9
10BEFORE YOU BEGIN
11
93d2f0c0 12You'll need ANSI-compliant C and C++ compilers, plus a make
13program and Bourne shell. The GNU compiler tools work well -
14we've tested the current CUPS code against GCC 2.95.x with
15excellent results.
61bdcfa6 16
93d2f0c0 17The makefiles used by the project should work with all versions
18of make. We've tested them with GNU make as well as the make
19programs shipped by Compaq, HP, SGI, and Sun. FreeBSD users
20should use GNU make (gmake).
61bdcfa6 21
22Besides 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
29CUPS will compile and run without these, however you'll miss out on
30many of the features provided by CUPS.
31
32
33CONFIGURATION
34
35CUPS uses GNU autoconf, so you should find the usual "configure"
36script in the main CUPS source directory. To configure CUPS for
37your system, type:
38
93d2f0c0 39 ./configure ENTER
40
41The default installation will put the CUPS software in the
42"/etc", "/usr", and "/var" directories on your system, which
43will overwrite any existing printing commands on your system.
44Use the "--prefix" option to install the CUPS software in
45another location:
46
47 ./configure --prefix=/some/directory ENTER
48
93d2f0c0 49If the PNG, JPEG, TIFF, and ZLIB libraries are not installed in
50a system default location (typically "/usr/include" and
753453e4 51"/usr/lib") you'll need to set the CFLAGS, CXXFLAGS, DSOFLAGS,
52and 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
60or:
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 68To enable support for encryption, you'll also want to add the
69"--enable-ssl" option:
70
71 ./configure --enable-ssl
72
73SSL and TLS support require the OpenSSL library, available at:
74
75 http://www.openssl.org
76
753453e4 77If the OpenSSL header files and libraries are not in a standard
78location, 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 85See the file "ENCRYPTION.txt" for information on using the
86encryption support in CUPS.
87
93d2f0c0 88Once you have configured things, just type:
89
90 make ENTER
91
753453e4 92or if you have FreeBSD, NetBSD, or OpenBSD type:
93d2f0c0 93
94 gmake ENTER
95
96to build the software.
97
98
99INSTALLING THE SOFTWARE
100
101Once you have built the software you need to install it. The
102"install" target provides a quick way to install the software on
103your local system:
104
105 make install ENTER
106
753453e4 107or for FreeBSD, NetBSD, or OpenBSD:
93d2f0c0 108
109 gmake install ENTER
110
111You can also build binary packages that can be installed on other
112machines using the RPM spec file ("cups.spec") or EPM list file
113("cups.list"). The latter also supports building of binary RPMs,
114so it may be more convenient to use - we use EPM to build all of
115our binary distributions.
116
117You can find the RPM software at:
118
119 http://www.rpm.org
120
121The RPM software is at:
122
123 http://www.easysw.com/epm
124
125
126CREATING BINARY DISTRIBUTIONS WITH EPM
127
128The top level makefile supports generation of many types of binary
129distributions using EPM. To build a binary distribution type:
130
131 make <format> ENTER
132
133or
134
135 gmake <format> ENTER
136
753453e4 137for FreeBSD, NetBSD, and OpenBSD. The <format> target is one of
138the 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
153REPORTING PROBLEMS
154
155If you have problems, READ THE DOCUMENTATION FIRST! If the
156documentation does not solve your problems please send an email
157to "cups-support@cups.org". Include your operating system and
158version, compiler and version, and any errors or problems you've
159run into. The "/var/log/cups/error_log" file should also be sent,
160as it often helps to determine the cause of your problem.
161
162If you are running a version of Linux, be sure to provide the
163Linux distribution you have, too.
164
165Please note that the "cups-support@cups.org" email address goes
166to the CUPS developers; they are busy people, so your email may
167go unanswered for days or weeks. In general, only general build
168or distribution problems will actually get answered - for
169end-user support see the "README.txt" for a summary of the
170resources available.