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
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
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
77       If you didn't enable autobuilding of the examples in qwtconfig.pri
78       you have to build the examples this way:
79
80       cd examples
81       qmake examples.pro
82       nmake
83
84       admin/msvc-qmake.bat helps users of Visual Studio users to
85       generate makefiles or project files (.dsp for MSVC-6.0 or vcproj for
86       MSVC.NET) for Qwt.
87
88       To generate makefiles, type: 'adminvc-qmake'
89       To generate project files, type: 'adminvc-qmake vc'
90
91       When you have built a Qwt DLL you need to add the following
92       define to your compiler flags: QWT_DLL.
93
94       Windows doesn't like mixing of debug and release binaries. Most
95       of the problems with using the Qwt designer plugin are because
96       of trying to load a Qwt debug library into a designer release
97       executable.
98
99
100       C) Win32/MinGW Qt4
101       ==================
102
103       C1) Windows Shell
104
105       Start a Windows Shell, where Qt4 is initialized. ( F.e. with
106
107       qmake qwt.pro
108       make
109
110       If you didn't enable autobuilding of the examples in qwtconfig.pri
111       you have to build the examples this way:
112
113       cd examples
114       qmake examples.pro
115       make
116       make install
117
118       C2) MSYS Shell Qt >= 4.3.0
119
120       Support for the MSYS Shell has been improved in Qt 4.3.0.
121       Now building Qwt from the MSYS Shell works exactly like in UNIX or in the
122       Windows Shell - or at least it should:
123       because of a bug in Qt 4.3.0 you always have to do a 'qmake -r'.
124
125       C3) MSYS Shell Qt < 4.3.0
126
127       For Qt < 4.3.0 you have to set the MINGW_IN_SHELL variable.
128       make will run into errors with the subdirs target, that can be
129       ignored (make -i).
130
131       export MINGW_IN_SHELL=1;
132
133       qmake
134       make -i
135       make -i install
136
137       If you didn't enable autobuilding of the examples in qwtconfig.pri
138       you have to build the examples this way:
139
140       cd examples
141       qmake examples.pro
142       make -i
143       make -i install
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++
165
166       D) Qtopia Core
167
168       I only tested Qwt with Qtopia Core in qvfb (Virtual Framebuffer Devivce)
169       Emulator on my Linux box. To build Qwt for the emulator was as simple as
170       for a regular Unix build.
171
172       qmake
173       make
174
175       E) Qtopia (!= Qtopia Core)
176
177       I once compiled the Qwt library against Qtopia 4.2.0 successfully - but
178       not more. It should be possible to build and install Qwt, but it's
179       not done yet.
180
181       Good luck !
182
183Version 5.2.1                     11 Apr 2010                    qwtinstall(3)