summaryrefslogtreecommitdiff
authoreilers <eilers>2003-11-04 13:22:08 (UTC)
committer eilers <eilers>2003-11-04 13:22:08 (UTC)
commitd2c52ff34d0ef37d055f74bb9fd957c6ffc583a9 (patch) (unidiff)
treecacd372f016edb110cfbbb9124f7c463c1db36a5
parent9b992a9790f072b76052d42f1182b1d116994061 (diff)
downloadopie-d2c52ff34d0ef37d055f74bb9fd957c6ffc583a9.zip
opie-d2c52ff34d0ef37d055f74bb9fd957c6ffc583a9.tar.gz
opie-d2c52ff34d0ef37d055f74bb9fd957c6ffc583a9.tar.bz2
Add some important informations, where to find information, how to build
QT for MacOS-X
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--development/macosx/README_MACOSX9
1 files changed, 5 insertions, 4 deletions
diff --git a/development/macosx/README_MACOSX b/development/macosx/README_MACOSX
index e2ed15f..e58aa8a 100644
--- a/development/macosx/README_MACOSX
+++ b/development/macosx/README_MACOSX
@@ -1,91 +1,92 @@
1Information about porting Opie to MacOS-X (eilers) 1Information about porting Opie to MacOS-X (eilers)
2================================================== 2==================================================
3 3
4Credits: 4Credits:
5-------- 5--------
6 6
7Special thanks to xxxx for its patches for qt-X11 (2.3.2), QT/E (2.3.5) and qtopia (1.6.1). 7Special thanks to Andreas Junghans (webmaster@lucid-cake.net) for its patches for qt-X11 (2.3.2),
8QT/E (2.3.5) and qtopia (1.6.1).
8Without them, I wouldn't be able to provide the port for OPIE to MacOS-X that fast.. 9Without them, I wouldn't be able to provide the port for OPIE to MacOS-X that fast..
9 10
10Status: 11Status:
11------- 12-------
12The basic system works quite well. But a lot of applications and plugins, 13The basic system works quite well. But a lot of applications and plugins,
13which are platform specific, need some work to be compileable. 14which are platform specific, need some work to be compileable.
14 15
15What is ready: 16What is ready:
16 17
17libqpe 18libqpe
18libopie1 19libopie1
19pim-applications (addressbook, todolist, datebook, today) 20pim-applications (addressbook, todolist, datebook, today)
20A lot of applications and plugins which are not platform specific. 21A lot of applications and plugins which are not platform specific.
21 22
22What will follow soon: 23What will follow soon:
23 24
24libopie2 25libopie2
25 26
26Remember: A lot of configuration-settings are not tested (as for instance 27Remember: A lot of configuration-settings are not tested (as for instance
27the quicklauncher) and might fail to compile. 28the quicklauncher) and might fail to compile.
28If you want to avoid misconfigurations, you may want to start with 29If you want to avoid misconfigurations, you may want to start with
29the config-file in this directory. Just copy "config_macosx" to $OPIEDIR/.config 30the config-file in this directory. Just copy "config_macosx" to $OPIEDIR/.config
30to get a working configuration to start with. 31to get a working configuration to start with.
31 32
32(The missing apps/plugins will be ported on demand.) 33(The missing apps/plugins will be ported on demand.)
33 34
34How to compile Opie for MacOS-X: 35How to compile Opie for MacOS-X:
35------------------------------- 36-------------------------------
36 37
37Before compiling for MacOS-X, you need the following: 38Before compiling for MacOS-X, you need the following:
38 39
391. X11-Server (Provided by Apple) 401. X11-Server (Provided by Apple)
402. QT-2.3.2 for X11 412. QT-2.3.2 for X11
413. QT/E-2.3.7 423. QT/E-2.3.7
424. Patches for QT-2.3.2 for MacOSX 434. Patches for QT-2.3.2 for MacOSX
435. Patches for QT/E-2.3.7 for MacOSX 445. Patches for QT/E-2.3.7 for MacOSX
44 45
45Please follow the instructions by xxxx how to create a buildsystem 46Please follow the instructions by http://www.lucid-cake.net/osx_qpe/index_de.html
46for your Mac. 47how to create a buildsystem for your Mac.
47What is different to the previous desciption: 48What is different to the previous desciption:
48You don't need Qtopia ! 49You don't need Qtopia !
49It is recommended to use QT/E in version 2.3.7 instead of 2.3.5 as described. 50It is recommended to use QT/E in version 2.3.7 instead of 2.3.5 as described.
50The Patch for QT/E for Opie, including all other opie-patches is available in the 51The Patch for QT/E for Opie, including all other opie-patches is available in the
51qt-directory ($OPIEDIR/qt) and is called "qte237-all-macosx.patch" 52qt-directory ($OPIEDIR/qt) and is called "qte237-all-macosx.patch".
52 53
53If your buildsystem is working correctly, you should be able to build 54If your buildsystem is working correctly, you should be able to build
54opie. You have to enter "make menuconfig" and set 55opie. You have to enter "make menuconfig" and set
55"Build Parameters"->"Target Machine"->"Mac OS X (DARWIN)" 56"Build Parameters"->"Target Machine"->"Mac OS X (DARWIN)"
56activate the platform specific changes. 57activate the platform specific changes.
57 58
58You will see that a lot of applications and plugins/applets will not compile 59You will see that a lot of applications and plugins/applets will not compile
59successfully, due to the fact that they are not ported to this platform. 60successfully, due to the fact that they are not ported to this platform.
60You may disable them to be able to compile the rest. 61You may disable them to be able to compile the rest.
61 62
62 63
63Information for Developers: 64Information for Developers:
64--------------------------- 65---------------------------
65 66
661. Platform specific code should be surrounded by 671. Platform specific code should be surrounded by
67#ifdef Q_OS_MACX 68#ifdef Q_OS_MACX
68MACOS-X CODE 69MACOS-X CODE
69#else 70#else
70OTHER-CODE 71OTHER-CODE
71#endif 72#endif
72 73
732. The Plugin-Handling by MacOS-X is different than it is by Linux. 742. The Plugin-Handling by MacOS-X is different than it is by Linux.
74On linux-systems, shared libraries are not different to dynamic loaded libraries 75On linux-systems, shared libraries are not different to dynamic loaded libraries
75(aka plugins). They just are different whether they are loaded automatically 76(aka plugins). They just are different whether they are loaded automatically
76at startup or manually by any application. 77at startup or manually by any application.
77On MacOS-X, the plugins are loaded by a special mechanism and must be in a special 78On MacOS-X, the plugins are loaded by a special mechanism and must be in a special
78binary format. Therefore you have to add the term "plugin" to the CONFIG-clause, as 79binary format. Therefore you have to add the term "plugin" to the CONFIG-clause, as
79for instance: 80for instance:
80 81
81TEMPLATE=lib 82TEMPLATE=lib
82CONFIG += qt plugin release 83CONFIG += qt plugin release
83 84
84If you don't add "plugin" you will get a shared library which is not loadable 85If you don't add "plugin" you will get a shared library which is not loadable
85(Error-Code: NSObjectFileImageInappropriateFile (2))! 86(Error-Code: NSObjectFileImageInappropriateFile (2))!
86 87
87 88
88 89
89For problems, help and flames, feel free to contact me at 90For problems, help and flames, feel free to contact me at
90 91
91eilers.stefan@epost.de \ No newline at end of file 92eilers.stefan@epost.de \ No newline at end of file