+ <p>
+ Add <tt>/usr/local/arm/2.95.3/bin</tt> to your PATH. Add the following line (depends on your shell)
+ to your shell's configuration file :
+ <tscreen><verb>
+export PATH=/usr/local/arm/2.95.3/bin:$PATH
+ </verb></tscreen>
+ I would advise you to completely log out and then log in again, so that
+ the change would be taken into account. You can now check that when you
+ type <tt>arm-linux-gcc</tt>, it launches the cross-compiler.
+ </p>
+
+ <p>
+ Next are some packages that you may compile by yourself, but I found
+ it was easier to use the precompiled packages. You can take them
+ at <htmlurl url="http://ipkgfind.handhelds.org/" name="ipkgfind">.
+ You may find packages with other version numbers which should not be
+ a problem.
+ <descrip>
+ <tag><tt>libgcc1_3.1.1-1_arm.ipk</tt></tag>
+ This provides libgcc.so.1 which is needed to compile some libraries.
+ <tag><tt>xlibs_4.1-5_arm.ipk</tt>, <tt>xlibs-dev_4.1.0-16_arm.ipk</tt></tag>
+ Those are the libraries ans the development files for X windows.
+ <tag><tt>zlib1g_1.1.4-3_arm.ipk</tt>, <tt>zlib1g-dev_1.1.3-fam1_arm.ipk</tt></tag>
+ These libraries are needed by some libraries to compile.
+ </descrip>
+
+ Install these packages on your compiler box in <tt>/usr/local/arm/2.95.3/arm-linux</tt> :
+ You can use the script <tt>install.sh</tt> :
+ <tscreen><verb>
+#!/bin/sh
+# script to install .ipk into the arm-toolchain
+# usage : ./install.sh foobar.ipk
+
+if ! tar -xvzf $1 2> /dev/null
+then
+ ar xv $1 2> /dev/null
+fi
+cp data.tar.gz /usr/local/arm/2.95.3/arm-linux
+cd /usr/local/arm/2.95.3/arm-linux
+tar -xvzf data.tar.gz
+ </verb></tscreen>
+ </p>
+ </sect1>
+</sect>
+
+<sect>
+ <heading>Setting up Opie cross-compile environment</heading>
+ <p>Download the Opie SDK from the website <htmlurl url="http://opie.handhelds.org/" name="OPIE website">
+using the menuitem "Download Opie SDK" or try the direct link here: <htmlurl url="ftp://ftp.handhelds.org/zecke/" name="Download Opie SDK">.
+Download all files to your ${SOURCES}/opie directory.
+ </p>
+ <sect1>
+ <heading>Opie SDK</heading>
+ <p>The Opie SDK does not come with a README file or installation instructions.
+I give them here instead. There are two tar files in the download a OpieSDK.tar.gz2 and a kdevelop_src.tar.bz2.
+The last file is a modified kdevelop for use with the OpieSDK. In this tutorial we will not use that.
+Unpack OpieSDK.tar.bz2 in your sources <tt>cd ${SOURCES}/opie</tt> directory.
+ <tscreen><verb>
+cd ${SOURCES}/opie
+tar -xjvf OpieSdk.tar.bz2
+ </verb></tscreen>
+ It creates a directories structure <tt>${SOURCES}/opie/opt/OpieSDK</tt>. Inside that directory a script is present to
+<tt>start_kdevelop</tt>. Modify this script so that it uses the correct paths for you setup.
+ <tscreen><verb>
+#!/bin/sh
+source ${SOURCES}/opie/opt/OpieSdk/dev_env
+
+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>