1qwtinstall(3)                  Qwt User's Guide                  qwtinstall(3)
2
3
4

NAME

6       qwtinstall - INSTALL
7
8       Introduction
9       ============
10
11       Qwt uses qmake to build all its components and examples.
12       qmake is part of a Qt distribution.
13
14       qmake reads project files, that contain the options and rules how to
15       build a certain project. A project file ends with the suffix '*.pro'.
16       Files that end with the suffix '*.pri' are included by the project
17       files and contain definitions, that are common for several project files.
18
19       qwtconfig.pri is read by all project files of the Qwt package.
20       So the first step is to edit qwtconfig.pri to adjust it to your
21       needs.
22
23       MathML Extension
24       ================
25
26       Qwt/Qt4 supports the MathML render engine from the Qt solutions package,
27       that is only available with a commercial Qt license.
28
29       You need a release of qtmmlwidget >= 2.1.
30       Copy the files qtmmlwidget.[cpp|h] to textengines/mathml.
31
32       Documentation
33       ==========================
34
35       Qwt includes a class documentation, that is available in various formats:
36
37       - Html files
38       - PDF document
39       - Qt Compressed Help (*.qch ) for the Qt assistant or creator.
40         You can load it 'Edit Preferences' -> 'Documentation' -> 'Add...'
41       - Man pages ( UNIX only )
42
43       A) Unix Qt3/Qt4
44       ==========================
45
46       qmake qwt.pro
47       make
48       make install
49
50       If you have installed a shared library it's path has to be known to
51       the run-time linker of your operating system. On Linux systems read
52       the LD_LIBRARY_PATH (on some systems LIBPATH is used instead, on MacOSX
53       it is called DYLD_LIBRARY_PATH) environment variable.
54
55       If you only want to check the Qwt examples without installing something,
56       you can set the LD_LIBRARY_PATH to the lib directory
57       of your local build.
58
59       If you didn't enable autobuilding of the examples in qwtconfig.pri
60       you have to build the examples this way:
61
62       cd examples
63       qmake examples.pro
64       make
65
66
67       B) Win32/MSVC Qt3/Qt4
68       =====================
69
70       Please read the qmake documentation how to convert
71       your *.pro files into your development environment.
72
73       F.e MSVC with nmake:
74       qmake qwt.pro
75       nmake
76       nmake install
77
78       If you didn't enable autobuilding of the examples in qwtconfig.pri
79       you have to build the examples this way:
80
81       cd examples
82       qmake examples.pro
83       nmake
84
85       admin/msvc-qmake.bat helps users of Visual Studio users to
86       generate makefiles or project files (.dsp for MSVC-6.0 or vcproj for
87       MSVC.NET) for Qwt.
88
89       To generate makefiles, type: 'adminvc-qmake'
90       To generate project files, type: 'adminvc-qmake vc'
91
92       When you have built a Qwt DLL you need to add the following
93       define to your compiler flags: QWT_DLL.
94
95       Windows doesn't like mixing of debug and release binaries. Most
96       of the problems with using the Qwt designer plugin are because
97       of trying to load a Qwt debug library into a designer release
98       executable.
99
100
101       C) Win32/MinGW Qt4
102       ==================
103
104       C1) Windows Shell
105
106       Start a Windows Shell, where Qt4 is initialized. ( F.e. with
107
108       qmake qwt.pro
109       make
110       make install
111
112       If you didn't enable autobuilding of the examples in qwtconfig.pri
113       you have to build the examples this way:
114
115       cd examples
116       qmake examples.pro
117       make
118
119       C2) MSYS Shell Qt >= 4.3.0
120
121       Support for the MSYS Shell has been improved in Qt 4.3.0.
122       Now building Qwt from the MSYS Shell works exactly like in UNIX or in the
123       Windows Shell - or at least it should:
124       because of a bug in Qt 4.3.0 you always have to do a 'qmake -r'.
125
126       C3) MSYS Shell Qt < 4.3.0
127
128       For Qt < 4.3.0 you have to set the MINGW_IN_SHELL variable.
129       make will run into errors with the subdirs target, that can be
130       ignored (make -i).
131
132       export MINGW_IN_SHELL=1;
133
134       qmake
135       make -i
136       make -i install
137
138       If you didn't enable autobuilding of the examples in qwtconfig.pri
139       you have to build the examples this way:
140
141       cd examples
142       qmake examples.pro
143       make -i
144
145       C1-C3)
146
147       When you have built a Qwt DLL you need to add QWT_DLL to your compiler
148       flags. If you are using qmake for your own builds this done by adding
149       the following line to your profile: 'DEFINES += QWT_DLL'.
150
151       Windows doesn't like mixing of debug and release binaries. Most
152       of the problems with using the Qwt designer plugin are because
153       of trying to load a Qwt debug library into a designer release
154       executable.
155
156       D) MacOSX
157
158       Well, the Mac is only another Unix system. So read the instructions in A).
159
160       In the recent Qt4 releases the default target of qmake is to generate
161       XCode project files instead of makefiles. So you might need to do the
162       following:
163
164       qmake -spec macx-g++ qwt.pro
165       ...
166
167       E) Qt Embedded
168       --------
169
170       I only tested Qwt with Qt Embedded in qvfb (Virtual Framebuffer Devivce)
171       Emulator on my Linux box. To build Qwt for the emulator was as simple as
172       for a regular Unix build.
173
174       F) Symbian
175       --------
176
177       I never tried this platform myself.
178
179
180       Good luck !
181
182Version 5.2.3                   Tue Nov 20 2012                  qwtinstall(3)