-rw-r--r-- | README.OE | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/README.OE b/README.OE new file mode 100644 index 0000000..19a0d5d --- a/dev/null +++ b/README.OE | |||
@@ -0,0 +1,24 @@ | |||
1 | How to use the Opie standalone buildsystem to develop against an OpenEmbedded tree: | ||
2 | |||
3 | a) Grab BitBake and OpenEmbedded (see GettingStarted on the openembedded.org Wiki) | ||
4 | b) Have a probperly working setup and edited local.conf w/ at least MACHINE and DISTRO set | ||
5 | c) bitbake qte | ||
6 | |||
7 | d) make clean in the Opie tree | ||
8 | e) Choose "OpenEmbedded w/ OE build dir set below (TARGET_OE) (Option 5)" as target machine | ||
9 | f) Specify your OpenEmbedded build dir, i.e. /local/pkg/oe/tosa | ||
10 | g) Answer all the rest - you may want to add more include paths pointing to inside the oe | ||
11 | build tree for some additional dependencies, i.e. for libsword, libipkg, libxine, and libsqlite3. | ||
12 | h) make menuconfig and sanity check your answers | ||
13 | i) build | ||
14 | |||
15 | j) copy the binaries over or mount your build tree via NFS | ||
16 | and export LD_LIBRARY_PATH=<path/to/oe/staging/libdir>:<path/to/opie/libdir> | ||
17 | and export PATH=<path/to/oe/staging/bindir>:<path/to/opie/bindir> | ||
18 | |||
19 | Note: It's pretty ad-hoc but it seems to work :) | ||
20 | |||
21 | Cheers, | ||
22 | |||
23 | Michael 'Mickey' Lauer | ||
24 | |||