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_MACOSX5
1 files changed, 4 insertions, 1 deletions
diff --git a/development/macosx/README_MACOSX b/development/macosx/README_MACOSX
index 864f486..877e2f8 100644
--- a/development/macosx/README_MACOSX
+++ b/development/macosx/README_MACOSX
@@ -1,90 +1,93 @@
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".
42The Patch for QT-2.3.2 is provided in this directory.. 42
43The 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
45"darwin-g++-shared" into the directory "configs" within the qt-2.3.2 directory !!
43 46
44If your buildsystem is working correctly, you should be able to build 47If your buildsystem is working correctly, you should be able to build
45opie. 48opie.
46 49
47HOWTO COMPILE: 50HOWTO COMPILE:
48------------- 51-------------
49 52
50Compile QT-2.3.2: 53Compile QT-2.3.2:
51 54
52Got to into the basic directory of qt-2.3.2 and enter 55Got to into the basic directory of qt-2.3.2 and enter
53export QTDIR=`pwd` 56export QTDIR=`pwd`
54export DYLD_LIBRARY_PATH=$QTDIR/lib 57export DYLD_LIBRARY_PATH=$QTDIR/lib
55./configure -no-xft -platform darwin-g++ 58./configure -no-xft -platform darwin-g++
56make 59make
57After compiling successful (I hope) you need qvfb: 60After compiling successful (I hope) you need qvfb:
58cd tools/qvfb 61cd tools/qvfb
59make 62make
60 63
61Compile QT/E-2.3.7: 64Compile QT/E-2.3.7:
62 65
63Got to into the basic directory of qt-2.3.2 and enter 66Got to into the basic directory of qt-2.3.2 and enter
64export QTDIR=`pwd` 67export QTDIR=`pwd`
65export QPEDIR=$QTDIR 68export QPEDIR=$QTDIR
66export DYLD_LIBRARY_PATH=$QTDIR/lib 69export DYLD_LIBRARY_PATH=$QTDIR/lib
67./configure -platform darwin-generic-g++ -qconfig qpe -qvfb -depths 4,8,16,32 70./configure -platform darwin-generic-g++ -qconfig qpe -qvfb -depths 4,8,16,32
68make 71make
69 72
70Compile OPIE: 73Compile OPIE:
71Set your environment 74Set your environment
72(You may use the script "set_vars.sh" to set your variables successfully ! 75(You may use the script "set_vars.sh" to set your variables successfully !
73BUT: You have to customize this script for YOUR needs !!) 76BUT: You have to customize this script for YOUR needs !!)
74Go into the basic directory of Opie 77Go into the basic directory of Opie
75make menuconfig" 78make menuconfig"
76set "Build Parameters"->"Target Machine"->"Mac OS X (DARWIN)" to activate the platform specific changes. 79set "Build Parameters"->"Target Machine"->"Mac OS X (DARWIN)" to activate the platform specific changes.
77save and exit the menuconfig app 80save and exit the menuconfig app
78make 81make
79 82
80You will see that a lot of applications and plugins/applets will not compile 83You will see that a lot of applications and plugins/applets will not compile
81successfully, due to the fact that they are not ported to this platform. 84successfully, due to the fact that they are not ported to this platform.
82You may disable them to be able to compile the rest. 85You may disable them to be able to compile the rest.
83 86
84Remember: A lot of configuration-settings are not tested and might fail to compile. 87Remember: A lot of configuration-settings are not tested and might fail to compile.
85If you want to avoid misconfigurations, you may want to start with 88If you want to avoid misconfigurations, you may want to start with
86the config-file in this directory. Just copy "config_macosx" to $OPIEDIR/.config 89the config-file in this directory. Just copy "config_macosx" to $OPIEDIR/.config
87to get a working configuration to start with. 90to get a working configuration to start with.
88 91
89(The missing apps/plugins will be ported on demand.) 92(The missing apps/plugins will be ported on demand.)
90 93