1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2
<html><head><meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1">
3
<title>Qwt User's Guide: INSTALL</title>
4
<link href="doxygen.css" rel="stylesheet" type="text/css">
5
<link href="tabs.css" rel="stylesheet" type="text/css">
7
<!-- Generated by Doxygen 1.5.0 -->
10
<li><a href="index.html"><span>Main Page</span></a></li>
11
<li><a href="classes.html"><span>Classes</span></a></li>
12
<li><a href="files.html"><span>Files</span></a></li>
13
<li><a href="pages.html"><span>Related Pages</span></a></li>
15
<h1><a class="anchor" name="qwtinstall">INSTALL</a></h1><div class="fragment"><pre class="fragment">Introduction
18
Qwt uses qmake to build all its components and examples.
19
qmake is part of a Qt distribution.
21
qmake reads project files, that contain the options and rules how to
22
build a certain project. A project file ends with the suffix <span class="stringliteral">"*.pro"</span>.
23
Files that end with the suffix <span class="stringliteral">"*.pri"</span> are included by the project
24
files and contain definitions, that are common <span class="keywordflow">for</span> several project files.
26
qwtconfig.pri is read by all project files of the Qwt package.
27
So the first step is to edit qwtconfig.pri to adjust it to your
33
Qwt/Qt4 supports the MathML render engine from the Qt solutions package,
34
that is only available with a commercial Qt license.
36
You need a release of qtmmlwidget >= 2.1.
37
Copy the files qtmmlwidget.[cpp|h] to textengines/mathml.
40
==========================
46
If you have installed a shared library it's path has to be known to
47
the run-time linker of your operating system. On Linux systems read
48
<span class="stringliteral">"man ldconfig"</span> ( or google <span class="keywordflow">for</span> it ). Another option is to use
49
the LD_LIBRARY_PATH (on some systems LIBPATH is used instead, on MacOSX
50
it is called DYLD_LIBRARY_PATH) environment variable.
52
If you only want to check the Qwt examples without installing something,
53
you can set the LD_LIBRARY_PATH to the lib directory
56
If you didn't enable autobuilding of the examples in qwtconfig.pri
57
you have to build the examples <span class="keyword">this</span> way:
67
Please read the qmake documentation how to convert
68
your *.pro files into your development environment.
74
If you didn't enable autobuilding of the examples in qwtconfig.pri
75
you have to build the examples <span class="keyword">this</span> way:
81
admin/msvc-qmake.bat helps users of Visual Studio users to
82
generate makefiles or project files (.dsp <span class="keywordflow">for</span> MSVC-6.0 or vcproj <span class="keywordflow">for</span>
83
MSVC.NET) <span class="keywordflow">for</span> Qwt.
85
To generate makefiles, type: <span class="stringliteral">"admin\msvc-qmake"</span>
86
To generate project files, type: <span class="stringliteral">"admin\msvc-qmake vc"</span>
88
When you have built a Qwt DLL you need to add the following
89
define to your compiler flags: QWT_DLL.
91
Windows doesn't like mixing of debug and release binaries. Most
92
of the problems with <span class="keyword">using</span> the Qwt designer plugin are because
93
of trying to load a Qwt debug library into a designer release
102
Start a Windows Shell, where Qt4 is initialized. ( F.e. with
103
<span class="stringliteral">"Programs->Qt by Trolltech ...->Qt 4.x.x Command Prompt"</span> ).
108
If you didn't enable autobuilding of the examples in qwtconfig.pri
109
you have to build the examples <span class="keyword">this</span> way:
116
C2) MSYS Shell Qt >= 4.3.0
118
Support <span class="keywordflow">for</span> the MSYS Shell has been improved in Qt 4.3.0.
119
Now building Qwt from the MSYS Shell works exactly like in UNIX or in the
120
Windows Shell - or at least it should:
121
because of a bug in Qt 4.3.0 you always have to <span class="keywordflow">do</span> a <span class="stringliteral">"qmake -r"</span>.
123
C3) MSYS Shell Qt < 4.3.0
125
For Qt < 4.3.0 you have to set the MINGW_IN_SHELL variable.
126
make will run into errors with the subdirs target, that can be
129
export MINGW_IN_SHELL=1;
135
If you didn't enable autobuilding of the examples in qwtconfig.pri
136
you have to build the examples <span class="keyword">this</span> way:
145
When you have built a Qwt DLL you need to add QWT_DLL to your compiler
146
flags. If you are <span class="keyword">using</span> qmake <span class="keywordflow">for</span> your own builds <span class="keyword">this</span> done by adding
147
the following line to your profile: <span class="stringliteral">"DEFINES += QWT_DLL"</span>.
149
Windows doesn't like mixing of debug and release binaries. Most
150
of the problems with <span class="keyword">using</span> the Qwt designer plugin are because
151
of trying to load a Qwt debug library into a designer release
156
Well, the Mac is only another Unix system. So read the instructions in A).
158
In the recent Qt4 releases the <span class="keywordflow">default</span> target of qmake is to generate
159
XCode project files instead of makefiles. So you might need to <span class="keywordflow">do</span> the
167
I only tested Qwt with Qtopia Core in qvfb (Virtual Framebuffer Devivce)
168
Emulator on my Linux box. To build Qwt <span class="keywordflow">for</span> the emulator was as simple as
169
<span class="keywordflow">for</span> a regular Unix build.
174
E) Qtopia (!= Qtopia Core)
176
I once compiled the Qwt library against Qtopia 4.2.0 successfully - but
177
not more. It should be possible to build and install Qwt, but it's
181
</pre></div> <hr size="1"><address style="align: right;"><small>Generated on Sun Mar 22 16:54:10 2009 for Qwt User's Guide by
182
<a href="http://www.doxygen.org/index.html">
183
<img src="doxygen.png" alt="doxygen" align="middle" border="0"></a> 1.5.0 </small></address>
added
removed
qwt-5.1.2/doc/html/qwtinstall.html
