-
Notifications
You must be signed in to change notification settings - Fork 6
/
PORTING
56 lines (43 loc) · 2.33 KB
/
PORTING
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
PORTING Qt TO OTHER PLATFORMS
Read this file if you want to port Qt to a new platform or C++
compiler. If you come across any problems, feel free to send mail to
qt-bugs@trolltech.com.
REQUIREMENTS
The new platform needs Xlib for X11R5 or newer. Motif is not required.
If it is not a Unix system (for instance VMS) things may get complicated.
Porting to other Unixes is generally straight-forward.
Qt requires that your C++ compiler supports multiple inheritance and
templates. The compiler must recognize the .cpp extension. Exception
handling and RTTI (Run-Time Type Information) are not required.
Expect problems with old CFront-based compilers.
PATCHES
Please send us the patches you had to make so we can add them to the
code base; then we can support the new platform in an orderly manner.
(We want Qt to run on as many platforms as possible, but _not_ if that
involves incompatible patches for the same platform floating around the
net.)
Further, we would like to have copies of all Qt-related files on
ftp.trolltech.com.
PORTING INSTRUCTIONS
In the configs/ directory you will find several build configuration
files for all platforms supported by Qt. Start off with one the
existing files in configs/, rename it, and change it manually to
fit your system. For example you may copy
configs/solaris-cc-shared-debug
to
configs/solaris-cxx-shared-debug
If possible try to modify all four configuration files.
Modify qt/src/tools/qglobal.h as required: you need to ensure that
_OS_whatever_ is defined. We've done it for many platforms in the
past, those should be okay. If you are using a compiler we don't
detect it's probably a good idea to add a _CC_whatever_ too (even
though you don't need it at once). There are also some size-dependent
types (Q_UINT32 and so on), make sure they're right for your system.
Some compilers emit bad warnings when they compile Qt. If yours does,
and the code in Qt is sane, please use a #pragma or two to shut your
compiler up. (This is a good reason for wanting the _CC_whatever_
define above.) Alternatively try using compiler option flags.
Make a unified diff (diff -u) and send the patch and the configuration
files to qt-bugs@trolltech.com.
For most Unix varieties, that's all. Some may need some include file
tweaks. Good luck, and again, feel free to send mail to qt-bugs@trolltech.com.