<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<title>Qwt User's Guide: INSTALL</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<link href="doxygen.css" rel="stylesheet" type="text/css"/>
</head>
<body>
<!-- Generated by Doxygen 1.7.3 -->
<div id="top">
<div id="titlearea">
<table cellspacing="0" cellpadding="0">
<tbody>
<tr style="height: 56px;">
<td style="padding-left: 0.5em;">
<div id="projectname">Qwt User's Guide <span id="projectnumber">6.0.1</span></div>
</td>
</tr>
</tbody>
</table>
</div>
<div id="navrow1" class="tabs">
<ul class="tablist">
<li><a href="index.html"><span>Main Page</span></a></li>
<li class="current"><a href="pages.html"><span>Related Pages</span></a></li>
<li><a href="annotated.html"><span>Classes</span></a></li>
<li><a href="files.html"><span>Files</span></a></li>
</ul>
</div>
</div>
<div class="header">
<div class="headertitle">
<h1>INSTALL </h1> </div>
</div>
<div class="contents">
<div class="textblock"><div class="fragment"><pre class="fragment">Introduction
============
Qwt uses qmake to build all its components and examples.
qmake is part of a Qt distribution.
qmake reads project files, that contain the options and rules how to
build a certain project. A project file ends with the suffix <span class="stringliteral">"*.pro"</span>.
Files that end with the suffix <span class="stringliteral">"*.pri"</span> are included by the project
files and contain definitions, that are common <span class="keywordflow">for</span> several project files.
qwtconfig.pri and qwtbuild.pri are read by all project files of the Qwt
package. qwtconfig.pri is also read by qwt.prf, when building your
application. So the first step is to edit the *.pri files to adjust
them to your needs.
The subdirs <span class="keyword">template</span> of qmake is known to be buggy when <span class="keyword">using</span> spaces
in path names. So better don<span class="stringliteral">'t build Qwt below a path name with spaces. </span>
<span class="stringliteral">( Otherwise you might have to run qmake in all subdirs manually ).</span>
<span class="stringliteral"></span>
<span class="stringliteral">Documentation</span>
<span class="stringliteral">==========================</span>
<span class="stringliteral"></span>
<span class="stringliteral">Qwt includes a class documentation, that is available in various formats:</span>
<span class="stringliteral"></span>
<span class="stringliteral">- Html files</span>
<span class="stringliteral">- PDF document </span>
<span class="stringliteral">- Qt Compressed Help (*.qch ) for the Qt assistant or creator. </span>
<span class="stringliteral"> You can load it "Edit Preferences" -> "Documentation" -> "Add..."</span>
<span class="stringliteral">- Man pages ( UNIX only )</span>
<span class="stringliteral"></span>
<span class="stringliteral">Building Qwt</span>
<span class="stringliteral">==========================</span>
<span class="stringliteral"></span>
<span class="stringliteral">The easiest way to build Qwt is from the command line - but you insist on </span>
<span class="stringliteral">using an IDE don'</span>t forget the <span class="stringliteral">"make install"</span> step.
A) Unix
--------
qmake
make
make install
If you have installed a shared library it<span class="stringliteral">'s path has to be known to </span>
<span class="stringliteral">the run-time linker of your operating system. On Linux systems read</span>
<span class="stringliteral">"man ldconfig" ( or google for it ). Another option is to use</span>
<span class="stringliteral">the LD_LIBRARY_PATH (on some systems LIBPATH is used instead, on MacOSX</span>
<span class="stringliteral">it is called DYLD_LIBRARY_PATH) environment variable.</span>
<span class="stringliteral"></span>
<span class="stringliteral">If you only want to check the Qwt examples without installing something,</span>
<span class="stringliteral">you can set the LD_LIBRARY_PATH to the lib directory </span>
<span class="stringliteral">of your local build. </span>
<span class="stringliteral"></span>
<span class="stringliteral">If you didn'</span>t enable autobuilding of the examples in qwtconfig.pri
you have to build the examples <span class="keyword">this</span> way:
cd examples
qmake
make
B) Win32/MSVC
--------
Check that your Qt version has been built with MSVC - not with MinGW !
Please read the qmake documentation how to convert
your *.pro files into your development environment.
F.e MSVC with nmake:
qmake qwt.pro
nmake
nmake install
If you didn<span class="stringliteral">'t enable autobuilding of the examples in qwtconfig.pri</span>
<span class="stringliteral">you have to build the examples this way:</span>
<span class="stringliteral"></span>
<span class="stringliteral">cd examples</span>
<span class="stringliteral">qmake examples.pro</span>
<span class="stringliteral">nmake</span>
<span class="stringliteral"></span>
<span class="stringliteral">Windows doesn'</span>t like mixing of debug and release binaries. Most
of the problems with <span class="keyword">using</span> the Qwt designer plugin are because
of trying to load a Qwt debug library into a designer release
executable.
It<span class="stringliteral">'s not possible to load a plugin, that has been built with MinGW</span>
<span class="stringliteral">into a Qt Designer/Creator, that has been built with MSVC ( and v.v ).</span>
<span class="stringliteral">This is a common reason for problems, when working with prebuild</span>
<span class="stringliteral">binaries of the Qt Creator.</span>
<span class="stringliteral"></span>
<span class="stringliteral">C) Win32/MinGW </span>
<span class="stringliteral">--------</span>
<span class="stringliteral"></span>
<span class="stringliteral">Check that your Qt version has been built with MinGW - not with MSVC !</span>
<span class="stringliteral"></span>
<span class="stringliteral">Start a Shell, where Qt4 is initialized. ( F.e. with</span>
<span class="stringliteral">"Programs->Qt by Trolltech ...->Qt 4.x.x Command Prompt" ).</span>
<span class="stringliteral">Check if you can execute "make" or something like "mingw32-make".</span>
<span class="stringliteral"></span>
<span class="stringliteral">qmake qwt.pro</span>
<span class="stringliteral">make</span>
<span class="stringliteral">make install</span>
<span class="stringliteral"></span>
<span class="stringliteral">If you didn'</span>t enable autobuilding of the examples in qwtconfig.pri
you have to build the examples <span class="keyword">this</span> way:
cd examples
qmake examples.pro
make
Windows doesn<span class="stringliteral">'t like mixing of debug and release binaries. Most</span>
<span class="stringliteral">of the problems with using the Qwt designer plugin are because</span>
<span class="stringliteral">of trying to load a Qwt debug library into a designer release </span>
<span class="stringliteral">executable.</span>
<span class="stringliteral"></span>
<span class="stringliteral">Don'</span>t forget to tell qmake where to find qwt.prf:
qmake -<span class="keyword">set</span> QMAKEFEATURES ...
D) MacOSX
--------
Well, the Mac is only another Unix system. So read the instructions in A).
In the recent Qt4 releases the <span class="keywordflow">default</span> target of qmake is to generate
XCode project files instead of makefiles. So you might need to <span class="keywordflow">do</span> the
following:
qmake -spec macx-g++
...
D) Qt Embedded
--------
I only tested Qwt with Qt Embedded in qvfb (Virtual Framebuffer Devivce)
Emulator on my Linux box. To build Qwt <span class="keywordflow">for</span> the emulator was as simple as
<span class="keywordflow">for</span> a regular Unix build.
F) Symbian
--------
I never tried <span class="keyword">this</span> platform myself.
Using Qwt
===========
For building a Qwt application with qmake use the Qwt configuration features
file, that has been installed by <span class="stringliteral">"make install"</span>. When qmake is able to find
it ( http:<span class="comment">//doc.qt.nokia.com/4.7/qmake-advanced-usage.html#adding-new-configuration-features )</span>
you can simply add <span class="stringliteral">"CONFIG += qwt"</span> to your application project file.
If you don<span class="stringliteral">'t use qmake you have to add the include path to find the Qwt </span>
<span class="stringliteral">headers to your compiler flags and the Qwt library to your linker list.</span>
<span class="stringliteral">Don'</span>t forget to add QWT_DLL to the compiler flags, when you work with a
Qwt-DLLs on Windows.
For <span class="keyword">using</span> the designer plugin you have to configure the Qt designer/creator
where to look <span class="keywordflow">for</span> plugins. This can be done by setting the QT_PLUGIN_PATH or
<span class="keyword">using</span> a qt.conf file ( see http:<span class="comment">//doc.qt.nokia.com/4.7/deployment-plugins.html ).</span>
Beside the plugin the Qwt library itsself also needs to be known to the Designer/Creator
( see LD_LIBRARY_PATH, PATH ... above ).
Good luck !
</pre></div> </div></div>
<hr class="footer"/><address class="footer"><small>Generated by 
<a href="http://www.doxygen.org/index.html">
<img class="footer" src="doxygen.png" alt="doxygen"/></a> 1.7.3 </small></address>
</body>
</html>
