INSTALLATION INSTRUCTIONS
These instructions refer to the package you are installing as
some-package.tar.gz or some-package.zip. The .zip file is intended for use
on Windows.
The directory you choose for the installation will be referred to as
your-install-dir.
Note to Qt Visual Studio Integration users: In the instructions below,
instead of building from command line with nmake, you can use the menu
command 'Qt->Open Solution from .pro file' on the .pro files in the
example and plugin directories, and then build from within Visual
Studio.
Unpacking and installation
--------------------------
1. Unpacking the archive (if you have not done so already).
On Unix and Mac OS X (in a terminal window):
cd your-install-dir
gunzip some-package.tar.gz
tar xvf some-package.tar
This creates the subdirectory some-package containing the files.
On Windows:
Unpack the .zip archive by right-clicking it in explorer and
choosing "Extract All...". If your version of Windows does not
have zip support, you can use the infozip tools available
from www.info-zip.org.
If you are using the infozip tools (in a command prompt window):
cd your-install-dir
unzip some-package.zip
2. Configuring the package.
The configure script is called "configure" on unix/mac and
"configure.bat" on Windows. It should be run from a command line
after cd'ing to the package directory.
You can choose whether you want to use the component by including
its source code directly into your project, or build the component
as a dynamic shared library (DLL) that is loaded into the
application at run-time. The latter may be preferable for
technical or licensing (LGPL) reasons. If you want to build a DLL,
run the configure script with the argument "-library". Also see
the note about usage below.
(Components that are Qt plugins, e.g. styles and image formats,
are by default built as a plugin DLL.)
The configure script will prompt you in some cases for further
information. Answer these questions and carefully read the license text
before accepting the license conditions. The package cannot be used if
you do not accept the license conditions.
3. Building the component and examples (when required).
If a DLL is to be built, or if you would like to build the
examples, next give the commands
qmake
make [or nmake if your are using Microsoft Visual C++]
The example program(s) can be found in the directory called
"examples" or "example".
Components that are Qt plugins, e.g. styles and image formats, are
ready to be used as soon as they are built, so the rest of this
installation instruction can be skipped.
4. Building the Qt Designer plugin (optional).
Some of the widget components are provided with plugins for Qt
Designer. To build and install the plugin, cd into the
some-package/plugin directory and give the commands
qmake
make [or nmake if your are using Microsoft Visual C++]
Restart Qt Designer to make it load the new widget plugin.
Note: If you are using the built-in Qt Designer from the Qt Visual
Studio Integration, you will need to manually copy the plugin DLL
file, i.e. copy
%QTDIR%\plugins\designer\some-component.dll
to the Qt Visual Studio Integration plugin path, typically:
C:\Program Files\Trolltech\Qt VS Integration\plugins
Note: If you for some reason are using a Qt Designer that is built
in debug mode, you will need to build the plugin in debug mode
also. Edit the file plugin.pro in the plugin directory, changing
'release' to 'debug' in the CONFIG line, before running qmake.
Solutions components are intended to be used directly from the package
directory during development, so there is no 'make install' procedure.
Using a component in your project
---------------------------------
To use this component in your project, add the following line to the
project's .pro file (or do the equivalent in your IDE):
include(your-install-dir/some-package/src/some-package.pri)
This adds the package's sources and headers to the SOURCES and HEADERS
project variables respectively (or, if the component has been
configured as a DLL, it adds that library to the LIBS variable), and
updates INCLUDEPATH to contain the package's src
directory. Additionally, the .pri file may include some dependencies
needed by the package.
To include a header file from the package in your sources, you can now
simply use:
#include <SomeClass>
or alternatively, in pre-Qt 4 style:
#include <some-class.h>
Refer to the documentation to see the classes and headers this
components provides.
Install documentation (optional)
--------------------------------
The HTML documentation for the package's classes is located in the
your-install-dir/some-package/doc/html/index.html. You can open this
file and read the documentation with any web browser.
To install the documentation into Qt Assistant (for Qt version 4.4 and
later):
1. In Assistant, open the Edit->Preferences dialog and choose the
Documentation tab. Click the Add... button and select the file
your-install-dir/some-package/doc/html/some-package.qch
For Qt versions prior to 4.4, do instead the following:
1. The directory your-install-dir/some-package/doc/html contains a
file called some-package.dcf. Execute the following commands in a
shell, command prompt or terminal window:
cd your-install-dir/some-package/doc/html/
assistant -addContentFile some-package.dcf
The next time you start Qt Assistant, you can access the package's
documentation.
Removing the documentation from assistant
-----------------------------------------
If you have installed the documentation into Qt Assistant, and want to uninstall it, do as follows, for Qt version 4.4 and later:
1. In Assistant, open the Edit->Preferences dialog and choose the
Documentation tab. In the list of Registered Documentation, select
the item com.nokia.qtsolutions.some-package_version, and click
the Remove button.
For Qt versions prior to 4.4, do instead the following:
1. The directory your-install-dir/some-package/doc/html contains a
file called some-package.dcf. Execute the following commands in a
shell, command prompt or terminal window:
cd your-install-dir/some-package/doc/html/
assistant -removeContentFile some-package.dcf
Using the component as a DLL
----------------------------
1. Normal components
The shared library (DLL) is built and placed in the
some-package/lib directory. It is intended to be used directly
from there during development. When appropriate, both debug and
release versions are built, since the run-time linker will in some
cases refuse to load a debug-built DLL into a release-built
application or vice versa.
The following steps are taken by default to help the dynamic
linker to locate the DLL at run-time (during development):
Unix: The some-package.pri file will add linker instructions to
add the some-package/lib directory to the rpath of the
executable. (When distributing, or if your system does not support
rpath, you can copy the shared library to another place that is
searched by the dynamic linker, e.g. the "lib" directory of your
Qt installation.)
Mac: The full path to the library is hardcoded into the library
itself, from where it is copied into the executable at link time,
and ready by the dynamic linker at run-time. (When distributing,
you will want to edit these hardcoded paths in the same way as for
the Qt DLLs. Refer to the document "Deploying an Application on
Mac OS X" in the Qt Reference Documentation.)
Windows: the .dll file(s) are copied into the "bin" directory of
your Qt installation. The Qt installation will already have set up
that directory to be searched by the dynamic linke
史上最全QT绘图工具集合
需积分: 5 87 浏览量
2023-04-14
10:41:49
上传
评论
收藏 42.32MB ZIP 举报
史上最全QT绘图工具集合 （796个子文件） 
MyPaint.pro.user.3.2-pre1 18KB QtDrawMaps.pro.user.69aec48.22 60KB drawcli.pro.user.466b8dd 18KB QtDrawMaps.pro.user.69aec48 60KB MiniDraw.pro.user.6bef07c 24KB configure.bat 3KB c++ 148.16MB QtDrawMaps.pro.user.cf6c23f 41KB configure 689B qrc_res.cpp 925KB qrc_app.cpp 217KB qtpropertymanager.cpp 211KB qtcanvas.cpp 161KB qtcanvas.cpp 161KB moc_qtpropertymanager.cpp 133KB qtvariantproperty.cpp 101KB qteditorfactory.cpp 83KB qrc_qss.cpp 73KB qtpropertybrowser.cpp 63KB qrc_res.cpp 61KB moc_qteditorfactory.cpp 60KB drawobj.cpp 41KB drawobj.cpp 41KB qttreepropertybrowser.cpp 35KB mainwindow.cpp 32KB bqgraphicsitem.cpp 29KB qrc_qtpropertybrowser.cpp 25KB mainwindow.cpp 21KB moc_qtvariantproperty.cpp 20KB tool.cpp 20KB qtbuttonpropertybrowser.cpp 20KB mainwindow.cpp 18KB drawtool.cpp 17KB qtgroupboxpropertybrowser.cpp 17KB customproperty.cpp 17KB drawtool.cpp 16KB moc_qtpropertybrowser.cpp 16KB qtdrawscene.cpp 16KB mypaint.cpp 16KB qtpropertybrowserutils.cpp 15KB moc_customproperty.cpp 15KB mainwindow.cpp 15KB moc_drawobj.cpp 15KB objectcontroller.cpp 14KB objectcontroller.cpp 14KB mainwindow.cpp 14KB objectcontroller.cpp 13KB drawobj.cpp 12KB mainwindow.cpp 12KB moc_mainwindow.cpp 12KB moc_mainwindow.cpp 12KB drawtool.cpp 12KB qtsingleapplication.cpp 12KB drawscene.cpp 11KB commands.cpp 11KB main.cpp 11KB PaintView.cpp 11KB commands.cpp 10KB moc_qttreepropertybrowser.cpp 10KB moc_drawscene.cpp 10KB main.cpp 10KB main.cpp 9KB drawview.cpp 9KB rulebar.cpp 9KB bpointitem.cpp 8KB moc_mainwindow.cpp 8KB moc_qtpropertybrowserutils_p.cpp 8KB main.cpp 8KB moc_mainwindow.cpp 8KB view.cpp 8KB scene.cpp 7KB mainscene.cpp 7KB qtlocalpeer.cpp 7KB qtlockedfile_win.cpp 6KB moc_qwgraphicsview.cpp 6KB qtlockedfile.cpp 6KB moc_qtbuttonpropertybrowser.cpp 6KB main.cpp 6KB mainwindow.cpp 6KB moc_qwgraphicsview.cpp 5KB qtsinglecoreapplication.cpp 5KB MainPaintScene.cpp 5KB mainwindow.cpp 5KB MainForm.cpp 5KB moc_rulebar.cpp 4KB moc_drawview.cpp 4KB moc_qtgroupboxpropertybrowser.cpp 4KB GraphicsArrowItem.cpp 4KB GraphicsItem.cpp 4KB moc_objectcontroller.cpp 4KB qtlockedfile_unix.cpp 3KB mainwindow.cpp 3KB GraphicsPathItem.cpp 3KB GraphicsPixmapItem.cpp 3KB GraphicsRectItem.cpp 3KB main.cpp 2KB main.cpp 2KB sizehandle.cpp 2KB main.cpp 2KB sizehandle.cpp 2KB共 796 条
- 1
- 2
- 3
- 4
- 5
- 6
- 8
资源评论
