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