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
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
|
QBrew Installation (Unix)
=========================
Note: QBrew requires the Qt 3.2 or greater development library. This
can be found at <http://www.trolltech.com>. These instructions are for
building and installing QBrew on a Unix or Linux system using the X11
version of Qt. The configure script and makefiles are not designed for
Windows or Macintosh systems.
====================================================================
QBrew uses the 'configure' script to attempt a reasonable and
correct configuration for compilation on your system. It creates
an appropriate 'Makefile' for each directory in this package, along
with one or more header files containing system-dependent definitions.
It also creates 'config.status', 'config.cache' and 'config.log' files
that are useful for recreating or debugging the configuration.
If you have problems configurating and compiling this package,
please send me the details of your problem, your system information, and
the 'config.log' file. Note that I am not providing installation support
for QBrew, and will consider such a submission to be a bug report as
opposed to a support request. I can be contacted at <david@usermode.org>.
Sincerely,
David Johnson
QBrew Installation in a Nutshell:
=====================================
1) Type './configure'
2) Type 'make'
3) Type 'make install'
QBrew Installation in More Detail:
=====================================
0) Make sure that the prerequisite Qt 3.2 or greater library is installed
first. This can be found at <http://www.trolltech.com>.
1) Unzip and untar the package into its own directory. Change into this
directory, and read the README and LICENSE files. (I'm assuming that
you've read this, the INSTALL file :-))
2) Type './configure --help", and peruse the configure options available.
It may be necessary to use one or more of these options on your system.
3) Type './configure' to configure the package for your system. If you're
using `csh' on an old version of System V, you might need to type
`sh ./configure' instead.
4) Type 'make' to compile the package.
5) If you are not logged in as root, type 'su' and enter the root password
to switch over to the root account. This is not necessary if you
configured the package to install to your home directory.
6) Type 'make install' to install the program and documentation.
7) Run QBrew from the command line by typing 'qbrew'.
8) You can remove the executable and object files from the source code
directory by typing 'make clean'. You can uninstall the program and
documentation by typing 'make uninstall'.
A Note on the Qt Library
========================
Because there are two incompatible Qt versions in common use, some Unix
distributions have renamed the libqt.so library to libqt3.so (or some other
variation). If you are in this situation, set the environment variable LIBQT
to '-lqt3' and reconfigure. You may also have to set MOC to 'moc3'.
Qt can be built for single threaded or multithreaded applications. Sometimes
the configure script will incorrectly try to use the single threaded library
while building a multithreaded application. If this is the case, set the LIBQT
variable to '-lqt-mt'.
You can use the QTMIN and QTMAX environment variables to specify with
versions of Qt to search for during configuration. For example:
QTMIN=320 QTMAX=399 ./configure
Compilers and Options
=====================
Some systems require unusual options for compilation or linking that
the `configure' script does not know about. You can give `configure'
initial values for variables by setting them in the environment. Using
a Bourne-compatible shell, you can do that on the command line like
this:
CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
Or on systems that have the `env' program, you can do it like this:
env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
Compiling For Multiple Architectures
====================================
You can compile the package for more than one kind of computer at the
same time, by placing the object files for each architecture in their
own directory. To do this, you must use a version of `make' that
supports the `VPATH' variable, such as GNU `make'. `cd' to the
directory where you want the object files and executables to go and run
the `configure' script. `configure' automatically checks for the
source code in the directory that `configure' is in and in `..'.
If you have to use a `make' that does not supports the `VPATH'
variable, you have to compile the package for one architecture at a time
in the source code directory. After you have installed the package for
one architecture, use `make distclean' before reconfiguring for another
architecture.
Installation Names
==================
By default, `make install' will install the package's files in
`/usr/local/bin', `/usr/local/man', etc. You can specify an
installation prefix other than `/usr/local' by giving `configure' the
option `--prefix=PATH'.
You can specify separate installation prefixes for
architecture-specific files and architecture-independent files. If you
give `configure' the option `--exec-prefix=PATH', the package will use
PATH as the prefix for installing programs and libraries.
Documentation and other data files will still use the regular prefix.
If the package supports it, you can cause programs to be installed
with an extra prefix or suffix on their names by giving `configure' the
option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Some packages pay attention to `--enable-FEATURE' options to
`configure', where FEATURE indicates an optional part of the package.
They may also pay attention to `--with-PACKAGE' options, where PACKAGE
is something like `gnu-as' or `x' (for the X Window System). The
`README' should mention any `--enable-' and `--with-' options that the
package recognizes.
For packages that use the X Window System, `configure' can usually
find the X include and library files automatically, but if it doesn't,
you can use the `configure' options `--x-includes=DIR' and
`--x-libraries=DIR' to specify their locations.
Specifying the System Type
==========================
There may be some features `configure' can not figure out
automatically, but needs to determine by the type of host the package
will run on. Usually `configure' can figure that out, but if it prints
a message saying it can not guess the host type, give it the
`--host=TYPE' option. TYPE can either be a short name for the system
type, such as `sun4', or a canonical name with three fields:
CPU-COMPANY-SYSTEM
See the file `config.sub' for the possible values of each field. If
`config.sub' isn't included in this package, then this package doesn't
need to know the host type.
If you are building compiler tools for cross-compiling, you can also
use the `--target=TYPE' option to select the type of system they will
produce code for and the `--build=TYPE' option to select the type of
system on which you are compiling the package.
Sharing Defaults
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Operation Controls
==================
`configure' recognizes the following options to control how it
operates.
`--cache-file=FILE'
Use and save the results of the tests in FILE instead of
`./config.cache'. Set FILE to `/dev/null' to disable caching, for
debugging `configure'.
`--help'
Print a summary of the options to `configure', and exit.
`--quiet'
`--silent'
`-q'
Do not print messages saying which checks are being made.
`--srcdir=DIR'
Look for the package's source code in directory DIR. Usually
`configure' can determine that directory automatically.
`--version'
Print the version of Autoconf used to generate the `configure'
script, and exit.
`configure' also accepts some other, not widely useful, options.
Rebuilding the Configuration
============================
If you ever need to rebuild the configuration files, type the
following in the base directory of the distribution:
make -f Makefile.cvs
You will need the automake/autoconf set of programs.
|
