summaryrefslogtreecommitdiff
path: root/development
Unidiff
Diffstat (limited to 'development') (more/less context) (show whitespace changes)
-rw-r--r--development/macosx/README_MACOSX15
1 files changed, 8 insertions, 7 deletions
diff --git a/development/macosx/README_MACOSX b/development/macosx/README_MACOSX
index bc21548..1c7119a 100644
--- a/development/macosx/README_MACOSX
+++ b/development/macosx/README_MACOSX
@@ -1,134 +1,135 @@
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 Andreas Junghans (webmaster@lucid-cake.net) for its patches for qt-X11 (2.3.2), 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). 8QT/E (2.3.5) and qtopia (1.6.1).
9Without 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..
10 10
11Status: 11Status:
12------- 12-------
13The 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,
14which are platform specific, need some work to be compileable. 14which are platform specific, need some work to be compileable.
15 15
16What is ready: 16What is ready:
17 17
18libqpe 18libqpe
19libopie1 19libopie1
20libopie2/opiedb 20libopie2/opiedb
21pim-applications (addressbook, todolist, datebook, today) 21pim-applications (addressbook, todolist, datebook, today)
22A lot of applications and plugins which are not platform specific. 22A lot of applications and plugins which are not platform specific.
23 23
24What will follow soon: 24What will follow soon:
25 25
26libopie2 26libopie2
27 27
28 28
29How to compile Opie for MacOS-X: 29How to compile Opie for MacOS-X:
30------------------------------- 30-------------------------------
31 31
32Before compiling for MacOS-X, you need the following: 32Before compiling for MacOS-X, you need the following:
33 33
34 1. X11-Server+X11SDK (Provided by Apple) 34 1. X11-Server+X11SDK (Provided by Apple)
35 2. QT-2.3.2 for X11 (Provided by Trolltech) 35 2. QT-2.3.2 for X11 (Provided by Trolltech)
36 3. QT/E-2.3.7 (Provided by Trolltech) 36 3. QT/E-2.3.7 (Provided by Trolltech)
37 4. Patches for QT-2.3.2 for MacOSX (take the one in this directory !) 37 4. Patches for QT-2.3.2 for MacOSX (take the one in this directory !)
38 5. Patches for QT/E-2.3.7 for MacOSX (take the one, provided in $OPIEDIR/qt) 38 5. Patches for QT/E-2.3.7 for MacOSX (take the one, provided in $OPIEDIR/qt)
39 39
40The Patch for QT-2.3.2 is provided in this directory and is called "qt232-X11.patch".
41Please copy the file "darwin-g++-shared" from the directory "./config-files/qt-2.3.2" into the directory "configs"
42within the qt-2.3.2 directory !!
43
40The Patch for QT/E for Opie, including all other opie-patches is available in the 44The Patch for QT/E for Opie, including all other opie-patches is available in the
41qt-directory ($OPIEDIR/qt) and is called "qte237-all-macosx.patch". 45qt-directory ($OPIEDIR/qt) and is called "qte237-all-macosx.patch".
42To be able to compile, you have to copy the file from the directory "./config-files/qte-2.3.7" 46To be able to compile, you have to copy the file from the directory "./config-files/qte-2.3.7"
43into the directory "configs" within the base directory of qt/e. 47into the directory "configs" within the base directory of qt/e.
48Secondly, you have to copy the file "qconfig-qpe.h" from the Directory "$OPIEDIR/qt" into the "tools" directory
49within the base directory of qt/e. Then, please add the line "#define QT_NO_SOUND" to this file.
44 50
45The Patch for QT-2.3.2 is provided in this directory and is called "qt232-X11.patch". 51Please read further, how to compile the stuff.
46Please copy the file "darwin-g++-shared" from the directory "./config-files/qt-2.3.2" into the directory "configs"
47within the qt-2.3.2 directory !!
48
49If your buildsystem is working correctly, you should be able to build
50opie.
51 52
52HOWTO COMPILE: 53HOWTO COMPILE:
53------------- 54-------------
54 55
55Compile QT-2.3.2: 56Compile QT-2.3.2:
56 57
57Got to into the basic directory of qt-2.3.2 and enter 58Go to into the basic directory of qt-2.3.2 and enter
58export QTDIR=`pwd` 59export QTDIR=`pwd`
59export DYLD_LIBRARY_PATH=$QTDIR/lib 60export DYLD_LIBRARY_PATH=$QTDIR/lib
60./configure -no-xft -platform darwin-g++ 61./configure -no-xft -platform darwin-g++
61make 62make
62After compiling successful (I hope) you need qvfb: 63After compiling successful (I hope) you need qvfb:
63cd tools/qvfb 64cd tools/qvfb
64make 65make
65 66
66Compile QT/E-2.3.7: 67Compile QT/E-2.3.7:
67 68
68Got to into the basic directory of qt-2.3.2 and enter 69Got to into the basic directory of qt-2.3.2 and enter
69export QTDIR=`pwd` 70export QTDIR=`pwd`
70export QPEDIR=$QTDIR 71export QPEDIR=$QTDIR
71export DYLD_LIBRARY_PATH=$QTDIR/lib 72export DYLD_LIBRARY_PATH=$QTDIR/lib
72./configure -platform darwin-generic-g++ -qconfig qpe -qvfb -depths 4,8,16,32 73./configure -platform darwin-generic-g++ -qconfig qpe -qvfb -depths 4,8,16,32
73make 74make
74 75
75Compile OPIE: 76Compile OPIE:
76Set your environment 77Set your environment
77(You may use the script "set_vars.sh" to set your variables successfully ! 78(You may use the script "set_vars.sh" to set your variables successfully !
78BUT: You have to customize this script for YOUR needs !!) 79BUT: You have to customize this script for YOUR needs !!)
79Go into the basic directory of Opie 80Go into the basic directory of Opie
80make menuconfig" 81make menuconfig"
81set "Build Parameters"->"Target Machine"->"Mac OS X (DARWIN)" to activate the platform specific changes. 82set "Build Parameters"->"Target Machine"->"Mac OS X (DARWIN)" to activate the platform specific changes.
82save and exit the menuconfig app 83save and exit the menuconfig app
83make 84make
84 85
85You will see that a lot of applications and plugins/applets will not compile 86You will see that a lot of applications and plugins/applets will not compile
86successfully, due to the fact that they are not ported to this platform. 87successfully, due to the fact that they are not ported to this platform.
87You may disable them to be able to compile the rest. 88You may disable them to be able to compile the rest.
88 89
89Remember: A lot of configuration-settings are not tested and might fail to compile. 90Remember: A lot of configuration-settings are not tested and might fail to compile.
90If you want to avoid misconfigurations, you may want to start with 91If you want to avoid misconfigurations, you may want to start with
91the config-file in this directory. Just copy "config_macosx" to $OPIEDIR/.config 92the config-file in this directory. Just copy "config_macosx" to $OPIEDIR/.config
92to get a working configuration to start with. 93to get a working configuration to start with.
93 94
94(The missing apps/plugins will be ported on demand.) 95(The missing apps/plugins will be ported on demand.)
95 96
96 97
97SPECIAL INFORMATION FOR USERS OF PANTHER 98SPECIAL INFORMATION FOR USERS OF PANTHER
98---------------------------------------- 99----------------------------------------
99I had a lot of problems compiling qt-2.3.2 and QT/E-2.3.7 on Panther. The 100I had a lot of problems compiling qt-2.3.2 and QT/E-2.3.7 on Panther. The
100new release of the X-Server causes a lot of trouble.. 101new release of the X-Server causes a lot of trouble..
101 102
102To compile QT-2.3.2 successfully, you have to disable support of freetype fonts and you have 103To compile QT-2.3.2 successfully, you have to disable support of freetype fonts and you have
103to use the patch in this directory, otherwise your wont't be able to compile ! 104to use the patch in this directory, otherwise your wont't be able to compile !
104Use the param "-no-xft" for the configure script to disable this function ! 105Use the param "-no-xft" for the configure script to disable this function !
105 106
106Information for Developers: 107Information for Developers:
107--------------------------- 108---------------------------
108 109
1091. Platform specific code should be surrounded by 1101. Platform specific code should be surrounded by
110#ifdef Q_OS_MACX 111#ifdef Q_OS_MACX
111MACOS-X CODE 112MACOS-X CODE
112#else 113#else
113OTHER-CODE 114OTHER-CODE
114#endif 115#endif
115 116
1162. The Plugin-Handling by MacOS-X is different than it is by Linux. 1172. The Plugin-Handling by MacOS-X is different than it is by Linux.
117On linux-systems, shared libraries are not different to dynamic loaded libraries 118On linux-systems, shared libraries are not different to dynamic loaded libraries
118(aka plugins). They just are different whether they are loaded automatically 119(aka plugins). They just are different whether they are loaded automatically
119at startup or manually by any application. 120at startup or manually by any application.
120On MacOS-X, the plugins are loaded by a special mechanism and must be in a special 121On MacOS-X, the plugins are loaded by a special mechanism and must be in a special
121binary format. Therefore you have to add the term "plugin" to the CONFIG-clause, as 122binary format. Therefore you have to add the term "plugin" to the CONFIG-clause, as
122for instance: 123for instance:
123 124
124TEMPLATE=lib 125TEMPLATE=lib
125CONFIG += qt plugin release 126CONFIG += qt plugin release
126 127
127If you don't add "plugin" you will get a shared library which is not loadable 128If you don't add "plugin" you will get a shared library which is not loadable
128(Error-Code: NSObjectFileImageInappropriateFile (2))! 129(Error-Code: NSObjectFileImageInappropriateFile (2))!
129 130
130 131
131 132
132For problems, help and flames, feel free to contact me at 133For problems, help and flames, feel free to contact me at
133 134
134eilers.stefan@epost.de \ No newline at end of file 135eilers.stefan@epost.de \ No newline at end of file