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