summaryrefslogtreecommitdiff
authormickeyl <mickeyl>2005-02-12 16:22:18 (UTC)
committer mickeyl <mickeyl>2005-02-12 16:22:18 (UTC)
commit292ce81455773c463a8d7ed9c1aef2d08b90514d (patch) (side-by-side diff)
tree433fd4e7ce23e53a9c65c19a18f630ad85d7f4d0
parent0bf0f893a82426615cfe9f0bf764e1344c733ee3 (diff)
downloadopie-292ce81455773c463a8d7ed9c1aef2d08b90514d.zip
opie-292ce81455773c463a8d7ed9c1aef2d08b90514d.tar.gz
opie-292ce81455773c463a8d7ed9c1aef2d08b90514d.tar.bz2
update per recent changes in oe and opie
Diffstat (more/less context) (show whitespace changes)
-rw-r--r--README.OE13
1 files changed, 7 insertions, 6 deletions
diff --git a/README.OE b/README.OE
index f99873a..ab722e1 100644
--- a/README.OE
+++ b/README.OE
@@ -1,27 +1,28 @@
------------------------------------------------------------------------------------
How to use the Opie standalone buildsystem to develop against an OpenEmbedded tree:
------------------------------------------------------------------------------------
a) Grab BitBake and OpenEmbedded (see GettingStarted on the openembedded.org Wiki)
b) Have a properly working setup and edited local.conf w/ at least MACHINE and DISTRO set
-c) bitbake qte-for-opie (you may also want to bitbake libpcap, openssl, sqlite3, ipkg, libxine, etc.)
+c) bitbake qte libpcap openssl sqlite3 (don't bitbake libqpe-for-opie nor any other opie library)
d) Use a freshly checked out Opie tree (yes, I mean it! Don't try just to make clean or mrproper)
e) Choose "OpenEmbedded w/ OE build dir set below (TARGET_OE) (Option 5)" as target machine
f) Specify your OpenEmbedded build dir, e.g. /local/pkg/oe/tosa
-g) Answer all the rest - you may want to add more include paths pointing to inside the oe
+g) Specify your OpenEmbedded host system (OE_HOST_SYSTEM) and target system (OE_TARGET_SYSTEM)
+h) Answer all the rest - you may want to add more include paths pointing to inside the oe
build tree for some additional dependencies, i.e. for libsword, libipkg, libxine, and libsqlite3.
-h) make menuconfig and sanity check your answers
-i) make. if the build stops, you either need to bitbake additional dependencies or something else happenend ;)
+i) make menuconfig and sanity check your answers
+j) make. if the build stops, you either need to bitbake additional dependencies or something else happenend ;)
-j) copy the binaries over or mount your build tree via NFS
+k) copy the binaries over or mount your build tree via NFS
and export LD_LIBRARY_PATH=<path/to/oe/staging/libdir>:<path/to/opie/libdir>
and export PATH=<path/to/oe/staging/bindir>:<path/to/opie/bindir>
-k) run qpe and enjoy a great cross development environment
+l) run qpe and enjoy a great cross development environment
Note: Send feedback to opie-devel@handhelds.org
Cheers,
Michael 'Mickey' Lauer