+export KDEDIR=${SOURCES}/opie/opt/OpieSdk/kde
+export PATH=${SOURCES}/opie/opt/OpieSdk/kde/bin:$PATH
+kbuildsycoca
+kdevelop
+ </verb></tscreen>
+ Save the script. Do the same with the script <tt>arm_source</tt>
+ <tscreen><verb>
+source ${SOURCES}/opie/opt/OpieSdk/dev_env
+export QTDIR=$QTDIR_ARM
+export OPIEDIR=$OPIEDIR_ARM
+ </verb></tscreen>
+ Save the script and modify the script <tt>host_source</tt> in the same manner as above.
+ <tscreen><verb>
+source ${SOURCES}/opie/opt/OpieSdk/dev_env
+export QTDIR=$QTDIR_NAT
+export OPIEDIR=$OPIEDIR_NAT
+ </verb></tscreen>
+ Save the script and modify the script <tt>dev_env</tt> in the same manner as above.
+ <tscreen><verb>
+export PYTHONPATH=${SOURCES}/opie/opt/OpieSdk/python/opie:${SOURCES}/opie/opt/OpieSdk/python/sip
+export PATH=/usr/local/arm/2.95.3/bin:/opt/OpieSdk/host_tools:${SOURCES}/opie/opt/OpieSdk/opie/x86/qt-2.3.7/bin:$PATH
+export PATH=${SOURCES}/opie/opt/OpieSdk/opie/x86/qmake:$PATH
+export QTDIR_NAT=${SOURCES}/opie/opt/OpieSdk/opie/x86/qt-2.3.7
+export OPIEDIR_NAT=${SOURCES}/opie/opt/OpieSdk/opie/x86/sdk
+export QTDIR_ARM=${SOURCES}/opie/opt/OpieSdk/opie/arm/qt-2.3.7
+export OPIEDIR_ARM=${SOURCES}/opie/opt/OpieSdk/opie/arm/sdk
+export OPIE_SDK_BASE=${SOURCES}/opie/opt/OpieSdk/
+export OPIE_SDK_QMAKE_BASE=${SOURCES}/opie/opt/OpieSdk/opie/x86/sdk/mkspecs/qws/
+export OPIE_DOC=${SOURCES}/opie/opt/OpieSdk/apidocs
+
+export LD_LIBRARY_PATH=${SOURCES}/opie/opt/OpieSdk/sip/lib:$OPIEDIR_NAT/lib:$QTDIR_NAT/lib:$LD_LIBRARY_PATH
+export OPIE_LANGUAGES=de:en:cz:da:dk:es:fr:hu:it:ja:ko:lv:mk:nl:no:pl:pt:pt_BR:ru:sl:zh_CN:zh_TW
+ </verb></tscreen>
+ The symbolic linke to the tool <tt>qmake</tt> points now to the wrong place. We need to fix this symbolic link.
+Here is the way to do that.
+ <tscreen><verb>
+cd host_tools
+ln -sf /home/jpsaman/src/opie/opt/OpieSdk/opie/x86/sdk/qmake/qmake qmake
+cd ../
+ </verb></tscreen>
+ Now it is time to fire up our development environment and start hacking in Opie.
+ </p>
+ </sect1>
+</sect>