author | eilers <eilers> | 2003-11-04 13:22:08 (UTC) |
---|---|---|
committer | eilers <eilers> | 2003-11-04 13:22:08 (UTC) |
commit | d2c52ff34d0ef37d055f74bb9fd957c6ffc583a9 (patch) (unidiff) | |
tree | cacd372f016edb110cfbbb9124f7c463c1db36a5 | |
parent | 9b992a9790f072b76052d42f1182b1d116994061 (diff) | |
download | opie-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
-rw-r--r-- | development/macosx/README_MACOSX | 9 |
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 @@ | |||
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 xxxx for its patches for qt-X11 (2.3.2), QT/E (2.3.5) and qtopia (1.6.1). | 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 | 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.. |
9 | 10 | ||
10 | Status: | 11 | Status: |
11 | ------- | 12 | ------- |
12 | 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, |
13 | which are platform specific, need some work to be compileable. | 14 | which are platform specific, need some work to be compileable. |
14 | 15 | ||
15 | What is ready: | 16 | What is ready: |
16 | 17 | ||
17 | libqpe | 18 | libqpe |
18 | libopie1 | 19 | libopie1 |
19 | pim-applications (addressbook, todolist, datebook, today) | 20 | pim-applications (addressbook, todolist, datebook, today) |
20 | A lot of applications and plugins which are not platform specific. | 21 | A lot of applications and plugins which are not platform specific. |
21 | 22 | ||
22 | What will follow soon: | 23 | What will follow soon: |
23 | 24 | ||
24 | libopie2 | 25 | libopie2 |
25 | 26 | ||
26 | Remember: A lot of configuration-settings are not tested (as for instance | 27 | Remember: A lot of configuration-settings are not tested (as for instance |
27 | the quicklauncher) and might fail to compile. | 28 | the quicklauncher) and might fail to compile. |
28 | If you want to avoid misconfigurations, you may want to start with | 29 | If you want to avoid misconfigurations, you may want to start with |
29 | the config-file in this directory. Just copy "config_macosx" to $OPIEDIR/.config | 30 | the config-file in this directory. Just copy "config_macosx" to $OPIEDIR/.config |
30 | to get a working configuration to start with. | 31 | to 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 | ||
34 | How to compile Opie for MacOS-X: | 35 | How to compile Opie for MacOS-X: |
35 | ------------------------------- | 36 | ------------------------------- |
36 | 37 | ||
37 | Before compiling for MacOS-X, you need the following: | 38 | Before compiling for MacOS-X, you need the following: |
38 | 39 | ||
39 | 1. X11-Server (Provided by Apple) | 40 | 1. X11-Server (Provided by Apple) |
40 | 2. QT-2.3.2 for X11 | 41 | 2. QT-2.3.2 for X11 |
41 | 3. QT/E-2.3.7 | 42 | 3. QT/E-2.3.7 |
42 | 4. Patches for QT-2.3.2 for MacOSX | 43 | 4. Patches for QT-2.3.2 for MacOSX |
43 | 5. Patches for QT/E-2.3.7 for MacOSX | 44 | 5. Patches for QT/E-2.3.7 for MacOSX |
44 | 45 | ||
45 | Please follow the instructions by xxxx how to create a buildsystem | 46 | Please follow the instructions by http://www.lucid-cake.net/osx_qpe/index_de.html |
46 | for your Mac. | 47 | how to create a buildsystem for your Mac. |
47 | What is different to the previous desciption: | 48 | What is different to the previous desciption: |
48 | You don't need Qtopia ! | 49 | You don't need Qtopia ! |
49 | It is recommended to use QT/E in version 2.3.7 instead of 2.3.5 as described. | 50 | It is recommended to use QT/E in version 2.3.7 instead of 2.3.5 as described. |
50 | The Patch for QT/E for Opie, including all other opie-patches is available in the | 51 | The Patch for QT/E for Opie, including all other opie-patches is available in the |
51 | qt-directory ($OPIEDIR/qt) and is called "qte237-all-macosx.patch" | 52 | qt-directory ($OPIEDIR/qt) and is called "qte237-all-macosx.patch". |
52 | 53 | ||
53 | If your buildsystem is working correctly, you should be able to build | 54 | If your buildsystem is working correctly, you should be able to build |
54 | opie. You have to enter "make menuconfig" and set | 55 | opie. 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)" |
56 | activate the platform specific changes. | 57 | activate the platform specific changes. |
57 | 58 | ||
58 | You will see that a lot of applications and plugins/applets will not compile | 59 | You will see that a lot of applications and plugins/applets will not compile |
59 | successfully, due to the fact that they are not ported to this platform. | 60 | successfully, due to the fact that they are not ported to this platform. |
60 | You may disable them to be able to compile the rest. | 61 | You may disable them to be able to compile the rest. |
61 | 62 | ||
62 | 63 | ||
63 | Information for Developers: | 64 | Information for Developers: |
64 | --------------------------- | 65 | --------------------------- |
65 | 66 | ||
66 | 1. Platform specific code should be surrounded by | 67 | 1. Platform specific code should be surrounded by |
67 | #ifdef Q_OS_MACX | 68 | #ifdef Q_OS_MACX |
68 | MACOS-X CODE | 69 | MACOS-X CODE |
69 | #else | 70 | #else |
70 | OTHER-CODE | 71 | OTHER-CODE |
71 | #endif | 72 | #endif |
72 | 73 | ||
73 | 2. The Plugin-Handling by MacOS-X is different than it is by Linux. | 74 | 2. The Plugin-Handling by MacOS-X is different than it is by Linux. |
74 | On linux-systems, shared libraries are not different to dynamic loaded libraries | 75 | On 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 |
76 | at startup or manually by any application. | 77 | at startup or manually by any application. |
77 | On MacOS-X, the plugins are loaded by a special mechanism and must be in a special | 78 | On MacOS-X, the plugins are loaded by a special mechanism and must be in a special |
78 | binary format. Therefore you have to add the term "plugin" to the CONFIG-clause, as | 79 | binary format. Therefore you have to add the term "plugin" to the CONFIG-clause, as |
79 | for instance: | 80 | for instance: |
80 | 81 | ||
81 | TEMPLATE=lib | 82 | TEMPLATE=lib |
82 | CONFIG += qt plugin release | 83 | CONFIG += qt plugin release |
83 | 84 | ||
84 | If you don't add "plugin" you will get a shared library which is not loadable | 85 | If 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 | ||
89 | For problems, help and flames, feel free to contact me at | 90 | For problems, help and flames, feel free to contact me at |
90 | 91 | ||
91 | eilers.stefan@epost.de \ No newline at end of file | 92 | eilers.stefan@epost.de \ No newline at end of file |