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