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_MACOSX8
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
@@ -72,25 +72,25 @@ make
72Compile QT/E-2.3.7: 72Compile QT/E-2.3.7:
73 73
74Got to into the basic directory of qt-2.3.2 and enter 74Got to into the basic directory of qt-2.3.2 and enter
75export QTDIR=`pwd` 75export QTDIR=`pwd`
76export QPEDIR=$QTDIR 76export QPEDIR=$QTDIR
77export DYLD_LIBRARY_PATH=$QTDIR/lib 77export DYLD_LIBRARY_PATH=$QTDIR/lib
78./configure -platform darwin-generic-g++ -qconfig qpe -qvfb -depths 4,8,16,32 78./configure -platform darwin-generic-g++ -qconfig qpe -qvfb -depths 4,8,16,32
79make 79make
80 80
81Now create a link for the uic of qt-2.3.2 into the bin-directory of qt/e 2.3.7 ! 81Now create a link for the uic of qt-2.3.2 into the bin-directory of qt/e 2.3.7 !
82Otherwise OPIE will fail to compile ! 82Otherwise OPIE will fail to compile !
83 83
84Compile OPIE: 84Compile OPIE (Please don't forget to read the following "Known Bugs" section!):
85Set your environment 85Set your environment
86(You may use the script "set_vars.sh" to set your variables successfully ! 86(You may use the script "set_vars.sh" to set your variables successfully !
87BUT: You have to customize this script for YOUR needs !!) 87BUT: You have to customize this script for YOUR needs !!)
88Go into the basic directory of Opie 88Go into the basic directory of Opie
89make menuconfig" 89make menuconfig"
90set "Build Parameters"->"Target Machine"->"Mac OS X (DARWIN)" to activate the platform specific changes. 90set "Build Parameters"->"Target Machine"->"Mac OS X (DARWIN)" to activate the platform specific changes.
91save and exit the menuconfig app 91save and exit the menuconfig app
92make (ATTENTION: See Known Bugs below!!) 92make (ATTENTION: See Known Bugs below!!)
93 93
94You will see that a lot of applications and plugins/applets will not compile 94You will see that a lot of applications and plugins/applets will not compile
95successfully, due to the fact that they are not ported to this platform. 95successfully, due to the fact that they are not ported to this platform.
96You may disable them to be able to compile the rest. 96You may disable them to be able to compile the rest.
@@ -104,28 +104,28 @@ to get a working configuration to start with.
104 104
105Known Bugs (compilation problems): 105Known Bugs (compilation problems):
106----------- 106-----------
107The Apple-Linker does not load indirect linked libraries automatically ( if somebody 107The Apple-Linker does not load indirect linked libraries automatically ( if somebody
108has a solution here, please inform me !!), therefore I had to add "-lopiedb2" and "-lqpe" 108has a solution here, please inform me !!), therefore I had to add "-lopiedb2" and "-lqpe"
109for applications/libraries who used libraries which are linked against them. 109for applications/libraries who used libraries which are linked against them.
110A goot solution would be to add it in the project files of these application, but this would 110A goot solution would be to add it in the project files of these application, but this would
111influence the linux-platform as well... :( 111influence the linux-platform as well... :(
112As a first (but stupid) solution, I added this linker parameter to the global "include.pro" 112As a first (but stupid) solution, I added this linker parameter to the global "include.pro"
113which adds them for everything.. Yes, also for libqpe etc.. 113which adds them for everything.. Yes, also for libqpe etc..
114Therefore this project will not compile out of the box. You have to compile in a two-pass way: 114Therefore this project will not compile out of the box. You have to compile in a two-pass way:
115 115
116Pass 1: Find the line "LIBS += -lopiedb2 -lqpe" in the file include.pro and comment out it (put a "#" 116Pass 1: Find the line "LIBS += -lopiedb2 -lqpe" or "LIBS += -lqpe" and the line "LIBS += -lopiecore2" in the file include.pro
117 in front of it) 117 and comment them out (put a "#" in front of them)
118 Do a "make -k" to compile what is already compileable (some will not compile) 118 Do a "make -k" to compile what is already compileable (some will not compile)
119Pass 2: Remove the comment from Pass1 and do a "make". The rest should compile now successfully. 119Pass 2: Remove the comments from Pass1 and do a "make". The rest should compile successfully.
120 120
121 121
122I know, this is a silly solution ! But I don't have anything better without influence the Linux build 122I know, this is a silly solution ! But I don't have anything better without influence the Linux build
123process too much .. I would be happy, if somebody could help me here ! 123process too much .. I would be happy, if somebody could help me here !
124 124
125SPECIAL INFORMATION FOR USERS OF PANTHER 125SPECIAL INFORMATION FOR USERS OF PANTHER
126---------------------------------------- 126----------------------------------------
127I had a lot of problems compiling qt-2.3.2 and QT/E-2.3.7 on Panther. The 127I had a lot of problems compiling qt-2.3.2 and QT/E-2.3.7 on Panther. The
128new release of the X-Server causes a lot of trouble.. 128new release of the X-Server causes a lot of trouble..
129 129
130To compile QT-2.3.2 successfully, you have to disable support of freetype fonts and you have 130To compile QT-2.3.2 successfully, you have to disable support of freetype fonts and you have
131to use the patch in this directory, otherwise your wont't be able to compile ! 131to use the patch in this directory, otherwise your wont't be able to compile !