1
.TH "qwtinstall" 3 "22 Mar 2009" "Version 5.1.2" "Qwt User's Guide" \" -*- nroff -*-
11
Qwt uses qmake to build all its components and examples.
12
qmake is part of a Qt distribution.
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.
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
26
Qwt/Qt4 supports the MathML render engine from the Qt solutions package,
27
that is only available with a commercial Qt license.
29
You need a release of qtmmlwidget >= 2.1.
30
Copy the files qtmmlwidget.[cpp|h] to textengines/mathml.
33
==========================
39
If you have installed a shared library it's path has to be known to
40
the run-time linker of your operating system. On Linux systems read
41
'man ldconfig' ( or google for it ). Another option is to use
42
the LD_LIBRARY_PATH (on some systems LIBPATH is used instead, on MacOSX
43
it is called DYLD_LIBRARY_PATH) environment variable.
45
If you only want to check the Qwt examples without installing something,
46
you can set the LD_LIBRARY_PATH to the lib directory
49
If you didn't enable autobuilding of the examples in qwtconfig.pri
50
you have to build the examples this way:
60
Please read the qmake documentation how to convert
61
your *.pro files into your development environment.
67
If you didn't enable autobuilding of the examples in qwtconfig.pri
68
you have to build the examples this way:
74
admin/msvc-qmake.bat helps users of Visual Studio users to
75
generate makefiles or project files (.dsp for MSVC-6.0 or vcproj for
78
To generate makefiles, type: 'admin\msvc-qmake'
79
To generate project files, type: 'admin\msvc-qmake vc'
81
When you have built a Qwt DLL you need to add the following
82
define to your compiler flags: QWT_DLL.
84
Windows doesn't like mixing of debug and release binaries. Most
85
of the problems with using the Qwt designer plugin are because
86
of trying to load a Qwt debug library into a designer release
95
Start a Windows Shell, where Qt4 is initialized. ( F.e. with
96
'Programs->Qt by Trolltech ...->Qt 4.x.x Command Prompt' ).
101
If you didn't enable autobuilding of the examples in qwtconfig.pri
102
you have to build the examples this way:
109
C2) MSYS Shell Qt >= 4.3.0
111
Support for the MSYS Shell has been improved in Qt 4.3.0.
112
Now building Qwt from the MSYS Shell works exactly like in UNIX or in the
113
Windows Shell - or at least it should:
114
because of a bug in Qt 4.3.0 you always have to do a 'qmake -r'.
116
C3) MSYS Shell Qt < 4.3.0
118
For Qt < 4.3.0 you have to set the MINGW_IN_SHELL variable.
119
make will run into errors with the subdirs target, that can be
122
export MINGW_IN_SHELL=1;
128
If you didn't enable autobuilding of the examples in qwtconfig.pri
129
you have to build the examples this way:
138
When you have built a Qwt DLL you need to add QWT_DLL to your compiler
139
flags. If you are using qmake for your own builds this done by adding
140
the following line to your profile: 'DEFINES += QWT_DLL'.
142
Windows doesn't like mixing of debug and release binaries. Most
143
of the problems with using the Qwt designer plugin are because
144
of trying to load a Qwt debug library into a designer release
149
Well, the Mac is only another Unix system. So read the instructions in A).
151
In the recent Qt4 releases the default target of qmake is to generate
152
XCode project files instead of makefiles. So you might need to do the
160
I only tested Qwt with Qtopia Core in qvfb (Virtual Framebuffer Devivce)
161
Emulator on my Linux box. To build Qwt for the emulator was as simple as
162
for a regular Unix build.
167
E) Qtopia (!= Qtopia Core)
169
I once compiled the Qwt library against Qtopia 4.2.0 successfully - but
170
not more. It should be possible to build and install Qwt, but it's