This file looks large and may slow your browser down if we attempt
to syntax highlight it, so we are showing it without any
pretty colors.
Highlight
it anyway.
| 1 |
------------------------------------------------------------------------------------ |
| 2 |
How to use the Opie standalone buildsystem to develop against an OpenEmbedded tree: |
| 3 |
------------------------------------------------------------------------------------ |
| 4 |
a) Grab BitBake and OpenEmbedded (see GettingStarted on the openembedded.org Wiki) |
| 5 |
b) Have a properly working setup and edited local.conf w/ at least MACHINE and DISTRO set |
| 6 |
c) bitbake qte libpcap openssl sqlite3 libetpan sword - Note: Don't bitbake libqpe-for-opie |
| 7 |
nor any other opie library! These will be built out of the standalone Opie build system. |
| 8 |
|
| 9 |
d) Use a freshly checked out Opie tree (yes, I mean it! Don't try just to make clean or mrproper) |
| 10 |
e) Choose "OpenEmbedded w/ OE build dir set below (TARGET_OE) (Option 5)" as target machine |
| 11 |
f) Specify your OpenEmbedded build dir, e.g. /local/pkg/oe/tosa |
| 12 |
g) Specify your OpenEmbedded host system (OE_HOST_SYSTEM) and target system (OE_TARGET_SYSTEM) |
| 13 |
h) Answer all the rest - you may want to add more include paths pointing to inside the oe |
| 14 |
build tree for some additional dependencies. |
| 15 |
i) make menuconfig and sanity check your answers |
| 16 |
j) make. if the build stops, you either need to bitbake additional dependencies or something else happenend ;) |
| 17 |
|
| 18 |
k) copy the binaries over or mount your build tree via NFS |
| 19 |
and export LD_LIBRARY_PATH=<path/to/oe/staging/libdir>:<path/to/opie/libdir> |
| 20 |
and export PATH=<path/to/oe/staging/bindir>:<path/to/opie/bindir> |
| 21 |
|
| 22 |
l) run qpe and enjoy your cross development environment |
| 23 |
|
| 24 |
Note: Send feedback to opie-devel@handhelds.org |
| 25 |
|
| 26 |
Cheers, |
| 27 |
|
| 28 |
Michael 'Mickey' Lauer |