Diffstat (limited to 'development/macosx/README_MACOSX') (more/less context) (show whitespace changes)
| -rw-r--r-- | development/macosx/README_MACOSX | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/development/macosx/README_MACOSX b/development/macosx/README_MACOSX index 25de8d6..34360c5 100644 --- a/development/macosx/README_MACOSX +++ b/development/macosx/README_MACOSX @@ -68,68 +68,68 @@ make After compiling successful (I hope) you need qvfb: cd tools/qvfb make Compile QT/E-2.3.7: Got to into the basic directory of qt-2.3.2 and enter export QTDIR=`pwd` export QPEDIR=$QTDIR export DYLD_LIBRARY_PATH=$QTDIR/lib ./configure -platform darwin-generic-g++ -qconfig qpe -qvfb -depths 4,8,16,32 make Now create a link for the uic of qt-2.3.2 into the bin-directory of qt/e 2.3.7 ! Otherwise OPIE will fail to compile ! -Compile OPIE: +Compile OPIE (Please don't forget to read the following "Known Bugs" section!): Set your environment (You may use the script "set_vars.sh" to set your variables successfully ! BUT: You have to customize this script for YOUR needs !!) Go into the basic directory of Opie make menuconfig" set "Build Parameters"->"Target Machine"->"Mac OS X (DARWIN)" to activate the platform specific changes. save and exit the menuconfig app make (ATTENTION: See Known Bugs below!!) You will see that a lot of applications and plugins/applets will not compile successfully, due to the fact that they are not ported to this platform. You may disable them to be able to compile the rest. Remember: A lot of configuration-settings are not tested and might fail to compile. If you want to avoid misconfigurations, you may want to start with the config-file in this directory. Just copy "config_macosx" to $OPIEDIR/.config to get a working configuration to start with. (The missing apps/plugins will be ported on demand.) Known Bugs (compilation problems): ----------- The Apple-Linker does not load indirect linked libraries automatically ( if somebody has a solution here, please inform me !!), therefore I had to add "-lopiedb2" and "-lqpe" for applications/libraries who used libraries which are linked against them. A goot solution would be to add it in the project files of these application, but this would influence the linux-platform as well... :( As a first (but stupid) solution, I added this linker parameter to the global "include.pro" which adds them for everything.. Yes, also for libqpe etc.. Therefore this project will not compile out of the box. You have to compile in a two-pass way: -Pass 1: Find the line "LIBS += -lopiedb2 -lqpe" in the file include.pro and comment out it (put a "#" - in front of it) +Pass 1: Find the line "LIBS += -lopiedb2 -lqpe" or "LIBS += -lqpe" and the line "LIBS += -lopiecore2" in the file include.pro + and comment them out (put a "#" in front of them) Do a "make -k" to compile what is already compileable (some will not compile) -Pass 2: Remove the comment from Pass1 and do a "make". The rest should compile now successfully. +Pass 2: Remove the comments from Pass1 and do a "make". The rest should compile successfully. I know, this is a silly solution ! But I don't have anything better without influence the Linux build process too much .. I would be happy, if somebody could help me here ! SPECIAL INFORMATION FOR USERS OF PANTHER ---------------------------------------- I had a lot of problems compiling qt-2.3.2 and QT/E-2.3.7 on Panther. The new release of the X-Server causes a lot of trouble.. To compile QT-2.3.2 successfully, you have to disable support of freetype fonts and you have to use the patch in this directory, otherwise your wont't be able to compile ! Use the param "-no-xft" for the configure script to disable this function ! Information for Developers: --------------------------- |