| author | ar <ar> | 2005-01-20 22:31:22 (UTC) |
|---|---|---|
| committer | ar <ar> | 2005-01-20 22:31:22 (UTC) |
| commit | fdc37fbd908472e28735a8f0b01e3e66a43535e0 (patch) (side-by-side diff) | |
| tree | f649f88e87c47d8196f921c466c880b11817ebaa /README.OE | |
| parent | 524366c3b9475346a8f5ba6790a61d19a52fb4ef (diff) | |
| download | opie-fdc37fbd908472e28735a8f0b01e3e66a43535e0.zip opie-fdc37fbd908472e28735a8f0b01e3e66a43535e0.tar.gz opie-fdc37fbd908472e28735a8f0b01e3e66a43535e0.tar.bz2 | |
- little correction for oe use
| -rw-r--r-- | README.OE | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -1,24 +1,24 @@ 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 probperly working setup and edited local.conf w/ at least MACHINE and DISTRO set -c) bitbake qte +c) bitbake qte-for-opie d) make clean in the Opie tree e) Choose "OpenEmbedded w/ OE build dir set below (TARGET_OE) (Option 5)" as target machine f) Specify your OpenEmbedded build dir, i.e. /local/pkg/oe/tosa g) 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) build j) 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> Note: It's pretty ad-hoc but it seems to work :) -Cheers, +Cheers, Michael 'Mickey' Lauer |