| -rw-r--r-- | development/macosx/README_MACOSX | 14 |
1 files changed, 4 insertions, 10 deletions
diff --git a/development/macosx/README_MACOSX b/development/macosx/README_MACOSX index ac62046..25de8d6 100644 --- a/development/macosx/README_MACOSX +++ b/development/macosx/README_MACOSX @@ -1,68 +1,62 @@ Information about porting Opie to MacOS-X (eilers) ================================================== Credits: -------- -Special thanks to Andreas Junghans (webmaster@lucid-cake.net) for its patches for qt-X11 (2.3.2), +Special thanks to Andreas Junghans (webmaster@lucid-cake.net) providing patches for qt-X11 (2.3.2), QT/E (2.3.5) and qtopia (1.6.1). -Without them, I wouldn't be able to provide the port for OPIE to MacOS-X that fast.. +Without them, I wasn't able to provide the port for OPIE to MacOS-X that fast.. Thanks to Juergen Graf to debug this very generic README ! Status: ------- -This work is done, do provide a development platform for Apple-Users! Please do not expect that you +Aim of this work is to provide a development platform for Apple-Users! Please do not expect that you could create a productive Opie system for the Mac with it !! The basic system works quite well. But a lot of applications and plugins, which are platform specific, need some work to be compileable. What is ready: libqpe libopie1 libopie2 pim-applications (addressbook, todolist, datebook, today) A lot of applications and plugins which are not platform specific. ToDO: ----- There are some functions in the sourcecode which are not yet ported to Mac. If the MacOS environment should be used for real productive work, the following functions must be implemented correctly: libopie/pim/otimezone.cpp: Accessing of "setenv(...)" on Mac caused bus-errors. Workaround/Fix: Unknown Current-State: setenv() was just commented out. Thus the related functions may behave wrong! -library/filemanager.cpp: -The sendfile() function is not available in MacOSX. Therefore a workaround must be implemented. -Workaround/Fix: Unknown. The function is available in the header files, but disabled by a -"#ifdef SENDFILE" .. and not implemented int the c-library. -If it will be supported, it should activate itself automatically by the "#ifdef".. - How to compile Opie for MacOS-X: ------------------------------- Before compiling for MacOS-X, you need the following: 1. X11-Server+X11SDK (Provided by Apple) 2. QT-2.3.2 for X11 (Provided by Trolltech) 3. QT/E-2.3.7 (Provided by Trolltech) 4. Patches for QT-2.3.2 for MacOSX (take the one in this directory !) 5. Patches for QT/E-2.3.7 for MacOSX (take the one, provided in $OPIEDIR/qt) The Patch for QT-2.3.2 is provided in this directory and is called "qt232-X11.patch". The Patch for QT/E for Opie, including all other opie-patches is available in the qt-directory ($OPIEDIR/qt) and is called "qte237-all-macosx.patch". Please read further, how to compile the stuff. HOWTO COMPILE: ------------- Compile QT-2.3.2: @@ -144,25 +138,25 @@ Information for Developers: #ifdef Q_OS_MACX MACOS-X CODE #else OTHER-CODE #endif 2. The Plugin-Handling by MacOS-X is different than it is by Linux. On linux-systems, shared libraries are not different to dynamic loaded libraries (aka plugins). They just are different whether they are loaded automatically at startup or manually by any application. On MacOS-X, the plugins are loaded by a special mechanism and must be in a special binary format. Therefore you have to add the term "plugin" to the CONFIG-clause, as for instance: TEMPLATE=lib CONFIG += qt plugin release If you don't add "plugin" you will get a shared library which is not loadable (Error-Code: NSObjectFileImageInappropriateFile (2))! For problems, help and flames, feel free to contact me at -eilers.stefan@epost.de
\ No newline at end of file +stefan@eilers-online.net |