-
Notifications
You must be signed in to change notification settings - Fork 0
/
INSTALL
147 lines (109 loc) · 5.42 KB
/
INSTALL
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
Basic Installation
==================
These are generic installation instructions.
For the installation of the system it is only necessary to invocke the command:
make install
This command build the system and install it into the predefined path
(/usr/local). It is possible to change the basic installation path with the command:
export prefix=/new_path
make -e install
or
make prefix='/new_path'
In any case the two command overrides the make variables.
Use make uninstall if you want to remove the installed files.
If you want build only the system:
make
or
make all
Use make clean to clean all the file generated with make all and make info.
For the generation of the reference documentation:
make info
or make ps/pdf/dvi
The doxygen and doxyfilter is required.
Basic Installation for Qt users
===============================
For building your project for Qt 2.x you need tmake. On SuSE it is hidden
in a package called qt-freebies. It can be downloaded from
http://www.trolltech.com/developer/download/tmake.html. In others distribution
the tmake is present without additional configuration.
You have to set TMAKEPATH to point to your development environment and run
tmake:
export TMAKEPATH=/usr/lib/tmake/linux-g++ # path depends on your system
For building your project for Qt 3.x you need qmake.
Set the QMAKE variable correctly into the Makefile.
It is important that the QTDIR environment variable is set to the correct
place of the Qt installation directory.
Path specifications for standard project
========================================
It is possible to specify the following paths:
'prefix'
A prefix used in constructing the default values of the variables listed below.
The default value of prefix should be `/usr/local'.
'exec_prefix'
A prefix used in constructing the default values of some of the variables listed
below. The default value of exec_prefix should be $(prefix).
'bindir'
The directory for installing executable programs that users can run. This should
normally be `/usr/local/bin', but write it as `$(exec_prefix)/bin'.
'datadir'
The directory for installing read-only architecture independent data files. This
should normally be `/usr/local/share', but write it as `$(prefix)/share'.
'libdir'
The directory for object files and libraries of object code. Do not install
executables here, they probably ought to go in `$(libexecdir)' instead. The
value of libdir should normally be `/usr/local/lib', but write it as
`$(exec_prefix)/lib'.
'infodir'
The directory for installing the Info files for this package. By default, it
should be `/usr/local/info', but it should be written as `$(prefix)/info'.
'includedir'
The directory for installing header files to be included by user programs with
the C `#include' preprocessor directive. This should normally be
`/usr/local/include', but write it as `$(prefix)/include'.
Make targets for standard project
=================================
It is possible to specify the following targets:
'all'
This should be the default target. Compile the entire program, but the
documentation files. Info files should normally be included in
the distribution, but it should generated explicitally by means of the 'Info' target.
Some related sub-targets are present:
- 'lib': generates the libraries. Two sub-target are present:
- 'dynamiclib': generates the dynamically linked library
- 'staticlib': generates the statically linked library
- 'exe': generates the executable
'install'
Compile the program and copy the executables, libraries, and so on to the file
names where they should reside for actual use. If possible, write the install
target rule so that it does not modify anything in the directory where the
program was built, provided `make all' has just been done. This is convenient
for building the program under one user name and installing it under another.
The commands should create all the directories in which files are to be
installed, if they don't already exist. This includes the directories specified
as the values of the variables prefix and exec_prefix, as well as all
subdirectories that are needed.
'uninstall'
Delete all the installed files--the copies that the `install' target creates.
This rule should not modify the directories where compilation is done, only the
directories where files are installed.
'clean'
Delete all files from the current directory that are normally created by
building the program. Don't delete the files that record the configuration. Also
preserve files that could be made by building, but normally aren't because the
distribution comes with them.
'info'
Generate any Info files needed. This command generates the reference documentation
automatically generated with Doxygen. Some related targets are present:
- 'ps': generate the ps file containing the reference documentation
- 'pdf': generate the pdf file containing the reference documentation
- 'dvi': generate the dvi file containing the reference documentation
The doxygen and doxyfilter executable should be installed into your system.
'dist'
Create a distribution tar file for this program. The tar file should be set up
so that the file names in the tar file start with a subdirectory name which is
the name of the package it is a distribution for.
'distclean'
Delete all files from the current directory that are created by configuring or
building the program. If you have unpacked the source and built the program
without creating any other files, `make distclean' should leave only the files
that were in the distribution.